Help, stuck with network/ad problem

[e_g_r]

OK is this a random Microsoft Server problem or should i worry about it and how can i get it back working?

At the start of P2 today all users got the following login funny

"Windows did not load your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Windows did not load your profile because a server copy of the profile folder already exists that does not have the correct security. Either the current user or the Administrator's group must be the owner of the folder. Contact your network administrator."

They then get a different desktop and can't access their files.

In AD in the user the profile path is set to the following UNC path:

\\data-server\data\profiles\test

For whatever reason i could not access this folder and had to take control. The ntuser.ini ntuser.dat and ntuser.dat.log files were owned by a pupil login and were date stamped at the end of p1 today.

Any help would be much appreciated to regain my login. I don't want to re engineer the network as i have inherited a beast that defy's all known networking logics.

[Geoff]

What sort of server? Are you using folder redirection? roaming profiles? mandatory profiles?

[e_g_r]

server 2000

XP clients

No XP templates in AD (i inherited this)

No folder redirection that i can see

Mandatory profiles i think

[tarquel]

roaming profile got corrupt perhaps?

I get that occasionally.... just clear it and let a new one create itself. If of course its a mandatory one, then I'm not sure you'll want to clear it until you have created a new one to go in its place

The permissions thing is normal with roaming ones [well it is with mine anyhow hehe] as you can just take over ownership easy enough and do whatever you need to do.

Cheers
Nath

[e_g_r]

when you say clear it, do you mean on the server?

[mark]

If the profiles folder is identical for each user it has to be mandatory surely. Is the NTUSER file in the server profile folder a .man or .dat ? It would explain the behavior if it were a .dat - tho' who would do such a crazy thing? - probably it's just the profile has corrupted somehow.

Yes - on the server

Just re-create the mandatory profile as detailed on the wiki: http://www.russdev.com/edugeek/doku....atory_profiles

Unfortunately on Win2K you can't change profile location in bulk [without scripting] so recreating the profile would be easier.

[witch]

I get this occasionally
Maybe I am being daft - rebooting the server works for me

[NetworkGeezer]

Unfortunately on Win2K you can't change profile location in bulk [without scripting] so recreating the profile would be easier.

is

 for /f %u in (listofusers.txt) do net user %u /profilepath:\\server\share\subfolder

really so hard?

The list of users has to be a file of usernames with one per line.
If you're realy fancy you can use command subsititution of a DIR of the folder containing home directories

 for /f %u in ('dir /b E:\Users\MyDocuments') do net user %u /profilepath:\\server\share\subfolder

[ChrisH]

I thought you could get round the inability to not multiple select in 2000 by running the admin tolls of an XP work station?

[e_g_r]

Sorted - thanks guys (a generic term might i add)

[e_g_r]

Right! should not have posted that last post coz its bleedy happened again. Watching a scroat log in and out via VNC when all of a sudden the profile failed again.

WHY, any ideas? What ownership and rights should be set on the profiles folder on the server (2000).

Any ideas will prevent me from being bald.

[mark]

see here: http://technet2.microsoft.com/Window....mspx?mfr=true

[ajbritton]

@e_g_r: From your first post, it looks to me like the profile was NOT a mandatory one. Mandatory profiles have NTUSER.MAN, not NTUSER.DAT. You cannot share non-mandatory profiles between users. Either make the profile mandatory (rename NTUSER.DAT to NTUSER.MAN) or give users individual roaming profiles. (See the wiki for further details)

[e_g_r]

Yep they are Mandatory, got them settled down now but not sure how the permissions changed on the folder to All for the Everyone group? This seemed to allow the workstations to write the profile back to the server with .pol and changes to desktop etc. which was causeing the problem. Now re set the permissions and cross fingers seem ok.