Can you follow up to the list Ron if that works as this is definitely
something we need to write a tip on.
Jim
Ron Oglesby wrote:
Hmmm. Good one. Let me try that.
------------------------------------------------------------------------
*From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On Behalf Of *Shonk, Joe - Perot
*Sent:* Wednesday, September 15, 2004 10:34 AM
*To:* thin@xxxxxxxxxxxxx
*Subject:* [THIN] Re: FYI Smartstart and app launch times
Could you turn off parsing of the autoexec file?
The key is: MyComputer\HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Value: ParseAutoexec
Set the value to 0
Joe
------------------------------------------------------------------------
*From:* Ron Oglesby [mailto:Roglesby@xxxxxxxxxxxx] *Sent:* Tuesday, September 14, 2004 6:27 PM *To:* thin@xxxxxxxxxxxxx *Subject:* [THIN] FYI Smartstart and app launch times
OK, Myself and another participant on the list (jeff Matheis) have figured out something interesting.
At his location and another client they were experiencing some “slow” launch times. Slow being relative and being between 18 seconds and 30 with an explicit app and on the first connection. In both locations the Servers were HP servers built with Smart start (or at least smartstart then imaged). Anyway in both sites we ran a winlogon debug and noted the same thing, a 9-12 second delay in the logon process where Autoexec.bat was attempting to be processed.
In both cases the smartstart builds left the autoexec.bat off the system (not like you need it right) anyway, by placing an empty autoexec.bat out there for processing we dropped about 10 seconds off of the app launch time. In my recent client this got our anonymous apps down to 4-5 seconds and our domain explicit logins down to 7 - 9.
Just an FYI for the list. Another of those untold number of little things we have to do to make it “right”
Ron Oglesby
Senior Technical Architect
Microsoft MVP - Windows Server Technologies
RapidApp, Chicago
Mobile: 815 325 7618
