Windows Server 2008 Long Boot Time - The winlogon notification subscriber <GPClient> took 505 second(s) to handle the notification event (CreateSession).

Lately, not sure why, but when booting up my Server 2008 Domain Controller (holds all roles) It sits at "Applying computer settings" for an extremely long time and I receive the following error message in the event logs, any ideas?

The winlogon notification subscriber <GPClient> took 505 second(s) to handle the notification event (CreateSession).
LVNeptuneAsked:
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.

Darius GhassemCommented:
I had the same issue with Applying computer settings but my fix was actually configuring some settings on the NIC. If you go to your NIC Properties then go to configure then click Advanced see if the TCP Checksum, TCP Offload, and IP Checksum are disabled or enabled? Do you  have the 64-bit or 32-bit verison?
LVNeptuneAuthor Commented:
They were all enabled. I disabled them going to reboot now. I read some stuff relating to that but noone said it fixed their issue so I didn't bother...
LVNeptuneAuthor Commented:
Did not work =( back to the drawing board!
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

LVNeptuneAuthor Commented:
Also it is 64bit, running Hyper-V
LVNeptuneAuthor Commented:
Ended up resolving it myself. I don't know why but replication was broken between this machine and the VM that was a DC running GC (nothing else, moved all roles to host OS). DCPROMO'd it off, removed the entry from sites and services, rebooted the host OS and it fired right up. Not sure what caused the originating issue however.

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
Pancake_EffectCommented:
I'm having the same issue. How did oyu do your fix??

"Ended up resolving it myself. I don't know why but replication was broken between this machine and the VM that was a DC running GC (nothing else, moved all roles to host OS). DCPROMO'd it off, removed the entry from sites and services, rebooted the host OS and it fired right up. Not sure what caused the originating issue however. "

I dont know how to do that, you someone explain this in steps? thanks
JARMARCommented:
I have this same issue but am not using VM.  What are the steps to correct this?
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
Active Directory

From novice to tech pro — start learning today.