We have an AD 2003 domain.
All users have a normal user home directory (not TS home directory) in their AD user account properties.
I dont want their normal user home directory (H: drive) to be mapped when they log on to Terminal Servers.
So this is what I did.
I placed the Terminal Servers into their own OU.
I created a GPO for the Terminal Servers, disabled the User Config, and enabled Loopback Policy Processing on the Computer Config for this GPO. In this Computer Config, I enabled TS User Home Directory to point to D:\Tsusers.
Now, when users log on to these Terminal Servers, their normal user home directory H: drive is still being mapped.
No home directories created in d:\tsusers.
Do I have to run the chkroot.cmd command to create a ROOT DRIVE on each Terminal Server, in addition to setting the TS User Home Directory in Group Policy?
If I do, then in Group Policy where I enabled Terminal Server Home Directory of d:\tsusers, do I also need to put the drive letter that I assigned as the ROOT DRIVE by running the chkroot.cmd command?
Any help here as to why the normal home drive is still being mapped instead of using the TS home drive would be greatly appreciated.