So I created a an OU for my Terminal Server then I created a lockdown GP applied it to my OU. I then Put my TS in the OU all by itself.
It has been working fine until I as admin got tired of being locked down too.
So I did this. I removed Authenticated Users and added my general users group. (MNoffUsers) Applied security of Read and Apply Group Policy to them.
Now the Terminal Server is not locking down at all for anyone. The kicker is that I put authenticated users back and removed the users group but that didn't work. It doesn't seem to be applying the group policy at all.
Start with the TS box; check out this question I helped with dealing with loopback and security filtering
MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.
While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…