[gptalk] Re: RSOP Reporting very slow
- From: "Cruz, Jerome L" <jerome.l.cruz@xxxxxxxxxx>
- To: "gptalk@xxxxxxxxxxxxx" <gptalk@xxxxxxxxxxxxx>
- Date: Thu, 13 Nov 2008 16:50:51 -0800
Alan,
Is there any chance that the systems involved are using GPPE settings?
Microsoft just released a KB article describing "Long User Logons" on WTS
servers if GPPE settings (with the removal history checkbox setting checked)
were being applied. This is a guess totally out of the blue, but perhaps this
is another artifact involved when "history" settings for GPPEs are engaged.
Here's the reference:
Feed: KBs-Win2K3
Posted on: Wednesday, November 12, 2008 11:20 PM
Author: Most Recent KBs for Windows Server 2003
Subject: It takes longer to log on to a Windows Server 2003-based terminal
server than expected when you enable Group Policy preferences in the terminal
server
View
article...<http://support.microsoft.com/default.aspx?scid=kb;en-us;955457&sd=rss&spid=3198>
Jerry Cruz | Group Policies Product Manager | Windows Infrastructure
Architecture | Boeing IT
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Darren Mar-Elia
Sent: Thursday, November 13, 2008 2:01 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: RSOP Reporting very slow
Alan-
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.
Darren
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
Hi,
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
Time Diff
text
16:08:07:604
29.152
Adding File name XXXXXXXX to the Adm list.
16:10:50:391
191.939
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):-
http://www.sysprosoft.com/index.php?ref=activedir&f=pol_summary.shtml
ADM Template Editor(Now with ADMX support):-
http://www.sysprosoft.com/index.php?ref=activedir&f=adm_summary.shtml
Policy Log Reporter - including Preference logging(Free)
http://www.sysprosoft.com/index.php?ref=activedir&f=policyreporter.shtml
Other related posts:
