Roaming Profiles for new users no longer works

[mgertz]

I am running a small school network and wanted to make the share folders invisible to the students -- profiles, SYSVOL, and Scripts (NETLOGON). So I changed the share name on the server to the same name with the $ sign (ie NETLOGON$). I found out that roaming profiles could not be accessed any longer so I put everything back the way it was and now I am not able to set up new user accounts so that they can access access roaming profiles from the client machines. I have tried creating a new share folder (Users) but the same thing occurs. Any users that were already set up can access their roaming profiles except for 4 of the accounts. Thanks for any help.

Mitch Gertz

 

[Jpoandl]

It sounds like you have the concept down. I would think that if most of the users are working, that you have a permissions problem or a mistype in the user profile for the 4 that do not work.

Here is a guidline:

http://support.microsoft.com/support/kb/articles/Q264/8/66.ASP

Joseph L. Poandl
MCSE 2000

 

[mgertz]

Thanks for your reply Joseph. Yes I thought it might be a mistype and have checked that numerous times. In fact I CTL C'd and CTL D'd from the user profiles paths that did work to the ones that didn't but to no avail.

I also have checked permissions and have found no discrepancy between the ones that work and any new users I am trying to input.

Seems as though something is corrupted although I don't know what. I am considering having my students saving everything (we are only 2 weeks into the year) and reformmating the hard drive and starting over if I can't resolve this.

One thing I didnt mention is that all my client machines are 2000 professional so there shouldn't be a problem with any OS mismatch.

By the way, why does SYSVOL and NETLOGON and profiles show up in the users network places by default. It would seem that microsoft would have by hid them by default.

Thanks again for your efforts in trying to help.

Mitch

 

[Zelandakh]

Remove the computer account from the domain, remove the client computer from the domain and then go and add them back in. This should cure you.