IT Employment

Ask something
Discussion Locked

win2k roaming profiles

0 helpful
1 reply

by aubhall

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Created new profile for some win2k (upgrade from nt)user who needed to use digital certs, this would not work with mandatory profiles for some reason as idividual users could not import the cert. I got a round this by turning the ntuser.man into ntuser.dat, which is almost a roaming profile except for the fact that the users do not have write access to the profile which is located in the netlogon of out nt pdc.

Anybody any idea why this may be happioning?

1 reply

by chris..

Could be because you're running in a mixed mode environment. 2k and 4.0 handle profiles completely different. As you're seeing with the NTUSER.DAT. Now another option is to add the reg key in to a NTUSER.DAT for the default profile creation that looks for the cert, thus forcing a prompt for the cert location when the new profile is created. It gets a bit uglier than that, but I'm betting you'll be able to figure out the rest of the details.

This discussion is closed to new replies.