Roaming Profiles - Black background and Group Policies

[RobD]

Hi All,

 

We have a annoying issue where when users logout their roaming profile is not deleted properly meaning when they logon again they get:

 

Username.Domain

 

And if it happens again they get numbers after the domain, the problem seems to be the profile has active files open meaning it cant be deleted so when they logon again the second profile is created and the users personal background goes black (yes they wont let me roll out desktop backgrounds) and they moan.

 

Everything except app data is redirected so really this only affects a few app data things but its really annoying me, I've tried to fix it by using a delprof2.exe script on PC boot but the problem still seems to be floating around (probably because staff never reboot PC's just logout). If I disable "Delete cached copies of roaming profiles" do you think I'll run into more different issues?

 

Any help would be great.

 

Thanks

[RobD]

No one?

[danmoly]

We get the same issue. As you say active files still open that prevent the deletion of the local files. Very annoying. We only found setting the desktop via registry works the black background fix, but annoying you can't set their desktops!

 

Sorry not much help, but I feel your pain!

[RobD]

Thanks for the reply @danmoly, whats the reg change you implement? I dont mind the .domain thing if they dont notice the wallpaper.

[themightymrp]

We have a similar problem with roaming profiles not always deleting and ending up with a bunch of username.domain.00x profiles in the c:\users folder. Never managed to find out what causes it so have just grown to live with it. I'd love a solution though if anyone has it?

[teejay]

Check you have the 'Always Wait for Network at startup and login' machine group policy set.

[themightymrp]

We have that set already :-/

[teejay]

Try setting the following reg keys (just do this on a test PC first):

 

regsetting: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon "GpNetworkStartTimeoutPolicyValue"=dword:00000019

regsetting: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters "DisableDHCPMediaSense"=dword:00000001

 

This problem usually occurs because the PC is failing to load the remote profile in time and so creates a new one. You also want to look if it's a loading issue on your servers or a network config issue, check with something like wireshark to see if your network is getting swamped with broadcast traffic etc (misbehaving printers are a common cause). Also, check your DNS and DHCP are working properly.

[danmoly]

@RobD

 

Just deployed via GP, update reg key of HKEY Current User\Control\Desktop\Wallpaper, type REG_SZ value pointing at the default Win 7 background for us -> C:\Windows\Web\Wallpaper\Windows\img0.jpg. It should work pointing to a network location, but haven't completely tested that.

 

Profiles may still be having issues somewhere but nothing we've noticed or taken any impact on. This just fixes that darn black wallpaper!

[RobD]

Thanks @danmoly I've just deployed this via a registry GPO which works like a charm:

 

Key: HKEY Current User\Control\Desktop\Wallpaper, type

Value: REG_SZ

Value: \\ProfileServer\Staff_profiles_Share\%username%.v2\appdata\roaming\microsoft\windows\themes\TranscodedWallpaper.jpg

 

(the above value allows user to have their personal wallpaper even if their profile has gone pair shaped on their PC).

[danmoly]

No worries buddy, glad to help!

 

Good idea on pointing it to their own profiles!

[WingDing]

Do you really want the help of a WingDing?