G
Guest
Hello
Serveral day ago I had two errors in Application event, 1065 (userEnv) and
1030. When I remove a WMI filter from infected GP policy (which is wrote in
1065 error), every policies applied again. But from that time I can't use WMI
filter on Policies.
On comps application event is error number 1090, source Userenv and desc:
Windows couldn't log the RSoP (Resultant Set of Policies) session status. An
attempt to connect to WMI failed. No more RSoP logging will be done for this
application of policy.
I found two solution but non of them help
First:
cd %windir%\system32
regsvr32 /n /I userenv.dll
cd wbem
mofcomp scersop.mof
gpupdate /force
Reboot
Second:
cd %windir%\system32\wbem\repository
net stop winmgmt
del * /s /q
regsvr32 wbemupgd.dll.
Error 1090 is still in application events on all computers (Win XP SP2, W2k3
domain)
Thank you for help
Slavek
Serveral day ago I had two errors in Application event, 1065 (userEnv) and
1030. When I remove a WMI filter from infected GP policy (which is wrote in
1065 error), every policies applied again. But from that time I can't use WMI
filter on Policies.
On comps application event is error number 1090, source Userenv and desc:
Windows couldn't log the RSoP (Resultant Set of Policies) session status. An
attempt to connect to WMI failed. No more RSoP logging will be done for this
application of policy.
I found two solution but non of them help
First:
cd %windir%\system32
regsvr32 /n /I userenv.dll
cd wbem
mofcomp scersop.mof
gpupdate /force
Reboot
Second:
cd %windir%\system32\wbem\repository
net stop winmgmt
del * /s /q
regsvr32 wbemupgd.dll.
Error 1090 is still in application events on all computers (Win XP SP2, W2k3
domain)
Thank you for help
Slavek