• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 825
  • Last Modified:

Windows 2012 Remote Desktop services naming convention

I am about to setup windows server 2012 Remote Desktop services. I plan to have 3 Rds servers, plus web app, broker server and licensing server.

Can someone suggest what roles i can put together and naming conventions of servers.

Thanks

Phil
0
philipfarnes
Asked:
philipfarnes
  • 3
  • 2
2 Solutions
 
Ayman BakrSenior ConsultantCommented:
Licensing and the web app are light weight. These could go together. The broker server carries out functions of load balancing and collecting information so it is kinda heavy and it would be better if you separate it in a production environment. RDS servers hosting your apps should be separate again because they might get overloaded serving your users. How many of RDS servers should depend on the users' load, type of applications (heavy, intensive, light) and number of applications that can go together (application silos).

Naming convention well depends on your environment, preferences, management style and policies. In our environment, server names should include the following information:
1. Code for the funtion/role of the server
2. Number determining its number within the list of servers with the same role
3. Code for determining whether it is a production or test server
4. Perhaps code for determining platform (windows/unix etc...)

The latter might not be so important. So for the second RDS server you might want the name to be: RDS0002P.
P - might stand for production. Note that I have put trailing zeros before the number in order to incorporate number of digits in your number code. This might turn handy later when you want to grow your server numbers in the future or you want to create a kind of number sets for different server categories or server roles but existing in different sites.
0
 
philipfarnesAuthor Commented:
Thanks for this

I was thinking of using

Ldn-Rds-01, ldn-Rds-02 and ldn-Rds-03 for Remote Desktop servers. What names would you give broker and web app/lic server.

Thanks

Phil
0
 
Ayman BakrSenior ConsultantCommented:
I don't know what ldn stands for, but what about:
Web App/license -> ldn-Wap-01
Broker server     -> ldn-Brk-01

Take into consideration whether you should standardize the number of characters in the name, i.e. limit the code of the role for example (like say only 3 characters for the role code as in your example rds), vs. different name sizes for different roles, like:
RDS server       -> ldn-Rds-01               and
Broker server  -> ldn-Brkr-01.

I would prefer to put rules and standardize the number of characters for each code. So if you foresee a growth abover 99 servers then you might want to have the number of digits in the number code to be three, like in: ldn-Rds-001.
0
 
philipfarnesAuthor Commented:
Do users connect to central server broker and it evenly distributes to rds servers.

What about public cert.

Do I go for rds.domain.com that points to public ip that Nats to broker server
0
 
Ayman BakrSenior ConsultantCommented:
Do users connect to central server broker and it evenly distributes to rds servers.

Users connect to RD Web -> RD Web contact server broker on behalf of users to find the least loaded RDS server.
What about public cert.

If you want to connect to RD Web remotely from outside your LAN then you need to setup RD Gateway and use public certs. Otherwise, public certs are not necessary.
Do I go for rds.domain.com that points to public ip that Nats to broker server
Please check the following:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_28047998.html
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_28014103.html
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now