Remote Desktop Server Configuration issues Two server configuration.

I have set up one Remote desktop server and chose the quick start method on server one. I had to set up the licensing mode on the server which pointed to our DC as was per user. It took a while for it to synchronize over our network but the next day common users were able to log onto that server and use it.

I took the same approach on the second desktop server but it does not seem to work. I pointed it to the licensing server and set it to per user in licensing mode however after waiting a day it still does not accept connecting and when logged onto server it still says " Remote Desktop Services will stop working in 117 Days. On the RD Connection Broker server, Use Server Manager to specify the Remote Desktop Licensing mode and the license server." When I go Remote Desktop Services > Overview and click on Tasks in Deployment Overview and choose Edit Deployment Properties is shows the licensing set to Per User and the license Server is selected below so I am confused.

How do I fix this.



I have checked the
TimSr. System AdminAsked:
Who is Participating?
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
You can have two separate ones.

We have singles running separately as well as singles/farm and farm/farm within the same AD Forest/Domain.

Splitting the DNS makes this simple as there will be two separate RD Gateway setups. By splitting the DNS folks on the inside and outside can access both resources via URL.

Make sure both are set up identically other than the URL.

Make sure NPS is set up correctly on the new server (Network Policy Server/Services). Register the new server in AD. That should give it the nudge it needs to work with Licensing.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Is the new Session Host being managed by the Broker service on the original?
0
 
TimSr. System AdminAuthor Commented:
They actually both have a broker service. I went into group policy and specified the license server and licensing mode then restarted the troubled server. Now when I go to Remote Desktop Services in Administrative Tools and open RD Licensing Diagnoser it shows a green checkmark and the number of licenses available but when I try to connect as a common user it fails and says the Connection was denied because the user account is not authorized for remote login. The same user can connect to the other Remote Desktop server without problem.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
I suggest adding the new server as a new Session Host to the existing Broker and thus Gateway and RDWeb. That simplifies things if they are on the same domain serving the same group of users.

If there is a need to publish an app or desktop session to a unique group of users then create a new Collection on the broker and give access to that collection to a Security Group that has the expected users in it.

Then set up the Session Host as needed.

Users with permissions to that Session Host will have access.
0
 
TimSr. System AdminAuthor Commented:
Ok, so how do I do that? Do I need to uninstall remote desktop from that server? Can I just uninstall the Broker from the second server. I am new to this type of deployment so please forgive me for asking dumb questions.

So if I uninstall all the roles then just add the server as a session host and that is it this will work?
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
The simplest way would be to re-install the OS, join the domain, and run the wizard on the Broker to add a new Session Host then create a new Collection there.
0
 
TimSr. System AdminAuthor Commented:
That is ugly and won't work for my situation. I have already configured this server and added all programs to the server that needs to be used. This deployment was supposed to be working today for all my users and If I have to reconfigure from scratch that is going to push me into next week which I cannot do.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
What do the RDS Licensing specific Event Logs say?
0
 
TimSr. System AdminAuthor Commented:
I have been playing with my current configuration and removed the broker role from the second server and just have the session host role on the second server.  I tried adding the server to a collection that was already created and received an error stating the wizard was unable to configure the RD session host server. Invalid Operation.

It added the server to the host list but when I try to access the server by name I get an error about a server farm.

Can I have two separate Remote Desktop servers where users can connect to either one or do I need to create this farm?
0
 
TimSr. System AdminAuthor Commented:
I am so confused and don't know the correct path or setup to do. I started out on this project to have two remote desktop servers pointing to one SQL server. On both servers I have installed our ERP software which connects to the SQL Server. I have set up both servers on a VM host. The one server is working yet the other server will not connect.

I have tried to setup the second server as a standalone like you state however when I go to install Remote Desktop services to the second server through the DC it  tells me a Remote Desktop Services Deployment already exists in the server pool. Select an RD Connection broker on which to create the Remote Desktop Services Deployment. How can I do this if it only lets me have one Connection Broker? Plus if I move forward I cannot install Session Based deployment it only allows Virtual Machine Based Desktop Deployment.  

I assume I need to install Remote Desktop services on the server locally instead of from the DC. What do you mean make sure NPS is setup correctly? The instruction set I am using (https://msfreaks.wordpress.com/2013/12/09/windows-2012-r2-remote-desktop-services-part-1/) does not mention this or it does not call it NPS.

Can you direct me to an instruction set that will help me with this setup? I am not familiar with this setup in any way and I am floundering. I am about to blow away both servers and start with a single hardware server and make all the users connect to it instead of have two VM servers.

I am going to try to install Remote Desktop Services completely on the second server and see if this works.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Second Paragraph: "... through the DC" ?

Run the entire RDS setup process on the new server. Nothing need be done anywhere else since it would be a standalone RDS environment.

NPS = Network Policy Server/Services. Click Start and type that to get the MMC. Right click on the root Node and Register in AD.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.