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

Multiple terminal servers, profile path problem

I have 2 Windows Server 2003 boxes w/ Terminal Services running and I need to be able to allow all domain users to log on to either box.  As such, I want to use Profile Paths to store the profiles on my data server.  However, everything wants to default to using the Locally stored profiles created prior to migrating from a workgroup environment to Active Directory.  If I disable the local user on the system, I can't logon.  If I rename the local profile, it creates a new one.  I can't get it to use a profile stored on my data server that is pathed in the Terminal Server Profile path.  Help!
1 Solution
The profile path is a user property. If you disable the local accounts, and your users can't logon anymore, well, then obviously, your users aren't logging on with their domain accounts. So have your users logon with the domain account, and they will start using the roaming profile specified in the terminal server profile path in the user's AD profile.

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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