Logging onto a TS with no user profile folder

Nikumba · 13 Sep 2012 at 09:39

Bit of a strange one this and really can not understand it.

We have windows 2003 terminal server with 20 odd users on it all working happily away with roaming profiles that are kept in their user drives on the file server.

However a new user who is having problems is they are logging onto the TS, no errors come up but no user profile is created in docs & settings and nor is any data copied to his roaming profile on log off.

Anyone have any idea where I can start to look?

Cheers

Kimbie

Hellsmk2 · 13 Sep 2012 at 13:33

Check ad u&c to see for mistakes in profile path.

If it is set via gp, run gpresult and ensure policy is applied. Gpresult will also list the roaming profile path that is in use (near the top of the results).

If that fails, check permissions on the users docs folder.

Have to say, absolutely not a fan of storing profiles in users doc folder. That's just asking for trouble.

Nikumba · 13 Sep 2012 at 13:35

Hellsmk2 said:
Check ad u&c to see for mistakes in profile path.

If it is set via gp, run gpresult and ensure policy is applied. Gpresult will also list the roaming profile path that is in use (near the top of the results).

If that fails, check permissions on the users docs folder.

Have to say, absolutely not a fan of storing profiles in users doc folder. That's just asking for trouble.

The profile paths are set by us in AD not via GP

Permissions all look fine as well, its the fact on the TS its not creating a user folder is baffling the hell out of me.

When we consolidate our fileservers we are going to move roaming profiles into a different share.

Kimbie

SoundsGood · 13 Sep 2012 at 19:53

Have you tried recreating his profile on the server?

Hellsmk2 · 13 Sep 2012 at 22:46

Nikumba said:
The profile paths are set by us in AD not via GP

Permissions all look fine as well, its the fact on the TS its not creating a user folder is baffling the hell out of me.

When we consolidate our fileservers we are going to move roaming profiles into a different share.

Kimbie

Have you checked gpresult against the user? That should at least give a clue as to if they're getting a roaming profile, and if so, where it's pointing to.

mrbios · 13 Sep 2012 at 23:47

Nikumba said:
The profile paths are set by us in AD not via GP

Permissions all look fine as well, its the fact on the TS its not creating a user folder is baffling the hell out of me.

When we consolidate our fileservers we are going to move roaming profiles into a different share.

Kimbie

On top of checking the profile path in AD make sure you don't have a different or incorrect one specified in the terminal services tab of his AD profile (and if you don't even use that part of AD make sure no ones typed something in by accident)

Catanonia · 16 Sep 2012 at 15:53

As said, check profile path and remote profile path tabs in AD users and computers for the user.

Also check you have no GPO's applied to the AD OU that can be overriding the AD settings.

Create a new user from scratch in AD and set the path and click apply. Are the directories created for the user where the profile is supposed to be stored.