Fix - No Remote Desktop Licence Server available on RD Session Host server

A fully functional and activated Windows 2008/2008 R2/2012 Remote Desktop Session Host server displayed the following message



This was a simple setup on one server with the: connection broker, Session Host and Licensing server with RDS/TS CAL’s installed.

Even though the licensing seems to be configured correctly, in server manager:


Licensing diagnostics:


everywhere you look, everything seems to be OK. But the license manager shows something odd where No licenses are being used? 
This server was used since late 2012 Some interesting things could also be found in the event logs, the following events appear


EventID: 1130
Source: TerminalServices-RemoteConnectionManager

The Remote Desktop Session Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Session Host server, use the Remote Desktop Session Host Configuration tool.


EventID: 1128
Source: TerminalServices-RemoteConnectionManager

The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.


Solution 

Delete the REG_BINARY in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod"

Only leaving the default.


After a reboot the server should be working fine and get the licenses issued now and being getting used


Although everything seemed to be ok and configured correctly with valid licenses, it seems that the setup was still in a 120 day grace period, even though it was correctly configured.

Note: you must take ownership and give admin users full control to be able to delete this key.

Image Source - Internet

Reset Terminal license on Windows Server OS

While Windows installed with Terminal Server role it does work without License for 120 Days on trail license, where within 120 days if the License server is not Connected the server will stop accepting connection with below error and event ID



EventID: 1128
Source: TerminalServices-RemoteConnectionManager

The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.



The official solution is to Activate the RDS/TS CAL License server and point the Server to License server with User/Device License and will be resolve the problem

But if you want to reset the timer and again avail 120 days grace time  here is the solution

The solution was to delete the REG_BINARY in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Only leaving the default.


Note: you must take ownership and give admin users full control to be able to delete this key.

After a reboot the server should be working again for another 120 Days


Source - Internet

Enable guest network in unify ap without vlan

Within the Unifi controller software, go to Settings -> Wireless Networks.  Create the SSID you want to be the guest network, leave security open, and check the box labeled Guest Policy.  Don't setup any VLAN configuration because you do not need it.

Once you have done that, go to Settings -> Guest Control.  You do not need to use the guest portal option.  In the Access Control area, add the subnets you do not want guest wifi clients touching in the Restricted Subnets area.  

Once you have completed these steps, you have just created a guest wifi that users can connect to without the need to authenticate, and Unifi has restricted clients on that wifi network from being able to touch your production network...all without VLANs.

And the clients on the guest network would get an ip from your DHCP server as you would expect, and you can then filter the web traffic by content as you desire.

And one other thing, you need to allow dhcp Ip address on guest wifi so that guest client can get ip from dhcp, within Settings -> Guest Control you can add your entire subnet (i.e. 192.168.0.0/24) under Restricted Subnets and then add an allowed subnet for just your dhcp server (i.e. 192.168.1.5/32).

Result: - User can get Ip from dhcp but will not be able to ping any devices into the network.

One Plus 3/3T recieves Nougat!!

Great news for one plus 3/3t users as the android 7.0 nougat has started rolling out. Here's what it posted on their official Forum.

Hi all,
We are starting the incremental roll-out of OxygenOS 4.0 (N) for the OnePlus 3. Here are the changes for this build.
Here are some highlights:
Upgraded to Android 7.0 Nougat
New Notifications Design
New Settings Menu Design
Multi-Window View
Notification Direct Reply
Custom DPI Support
Added Status Bar Icon Options
Improved Shelf Customization
For those who were on previous versions for the OnePlus 3, we appreciate your active feedback and attempts to reach out to us. With your help, we have been able to better optimize and improve several key areas. Thank you for your patience and as always, we look forward to hearing your continued feedback in the bug reporting forum here: https://forums.oneplus.net/feedback/.

As always, this OTA will be incremental. The OTA will reach a small percentage of users today, and we'll begin a broader rollout in a few days.

Your feedback is appreciated. We may not always be able to respond to every comment in the forums, but please be assured that we take your comments and feedback seriously. Hope you enjoy!

Never Settle.