8 replies
by ewgny
I solved this problem by setting up secondary accounts for users that use terminal services
TSuser01 02 etc. The users don't even know that they are changing logons since I configure their TS shortcut with the secondary login & password You can then give the TS user accounts a mandatory profile and script them their printers. The last thing you need is a roaming profile loading on your TS. The basic mandatory profile will load so fast they won't even realize that they are logging onto another server.
by ewgny
by ewgny
Ok What you can do is put the Computer object for the Terminal Server in a "Terminal Server" OU Create a Group Policy Loopback policy. If you need more on Loopback policies let me know).
The loopback policy will apply the group policy to the Computer object instead of the user object. In the loopback policy under computer configuration - Administrative logon - system, enable the "allow only local user profiles policy". Now the users Roaming Profiles will not be allowed to load on the TS.
by phand
Poster rated this answer.
by phand
Thank you ewgny@hotmail.com for your suggestion. I thought about this before however, decided it's not going to work for me. First, because users will expect to have access to their folders on another files server share, and my department policy want user to log on with their network account but not a generic account. Based on MS knowledge base article #246132,Terminal server suppose to look for specified profile path under account property first and then ignore roaming profile. I don't know what I did wrong but my TS did seem behaving this way. Here is the link to the MS article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;246132&Product=win2000
by flan
by phand
This is not an option for me because all of my users will get upset with the new account and password
by phand
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending