The third user gets the option to disconnect one of the other two. Two users can log in perfectly fine, and launch remoteapps. I also am trying the Remote Web access, and the same thing happens. The License Server Manager shows that the server is activated.
I have the RAP and CAP policies enabled, it is set to allow the maximum number of simultaneous users. I don't think this matters but along with the services selected here when originally setting up I also installed the Connection Broker and Session Host services. Are there any additional settings to change in Or Remote Services based, I do not have the Network Policy category seen here though I am able to launch the Network Policy Server. When I was checking to see if the RDS role was installed, in the Add Roles and Features wizard, regardless of whether I was doing Role-Based I'm wondering if the link you provided was discussing 2012 and not 2012 r2 because I did see some differences. I added the server there, the certificate checks out, and it says One thing that was not done was adding the server to the Gateway Farm in the Gateway manager. Ok, went through and double checked everything - the RDS role was already installed. I'm going to try to provide as much info as possible. I wouldn’t do this if you have already obtained licensing and should definitely not be used in a production environment.First, thanks for your quick response, much appreciated. Once back up your RDS Licensing should be back at the start of a 128 Day grace period. Now there should be a binary key value (like in the screenshot), you first need to have full access permissions to the folder (or take ownership) and then simply delete that value and reboot the server. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod As always when editing the registry, take a backup of the key/s you’re modifying. To reset the grace period there is a registry key that we need to delete. Since this was a test I didn’t want to go using keys to activate or setup a licensing server (purely a PoC for us in IT at this stage). Going back to the RDS host I found the Licensing popup that informed me that the 128 day trial license had expired. When installing the Remote Desktop Session Host role on a Windows Server, you get a 120 days grace period where you do not need to specify a license server. After going through the motions of enabling the Remote Desktop Features and setting up RemoteFX on a Virtual Machine for testing, I found that I couldn’t login via RDP to that machine. As a trial I begun setting up RDS on one of our Dev machines. So we recently started looking into Terminal Services and RemoteFX to power some of our admin users and move them off to thin clients instead of full blown desktops.
0 kommentar(er)
