Microsoft
Software
Hardware
Network
Question : How to diagnose long logoff times?
Recently I converted our DC from a Server Core install to a regular (full) installation. That is, I set up a brand new DC and shipped over all the roles, then demoted the Server Core DC and removed it from the domain. Since then, our logoff times have increased dramatically, to just under 10 minutes. The only 2 hints I'm seeing are these entries in the application event log:
The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (EndShell).
The winlogon notification subscriber <GPClient> took 600 second(s) to handle the notification event (EndShell).
Googling these didn't yield much - most answers were relevant to wireless networks, which doesn't apply here.
Clients are Win7, with 2008R2 DC. Any suggestions?
Answer : How to diagnose long logoff times?
well there are a couple of ways but i would say use powercli from vmware to update vmtools
see
http://get-admin.com/blog/
?p=714
Random Solutions
How do I print to a CString?
How to remove new line from a string
Oracle Error "To many precesion Specifiers"
Crystal connection with OLE DB ADO
XSLT Parsing pairs of xml tags
My.Application.Log.WriteEn
try is Not Writing to App Log
Which KEY do I use for my KMS Server and clients?
Optimize Javascript and CSS
Adding 2nd domain controller (Server 2008 R2 64bit) to existing 2003 sp2 domain
Browser Hijack