General discussion

Locked

Mandatory profile for terminal server

By Phand ·
I would like to assign a mandatory profile for my terminal users. I would like all of of my users connect the terminal server will use a same profile because I don't several hundred profiles store on my terminal server. My users already have roaming profile setup in their profile. I create a mandatory profile and shared it out and assign this patth to my user under Terminal service profile path. However, when my user log in, they see this message "Windows cannon locate your roaming profile and is attempting to log you on with your local profile..." What did I do wrong? any suggestion how to handle this problem? Thanks

This conversation is currently closed to new comments.

8 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by ewgny In reply to Mandatory profile for ter ...

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.

Collapse -

by ewgny In reply to

Another advantage to creating seperate TSuser accounts is that you can place all of the TS user accounts into their own OU. By doing this you can apply a restrictive set of group policies to the TSusers. Policies that may differ greatly from the users primary login.

Collapse -

by ewgny In reply to

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.

Collapse -

by Phand In reply to

Poster rated this answer.

Collapse -

by Phand In reply to Mandatory profile for ter ...

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

Collapse -

by flan In reply to Mandatory profile for ter ...

kill the accounts with roaming profiles and just recreates accounts. this should help because the new accounts you create will be the stadard you created for them.

Collapse -

by Phand In reply to

This is not an option for me because all of my users will get upset with the new account and password

Collapse -

by Phand In reply to Mandatory profile for ter ...

This question was closed by the author

Back to Windows Forum
8 total posts (Page 1 of 1)  

Related Discussions

Related Forums