Another roaming profile issue 1

[aristos]

Okay. I've searched the forums and haven't seen an issue that was like the one we're experiencing here.

We have an existing farm that works just fine. Everyone can log on, no problems.

I've built 4 new farm servers and some people can log on, some people can't. The ones that *can't* log in get the following error:

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.

Then they get:
Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.

We have roaming profiles stored on //server1/userprofiles.
We're running MetaFrame XPe 1.0, FR2, SP2 on Win2kServer SP3.

Now, we switched domains some time ago and the people who are having problems *appear* to be those whose profiles were used in the old domain.

Looking for places to go poke around...

Thanks!

Mike
Will BF1942 for food...

 

[pgaliardo]

The answer seems to be right there in the message. Make sure the user in question is the owner of his profile folder and has full control to the folder.

 

[aristos]

Thanks for the pointer, but we already did that. The user *is* the owner. Administrator can't touch the folders.

And it's strange because the users that are having problems can log into the existing farm machines - but not the new ones.

Oh, one more piece of info: These servers are ghosted from an existing working install.

On server \\t14, which is on another farm, the users who have problems can log in just fine. On the new servers on the primary site, they cannot.

Still lookin'

Mike
Will BF1942 for food...

 

[pgaliardo]

OK - I see, I misread your post. These users can log onto the farm fine on certain servers. Then my solution wouldn't be valid. How about the rights on the new servers? Roaming profiles need to be written to C:\Documents and Settings
Do these users have the appropriate rights to write to the directory?

 

[aristos]

We've got a group (mac) that has read & Execute priveleges to the directory. It's the same setup that we've got on our production servers. They don't have write access, but do they need it? When the system creates the profile folder, they have write access to that profile folder.

If we create a new profile for the users, then they can log in fine. But we're not looking forward to creating maybe 200-300 new profiles.

Mike
Will BF1942 for food...

 

[tk36]

You mentioned 'switched domains'
Does this mean the users, instead of logging in as say OldDomain\user1 will have to log in as NewDomain\user1?

If this is the case, the server will in fact take this as 2 different users. Have you given permission to NewDomain\User1 over the old Profile folder of OldDomain\user1?

Just the thought.

Ta

 

[aristos]

Well, we finally figured it out.

It did indeed have to do with folder ownership and here's how it played out:

We looked at the permissions of someone who was having issues logging in. Sounds simpler than it really was, because we as admins don't have rights to the user folders(it's a company thing...). So, we had to wait until the user was off of his phone call (we're a call center).

We looked at the permissions on his folder and, lo and behold, the owner was a string of letters and numbers (the SID from the previous domain). We had him take owner of the folder with his *current* log in and then he was able to access the new server sans probleme!

So, my thanks for the places to look. tk36, you were right - we just fixed it before you posted. But you get a gold... err... purple star anyway for being right.


Mike
Will BF1942 for food...

 

[tk36]

Wow Thanks so much

Well done !

Ta