tucktech
asked on
Active Directory and RDS OU Organizing
Hello Experts, I would like a few opinions on the organization of keeping users and setups simple and clean as well as with using it with RDS.
Part 1: Active Directory
I have setup my active directory so that I have an OU setup for each department and then I put the users in each of the departments. I did this thinking it would be helpful when deploying printers and keeping security per OU.
Now I am thinking I would have been better off just setting up "Security Group - Global" for each department and keeping everyone in one OU.
Thoughts please.
Part 2: I have read the article Terminal Services: from A to Z (www.2x.com/docs/en/manuals/pdf/TerminalServicesAtoZ.pdf) and it was great however does not work well with my oringinal scheme, I think. In the guide it talks about creating an OU named TS (in my case I used RDS Users). For these users that are switching to RDS, I would move them from their departmental OU to the new RDS OU which completely breaks my original OU design.
I am ok with changing the OU design and revamping everything. I have about 30 users and if it makes it easier to manage I am all for it. I know organization design is a personal preference but I would like to hear from some experienced admins and their approach along with advantages and disadvantages. All comments welcome becuase I trying to figure out what would fit best.
Also, I believe if I turn on the loopback processing users would be in "thick client" mode when they are logging on from a desktop or laptop versus thin client.
To the person who wrote the terminal services: from a to z, great job!
Part 1: Active Directory
I have setup my active directory so that I have an OU setup for each department and then I put the users in each of the departments. I did this thinking it would be helpful when deploying printers and keeping security per OU.
Now I am thinking I would have been better off just setting up "Security Group - Global" for each department and keeping everyone in one OU.
Thoughts please.
Part 2: I have read the article Terminal Services: from A to Z (www.2x.com/docs/en/manuals/pdf/TerminalServicesAtoZ.pdf) and it was great however does not work well with my oringinal scheme, I think. In the guide it talks about creating an OU named TS (in my case I used RDS Users). For these users that are switching to RDS, I would move them from their departmental OU to the new RDS OU which completely breaks my original OU design.
I am ok with changing the OU design and revamping everything. I have about 30 users and if it makes it easier to manage I am all for it. I know organization design is a personal preference but I would like to hear from some experienced admins and their approach along with advantages and disadvantages. All comments welcome becuase I trying to figure out what would fit best.
Also, I believe if I turn on the loopback processing users would be in "thick client" mode when they are logging on from a desktop or laptop versus thin client.
To the person who wrote the terminal services: from a to z, great job!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.