Numerous errors with domain admin profile registry settings on domain computers
Hello guys! I've faced an awful bug. I am a domain administrator and I have to login remotly or interactive to all of domain workstations. They all are running Windows 7 Pro 64 bit. And sometimes I just cannot login, for example when I open PowerShell session to remote workstation I get an error that says it cannot be opened. I've found the reason why this happens. Every user has a profile and information about this profile is stored in registry in HKLM\Software\Microsoft\WindowsNT\CurrentVersion\ProfileList. This branch has some entries named after users ID. And I've found that my original entry S-1-5-21-3813813793-1773182282-2394712197-1103 was renamed with S-1-5-21-3813813793-1773182282-2394712197-1103.bak and a new entry with my ID was created with ProfileImagePath=c:\TEMP. So I wasn't able to login. And this happens with most workstations in my domain, and therefore I cannot use PowerShell scripts that perform some actions on all domain computers, and of course I can't perform administrative tasks interactively. If someone has solved this bug or has an idea what to do - please let me know - that's a HUGE issue! Thanks in advance!
September 27th, 2011 3:25pm

So which error do you get if you try to launch PowerShell? I remember one error, which did not allow to launch PowerShell or run PS Scripts was caused by an non existing registry key in HKCU: HKEY_CURRENT_USER\Environment. This could be the case with the temporary profile you mentioned. A corrupted profile, however can be caused by various situations. You can try to rename the appropriate registry keys (delete the new one in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList and rename the old path entry to match again) or delete the profile in total and logon locally one more time. If you have cloned your workstations with a broken profile, this can be a reason. Best greetings from Germany Olaf
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2011 8:40am

Hi, Did this issue occur with all the Windows 7 client? Did they use roman profile? According to your description, the issue may appear when you use PowerShell session. I suggest to contact Windows Server Forum for further help: http://social.technet.microsoft.com/Forums/en-US/category/windowsserver The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding. Regards, Leo Huang Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
September 29th, 2011 10:03am

Thanks for reply, Leo! Yeah, this bug might be related to PowerShell, but it doesn't occures on Windows Server hosts, it's only about Windows 7. I think user profiles (in my case - domain administrator profile) are part of Windows security subsystem, so I posted this here. Dmitriy Titov
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2011 10:37am

Thanks for reply, Olaf! It took me two weeks to response, sorry. So, yes, I can rename that registry branch and it does solve the problem but just for a while. I didn't clone workstations and my profile was ok. So that's not a solution, it could fix the problem for now on particular workstation but it doesn't solve the whole problem. The main idea of my question was to ask profi about the reason why this could happen, understanding the reason is the only way to find robust solution. But again, thanks!
October 6th, 2011 5:15am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics