Multiple Users Using Same Profile

[JBailey]

Hello,

We have two terminal servers, and multiple 'public' computers through out
our sites. Each site has one logon acct, and each logon acct maps to one
roaming profile.

For instance, all users at site2 user the user account site2. Acct is set to
use profile at \\server\share\site2

Is there a problem with 20 some users all logged in at the same time
accessing this same profile?

Thanks,
JBailey

 

[Vera Noest [MVP]]

Not if you make it a mandatory profile, which the users cannot
change. Otherwise the last user that logs of saves the settings for
all other users, and you will eventually end up with a corrupt
profile.

 

[JBailey]

Thats easy enough to do. Now a follow up.

When users log in to one server all profiles are correct. When they log into
another its like the profile didnt take effect. Both machines show the
profile as being mandatory, but svrA isnt applying the profile, while svrB
is

any idas??

 

[Vera Noest [MVP]]

Not without details like:
* is this a domain account or a local account on the TS?
* is there a normal and a TS-specific profile?
* how exactly is (are) the profile path(s)
* do the users have the correct premission to the TS-profile?
* do you get any security errors in the EvemtLog?

 

[JBailey]

* is this a domain account or a local account on the TS?
-this is a domain acct on a thin-client

* is there a normal and a TS-specific profile?
-only a TS-specific profile

* how exactly is (are) the profile path(s)
-\\server\tsprofiles\store_profile

* do the users have the correct permission to the TS-profile?
-for the purpose of troubleshooting, the group that needs access to this
profile have Full Access

* do you get any security errors in the EvemtLog?
-event id: 1000
windows cannot unload your registry class file. If you have a roaming
profile your settings are not replicated.
DETAIL: Access is denied. Build Number 2195

 

[Vera Noest [MVP]]

OK, these 2 different threads are getting very messy now.
But the important part is of course the eventid 1000, which makes
clear that this is a problem with a registry key.

This is a known problem, which is supposed to be fixed in SP3. Which
SP are you running? There is also a work around: installing IPSec.
For details, see:

319909 - A User May Experience a Slow Logoff Process Because of an
Open Registry Handle in the Classes Hive
http://support.microsoft.com/?kbid=319909

--
Vera Noest
MCSE, CCEA, MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please answer in newsgroup ---

 

[JBailey]

The IPSec fix corrected the problem.

Thanks!
JBailey

]