Windows 7 client takes forever to logon

[meyner22]

Not sure if anyone has seen this warning in windows but i'm getting "The winlogon notification subscriber <VMWVvpsvc> is taking long time to handle the notification event (Logon)."  And my client is taking almost 3 to 5mins to logon.  I haven't tried this with and without persistent disk and redirection of the profile using persona.  I haven't tried it with just persistent disk and no redirection.  Anyone have any ideas what would be causing this.

[marcdrinkwater]

Do you have Lync or Live Messenger installed on your Image?

Do you see any errors in the Application log pertaining to COM+?

[meyner22]

Lync and Live are not installed, pretty bare image.  The only error I see the in the application log is:

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

[gamoid]

Had to dig up this old thread. I'm facing similar issues as well and the exact same event exists on the affected machines.

Anyone has any ideas on what is going on? We have an environment of 200-250 machines and is happening randomly to 20-25 machines.

[meyner22]

Are they all running off the same image?  What version of view are you running?

[gamoid]

They are off different images. We are currently using 5.3.0 build-1427931.

[BlackBurn83]

where you able to resolve this issue, we (just) encountered the same problem

Thanks in advance

[ZeroStalin]

Hello, we have same trouble at logs... But some linked clone virtual machine doesn't update DNS records, doesn't authorize at domain controller... We doesn't see events with state error and source "netlogon" at system logs. Anybody help!!!)

[nealus]

Just a thought but in the 'physical' world, logon delay are often caused by DNS resolution issues.  No reason why this would be different in a VDI setup.  Any timeouts noted in DNS or resolution problems on the desktops?  Are they domain joined - if so, can a problem box be removed from the domain - does the issue still occur on the standalone?

[VMMalley]

could be any number of issues as other posters have said.

This could be an antivirus agent, dns, etc.

also, a corrupt persona also is something to check.

rename your current persona on your persona server, and try to log back in with same credentials and see what happens.

[ZeroStalin]

we don't have persona server... and we don't have active persona service... all at qiuck prep...

[ZeroStalin]

and standalone... We don't see error events at dc - all clear...

[maharajan_be]

Do you have persona service installed on the view desktop. Did you check if the service is running and logging into the view desktop

[MaydayIT]

We have the exact same issue cropping up here, except after the user sees the error, the system returns to the login screen.  If the user goes and does something else for a couple of minutes, he's able to log in normally.

Systems are domain-joined, and Persona Management service is disabled.  VMs are full clones with persistent disks.  We're running View 6.3.  DNS is working fine with no issues seen.  AV is System Centre Endpoint Protection.

If there's any other information I can provide, I'd be happy to!

Any help greatly appreciated.

Derek

[nettech1]

are you seeing event id 6005 in your windows application log?

https://support.microsoft.com/en-us/help/2590550/the-desktop-does-not-load-and-only-displays-a-black...

https://windowsexplored.com/2012/11/06/windows-7-black-screen-and-mouse-cursor-after-logon/