Application log shows:
* Application [Wuser32.exe]. The application was started while the service manager was locked and NtLmSsp wasn't running. If the application will try to remote via WinSock Proxy it can cause a deadlock with the service manager. For this reason the remoting is disabled. If the application is a service, and you want it to be able to remote, make it dependent on NtLmSsp.
* Application [MSTask.exe]. The application was started while the service manager was locked and NtLmSsp wasn't running. If the application will try to remote via WinSock Proxy it can cause a deadlock with the service manager. For this reason the remoting is disabled. If the application is a service, and you want it to be able to remote, make it dependent on NtLmSsp.
* Application [SavRoam.exe]. The application was started while the service manager was locked and NtLmSsp wasn't running. If the application will try to remote via WinSock Proxy it can cause a deadlock with the service manager. For this reason the remoting is disabled. If the application is a service, and you want it to be able to remote, make it dependent on NtLmSsp.
* Application [mnmsrvc.exe]. The application was started while the service manager was locked and NtLmSsp wasn't running. If the application will try to remote via WinSock Proxy it can cause a deadlock with the service manager. For this reason the remoting is disabled. If the application is a service, and you want it to be able to remote, make it dependent on NtLmSsp.
* Application [lsass.exe]. The application was started while the service manager was locked and NtLmSsp wasn't running. If the application will try to remote via WinSock Proxy it can cause a deadlock with the service manager. For this reason the remoting is disabled. If the application is a service, and you want it to be able to remote, make it dependent on NtLmSsp.
* Application [svchost.exe]. The application was started while the service manager was locked and NtLmSsp wasn't running. If the application will try to remote via WinSock Proxy it can cause a deadlock with the service manager. For this reason the remoting is disabled. If the application is a service, and you want it to be able to remote, make it dependent on NtLmSsp.
*Security policy in the Group policy objects are applied successfully.
I have not been able to open it.
Thanks.