2008R2 DC profile issues with my XP clients

[techie2008]

Hi there, we are experiecing profile issues in our 2003 domain with our newly added 2008R2 Domain Controller.

 

Users receiving the following image when the 2008R2 DC authenticates them:

 

http://filedb.experts-exchange.com/incoming/2010/07_w28/t324554/User-Environment.jpg

 

This only happens on this DC, the other two 2003 DCs run happily without any problems.

 

Can anyone advise me what I need to do as i'm banging my head at the wall at the moment

 

NB: This is the first DC to move from 2003 to 2008R2.

 

Regards

 

Simon

[sted]

usually means if you check the docs and settings folder on the pcs hdd you will find lots of user user.domain user.domain.000 ..... user.domain.999

 

try logging onto a pc as admin and emotying the docs and settings folder of stale profiles

[sven]

So am I right in assuming that the profiles themselves have not changed location/permissions?

[sted]

So am I right in assuming that the profiles themselves have not changed location/permissions?

 

they just dont get deleted on logoff like they should and then when the same user tried to logon its still there and they cant create a new one so somputer says no

[techie2008]

Thank you for your responses.

 

Sted, if this is what is causing the problem could I do something remotely as I have 500 clients in my environment.

 

Why would this only happen on my 2008R2 DC and work fine on the 2003 ones?

[sted]

no idea i have a script i use but try it first as its a sledgehammer to crack a nut solution

[techie2008]

Can anyone on here kindly explain why this would be happening? I don't really fance going to every PC delelting certain docs and settings folders

[sted]

iirc windows dosent close the registry in a timely fashion so when user logs off the hive is still open so the folder cant be deleted

 

SOMETIMES installing the user hive cleanup tools helps

[mthomas08]

I have a 2008 DC and no issues there, as for 2008 R2 DC.. not done that one yet.

 

Would be interesting to know why it is occuring, I have nothing to test our R2 version because we got the x64 version, only one of our boxes has that and that is a virtual box.

 

If it is happening on every PC, perhaps start the profile creation process again? It is what I would do.

 

Make sure the shared path is working okay as well.

[Richie1972]

Yes sometimes the user hive tool works. I think it might also be related to anti-virus or print spooler issues that prevent all the local user settings from being deleted

[DMcCoy]

Where are the profiles stored? Hopefully not on sysvol or a dfs share.

[Richie1972]

Hmmm, DFS for profile storage? Yes I seem to remember getting my fingers burnt with that one a while back.

I have Unlocker installed on the XP computers and I have, on occasion, attempted to delete the "offending" profile folder only to be told that the spooler has the file open

[sukh]

@Techie2008 - How sure are you that this issue only occurs when users autheticate against the 2008R2DC? What makes you believe this?

 

Are there any errors in the Event Log on the client or 2008R2 Server?

 

If you pick one user are you able to recreate the issue?

 

Can you enable client side logging and reproduce the issue.

 

On an affected client computer, use Registry Editor to add the following registry value (or modify it, if the value already exists):

 

Value Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

 

Value Name: UserEnvDebugLevel

 

Value Type: REG_DWORD

 

Value Data: 10002 (Hexadecimal)

 

Can you collect the logs and post/PM? (%SystemRoot%\Debug\UserMode\Userenv.log)

 

Sukh

Edited April 5, 2011 by sukh
Also confirm where the user profiles are stored? I.e DFS which includes the 2008 DC or not?

[SYNACK]

Whats the issue with DFS?

[Richie1972]

The problem with DFS for profile shares when you roaming profiles is hat the user can logoff one machine and logon to another before the data has replicated to another server (unless you speficy a preferred server)

[SYNACK]

The problem with DFS for profile shares when you roaming profiles is hat the user can logoff one machine and logon to another before the data has replicated to another server (unless you speficy a preferred server)

 

Oh, thats assuming replication not just redirection which makes sense.

[Richie1972]

I rarely think of the two separately, which is probably why I don't use DFS as much as I should

[oxide54]

i don't use it for replication, i just use it so as the shares aren't tied to server names,