[gptalk] Re: RSOP Reporting very slow

  • From: "Darren Mar-Elia" <darren@xxxxxxxxxx>
  • To: <gptalk@xxxxxxxxxxxxx>
  • Date: Thu, 13 Nov 2008 14:01:28 -0800


I have not seen these types of issues with RSOP and I wonder if this isn't
an artifact of TS where you have multiple users worth of RSOP data trying to
get stuffed into WMI at the same time? I generally never turn RSOP off
unless (not even sure I know how to!) but if it helps in this circumstance,
all it means is that you won't be able to run GP Results for those users.




From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Alan & Margaret
Sent: Thursday, November 13, 2008 12:35 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] RSOP Reporting very slow




I had a query from a site as to why logons were so slow. up to 25 minutes on
a terminal server when multiple users logged on. I checked the UserEnv log
(using my log reporter!) and it showed the following two entries



Time Diff




Adding File name XXXXXXXX to the Adm list.



Successfully logged registry Rsop data



Basically for a single user it took 3 minutes to write the RSOP data. They
disabled RSOP processing and logon times reduced 80%. Detailed checks of the
log show that they had thousands of registry keys being applied. It took 27
seconds to apply the registry settings and a further 170 seconds to log the
RSOP data.


I am not sure whether there is an underlying problem with why the logging
took so long, or whether it is standard for RSOP processing.


So my question is, have others seen this problem, and is there really any
need to have RSOP processing activated? Is it just easier to activate it
when you have a problem? Does any one use the RSOP processing extensively?  


Alan Cuthbertson



 Policy Management Software (Now with ADMX and Preference support):-



ADM Template Editor(Now with ADMX support):-



Policy Log Reporter - including Preference logging(Free)




Other related posts: