Very Slow Logon after SBS 2011 migration (from SBS2003)

After migration from SBS 2003 to SBS2011, all workstations take forever to boot and get to the login screen.

From Userenv.log:
USERENV(15c4.15c8) 17:14:57:269 LibMain: Process Name:  \\?\C:\WINDOWS\system32\WBEM\WMIADAP.EXE
USERENV(300.540) 17:15:18:418 ImpersonateUser: Failed to impersonate user with 5.
USERENV(300.540) 17:15:18:418 GetUserNameAndDomain Failed to impersonate user
USERENV(300.540) 17:15:18:418 ImpersonateUser: Failed to impersonate user with 5.
...
The above "waists about 5 minutes...
I followed many troubleshooting "hints" but I could not figure it out yet...

Not sure if related: I have some IIS issues (Companyweb: service unavailable/error 503)...

Also, I cannot remote to workstations (but Server remoting is ok...)  I have a feeling that this could be a GPO / certificate problem?
Any help will be appreciated :)

   
Constantine_GAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

CNS_SupportCommented:
Couple of things to try.
Disconnect the network cable and start the computer.
You could also try removing computer from the domain and then rejoining the domain.
If you have trouble finding the server, be sure to use the FQDN (fully qualified domain name)
ie not domain = domain  it should be domain = domain.local or whatever you are using for your domain.
0
Constantine_GAuthor Commented:
I removed / rejoined but still bad.  Maybe I saved a couple of minutes...  
I still see these errors in the userenv.log:

USERENV(40c.410) 10:00:14:937 GetUserDNSDomainName:  Domain name is NT Authority.  No DNS domain name available.
USERENV(740.220) 10:00:14:953 GetProfileType:  Profile already loaded.
USERENV(740.220) 10:00:14:953 GetProfileType: ProfileFlags is 0
USERENV(740.220) 10:00:14:953 ImpersonateUser: Failed to impersonate user with 5.
USERENV(740.220) 10:00:14:953 GetUserNameAndDomain Failed to impersonate user
USERENV(740.220) 10:00:14:968 GetUserDNSDomainName:  Domain name is NT Authority.  No DNS domain name available.
...
USERENV(b3c.298) 10:04:37:350 GetUserDNSDomainName: Failed to impersonate user
USERENV(134c.1350) 10:04:38:131 LibMain: Process Name:  C:\WINDOWS\system32\wbem\unsecapp.exe
USERENV(1368.136c) 10:04:38:209 LibMain: Process Name:  C:\WINDOWS\system32\wbem\wmiprvse.exe
USERENV(ea8.f08) 10:04:49:627 LibMain: Process Name:  C:\Program Files\Windows Home Server\WHSTrayApp.exe
USERENV(b3c.298) 10:05:37:733 ImpersonateUser: Failed to impersonate user with 5.
USERENV(b3c.298) 10:05:37:733 GetUserNameAndDomain Failed to impersonate user
USERENV(b3c.298) 10:05:37:749 ImpersonateUser: Failed to impersonate user with 5.
USERENV(b3c.298) 10:05:37:749 GetUserDNSDomainName: Failed to impersonate user
USERENV(b3c.298) 10:05:37:749 ImpersonateUser: Failed to impersonate user with 5.
...
0
Constantine_GAuthor Commented:
Am I the only one with this problem?  (I am sure not...)  Any clues?

Thanks
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Constantine_GAuthor Commented:
Looking at the logs again:  This is a laptop that at work connects to the new server (SBS2011) and at home it connects to a home server.  Could this be a conflict? (But it used to be ok with the old SBS2003 Server at work...).
 
0
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
I've requested that this question be deleted for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
Constantine_GAuthor Commented:
•      I disabled Windows SBS CSE Policy (not CES as mentioned above), I set the maximum time for Group Policy scripts to "not configured", I forced an update of the policy, rebooted the workstation and:
Workstation started /I saw the login screen in less than 30 seconds!!!!!!!!!!!!!
I really suspected that there is a "trust issue" running the scripts on the workstations OR there is a setting altered on the workstations that donot allow vbs scripts at all!
Using notepad I created a test.vbs file on the desktop. Right click, check "Open with": check what options are selected. Microsoft® Windows Based Script Hostshould be Bold (selected) as the program we need to run the vb scripts.
In my case it was not: I looked around and I saw a similar posting. What settings were "altered or damaged" in the registry and vb scripts could not run? I found theWin XP registry settings from http://www.dougknox.com/xp/fileassoc/xp_vbs_file_association.zip (WARNING: NOTsure if these apply to other OS's)
1) on the workstation: Merged the above settings to the registry,
2) On the SBS server: Restored the default GPO to run the vbscripts on the SBS clients
3) on the workstation, a cmd window I forced (c:\gpupdate /force)
4) on the workstation, I verified that the .vbs files run with Microsoft® Windows Based Script Host(Right click a "test.vbs" file (could be an empty file) > open with> choose program> Under "other programs" is "Microsoft ® Windows Based Script Host" listed?
Choose it> checkmark "always use this program to open this type of file"> then hit OK)
Restarted the workstation. It connected to the network, run the scripts and I got login screen in45 seconds!
PS: Someone told me that in some workstations they had installed System Mechanic (IOLO). I looked around and I found out that this software disables the ability to run vb scripts as this could be a "security threat" to the system... This statement is true but it caused me a lot of headackes... The computers are made to run programs! What good are they if they cannot run programs??? You just need to be carefull to run programs that are trusted... ;)
THANKS EVERYONE FOR THE HELP!!!!!!!!!!!!!!!!!!!
________________________________________
Constantine
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Constantine_GAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for Constantine_G's comment http:/Q_26941759.html#37003811

for the following reason:

This worked...  It might help others with same problems.
0
Constantine_GAuthor Commented:
This worked...  It might help others with same problems
0
PAQ_ManCommented:
Restarting the process on behalf of the author.
0
Constantine_GAuthor Commented:
PAQ_Man
Sorry but I do not really understand how this works...  I figured that if you close it then no-one can see the answer?  
My intend was to provide the solution so other people can see it...
Thanks
CG
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.