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?
 
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.
0
 
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?
0
 
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...
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
LVNeptuneAuthor Commented:
Did not work =( back to the drawing board!
0
 
LVNeptuneAuthor Commented:
Also it is 64bit, running Hyper-V
0
 
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
0
 
JARMARCommented:
I have this same issue but am not using VM.  What are the steps to correct this?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.