Sorry, I had a very blonde moment when I saw "slow logons" and thought W2K SP4. ...Chris -----Original Message----- From: Schneider, Chad M. [mailto:CMSchneider@xxxxxxxxx] Sent: Thursday, 28 August 2003 11:50 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: Post MF SP3 slow logons.... Differing issue, as I do not have M$ SP4 on any servers. This issue is strictly post MF SP3. -----Original Message----- From: Chris Coleman [mailto:Chris.Coleman@xxxxxxxxxx] Sent: Wednesday, August 27, 2003 7:31 PM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: Post MF SP3 slow logons.... Microsoft have released a hotfix to address this issue - http://support.microsoft.com/?kbid=824309 <http://support.microsoft.com/?kbid=824309> I haven't had a chance yet to test it though. ...Chris -----Original Message----- From: Schneider, Chad M. [mailto:CMSchneider@xxxxxxxxx] Sent: Wednesday, 27 August 2003 4:00 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Post MF SP3 slow logons.... Interesting. _____ From: Andy Lalaguna [mailto:Andy.lalaguna@xxxxxxxxxxxx] Sent: Tuesday, August 26, 2003 1:06 PM To: thin@xxxxxxxxxxxxx Something else to add to the discussion. Perhaps more petrol on the fire. I have been exploring this with a customer, for some time, and he discovered this. Comments? AndyL http://support.microsoft.com/default.aspx?kbid=324446 <http://support.microsoft.com/default.aspx?kbid=324446> Terminal Server and Connected Terminal Services Clients Pause When a Terminal Services Client Logs On or Logs Off The information in this article applies to: * Microsoft Windows 2000 Advanced Server SP3 * Microsoft Windows 2000 Server SP3 This article was previously published under Q324446 SYMPTOMS When a Terminal Services client logs on or logs off (either in a session or on the console of the Terminal server), the Windows 2000-based Terminal server together with the connected Terminal Services client computers may stop responding or may pause for several seconds. Users may also experience one or more of the follow symptoms: * When a user types in a document, characters do not appear on the screen until this pause has ended. * Keyboard input and mouse input are queued, but they are not processed until this pause has ended. * Live performance monitoring (Perfmon) graphs have missing data points during this pause. * All running programs appear to stop responding, or "hang," during this pause. * When Spooler is under a load from a large number of users, a high CPU usage is displayed for it. CAUSE This problem may occur if there is a contention among server resources. The contention causes a delay in processing that appears as a pause or as unresponsiveness. RESOLUTION Hotfix Information A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this fix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: <http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS> http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. Prerequisites Windows 2000 Service Pack 3 (SP3) or later is required to install this hotfix. For additional information about how to obtain the latest Windows 2000 service pack, click the following article number to view the article in the Microsoft Knowledge Base: <http://support.microsoft.com/default.aspx?scid=kb;EN-US;260910> 260910 How to Obtain the Latest Windows 2000 Service Pack Restart Requirement You must restart your computer after you apply this hotfix. File Information The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name -------------------------------------------------------------- 29-May-2003 00:11 5.0.2195.6748 124,688 Adsldp.dll 29-May-2003 00:11 5.0.2195.6748 132,368 Adsldpc.dll 29-May-2003 00:11 5.0.2195.6748 63,760 Adsmsext.dll 29-May-2003 00:11 5.0.2195.6743 381,200 Advapi32.dll 29-May-2003 00:05 5.0.2195.6738 42,256 Basesrv.dll 29-May-2003 00:11 5.0.2195.6693 68,880 Browser.dll 14-Apr-2003 20:53 5.0.2195.6736 35,856 Classpnp.sys 17-Jan-2003 16:06 5.0.2195.6656 236,304 Cmd.exe 15-Jan-2003 19:43 5.0.2195.6655 30,768 Disk.sys 29-May-2003 00:11 5.0.2195.6680 134,928 Dnsapi.dll 29-May-2003 00:11 5.0.2195.6663 92,432 Dnsrslvr.dll 29-May-2003 00:11 5.0.2195.6700 47,376 Eventlog.dll 05-Apr-2003 00:10 5.0.3700.6690 243,472 Explorer.exe 29-May-2003 00:05 5.0.2195.6660 233,232 Gdi32.dll 29-May-2003 00:11 5.0.2195.6747 148,240 Kdcsvc.dll 20-May-2003 18:49 5.0.2195.6747 205,072 Kerberos.dll 29-May-2003 00:05 5.0.2195.6741 711,440 Kernel32.dll 26-Mar-2003 21:37 5.0.2195.6695 71,888 Ksecdd.sys 29-May-2003 00:11 5.0.2195.6749 252,176 Localspl.dll 28-May-2003 20:39 5.0.2195.6749 509,712 Lsasrv.dll 28-May-2003 20:39 5.0.2195.6749 33,552 Lsass.exe 04-Feb-2003 20:15 5.0.2195.6661 29,264 Mountmgr.sys 26-May-2003 19:35 5.0.2195.6748 407,792 Mrxsmb.sys 29-May-2003 00:05 5.0.2195.6746 333,072 Msgina.dll 05-Apr-2003 00:12 5.0.2195.6680 117,520 Msv1_0.dll 29-May-2003 00:11 5.0.2195.6601 311,568 Netapi32.dll 29-May-2003 00:11 5.0.2195.6695 371,984 Netlogon.dll 29-May-2003 00:05 5.0.2195.6741 483,600 Ntdll.dll 29-May-2003 00:11 5.0.2195.6697 1,040,144 Ntdsa.dll 26-May-2003 19:33 5.0.2195.6748 1,695,232 Ntkrnlmp.exe 26-May-2003 19:33 5.0.2195.6748 1,694,272 Ntkrnlpa.exe 26-May-2003 19:33 5.0.2195.6748 1,715,200 Ntkrpamp.exe 26-May-2003 19:33 5.0.2195.6748 1,672,768 Ntoskrnl.exe 29-May-2003 00:11 5.0.2195.6745 66,320 Ntprint.dll 29-May-2003 00:11 5.0.2195.6692 994,064 Ole32.dll 29-May-2003 00:11 5.0.2195.6745 381,712 Printui.dll 26-May-2003 19:35 5.0.2195.6748 168,208 Rdbss.sys 08-Apr-2003 05:54 5.0.2195.6701 90,232 Rdpwd.sys 29-May-2003 00:11 5.0.2195.6742 432,400 Rpcrt4.dll 29-May-2003 00:11 5.0.2195.6702 187,664 Rpcss.dll 29-May-2003 00:11 5.0.2195.6742 392,464 Samsrv.dll 29-May-2003 00:11 5.0.2195.6737 131,344 Scecli.dll 29-May-2003 00:11 5.0.2195.6737 306,448 Scesrv.dll 29-May-2003 00:05 5.0.3700.6737 2,356,496 Shell32.dll 21-May-2003 18:47 5.0.2195.6746 4,554,240 Sp3res.dll 29-May-2003 00:11 5.0.2195.6741 80,656 Spoolss.dll 29-May-2003 00:05 5.0.2195.6684 11,536 Usbmon.dll 29-May-2003 00:05 5.0.2195.6688 403,216 User32.dll 29-May-2003 00:05 5.0.2195.6745 385,808 Userenv.dll 29-May-2003 00:11 5.0.2195.6601 51,472 W32time.dll 16-Aug-2002 13:32 5.0.2195.6601 57,104 W32tm.exe 29-Apr-2003 17:44 5.0.2195.6742 1,628,784 Win32k.sys 29-May-2003 00:11 5.0.2195.6681 97,040 Win32spl.dll 28-May-2003 20:57 5.0.2195.6749 181,520 Winlogon.exe 29-May-2003 00:11 5.0.2195.6659 113,936 Winspool.drv 29-May-2003 00:05 5.0.2195.6699 252,176 Winsrv.dll 29-May-2003 00:11 5.0.2195.6741 126,224 Wldap32.dll 29-May-2003 00:11 5.0.2195.6738 57,104 Wlnotify.dll 29-May-2003 00:11 5.0.2195.6741 711,440 Kernel32.dll 29-May-2003 00:11 5.0.2195.6741 483,600 Ntdll.dll 29-May-2003 00:11 5.0.2195.6742 1,628,784 Win32k.sys 29-May-2003 00:05 5.0.2195.6699 252,176 Winsrv.dll STATUS Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION To install the hotfix that is described in this article, the Terminal server must be running Windows 2000 Service Pack 3 (SP3) or later. After you install the hotfix and restart the computer, you must turn on the Power Protect write cache option for each hard disk that has write caching enabled and that has its write cache protected against accidental loss of power. To configure the Power Protect option, use the Dskcache.exe tool. For additional information about how to obtain the Dskcache.exe tool and how to use it to configure the Power Protect write cache option, click the following article number to view the article in the Microsoft Knowledge Base: <http://support.microsoft.com/default.aspx?scid=kb;EN-US;811392> 811392 Obtain the Dskcache.exe Tool to Configure the "Power Protected" Write Cache Option When you run Dskcache.exe without any parameters, the current write cache settings for all hard disks are displayed. For each hard disk that is currently installed on your computer, the following information is displayed: Disk device: \\?\\<SCSI DEVICE ID> Current Settings: Write Cache is [ enabled | disabled ] Power Protect is [ enabled | disabled ] To turn on the Power Protect option on a hard disk, use the p command-line switch. For example, to turn on the Power Protect option on drive C, type the following line at the command prompt, and then press ENTER: dskcache +p c: The following information is displayed for drive C: Disk device: \\?\\<SCSI DEVICE ID> Current Settings: Write Cache is enabled Power Protect is disabled New Settings: Write Cache is enabled Power Protect is enabled Note You can turn on the Power Protect write cache option only for disks that are currently present on your computer. By default, the Power Protect option is turned off. As a result, this option is turned off for any hard disks that are added to the computer after you apply this setting. When you add additional hard disks, you must turn on the Power Protect option for those disks if you want the setting to apply to those disks. You must also configure the following registry subkeys on the Terminal server: * In the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters subkey, configure the following entries: * Name: MaxWorkItems Data Type: REG_DWORD Value data: 16384 (decimal) * Name: MaxMpxCt Data Type: REG_DWORD Value data: 2048 (decimal) * Name: MaxRawWorkItems Data Type: REG_DWORD Value data: 512 (decimal) * Name: MaxFreeConnections Data Type: REG_DWORD Value data: 100 (decimal) * Name: MinFreeConnections Data Type: REG_DWORD Value data: 32 (decimal) * In the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanworkstation\Param eters subkey, configure the following entry: * Name: MaxCmds Data Type: REG_DWORD Value data: 2048 (decimal) * In the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Configuration Manager subkey, configure the following entry: * Name: RegistryLazyFlushInterval Data Type: REG_DWORD Value data: 60 (decimal) If you use a file server to share data, use roaming profiles, or redirect home folders for Terminal Services users. Configure the following registry subkeys on all file servers: * In the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters subkey, configure the following entries: * Name: MaxWorkItems Data Type: REG_DWORD Value data: 16384 (decimal) * Name: MaxMpxCt Data Type: REG_DWORD Value data: 2048 (decimal) * Name: MaxRawWorkItems Data Type: REG_DWORD Value data: 512 (decimal) * Name: MaxFreeConnections Data Type: REG_DWORD Value data: 100 (decimal) * Name: MinFreeConnections Data Type: REG_DWORD Value data: 32 (decimal) For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base: <http://support.microsoft.com/default.aspx?scid=kb;EN-US;816915> 816915 New Naming Schema for Microsoft Windows Hotfix Packages -----Original Message----- From: Schneider, Chad M. [mailto:CMSchneider@xxxxxxxxx] Sent: 26 August 2003 19:01 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Post MF SP3 slow logons.... Sure seemed to be. Even with RDP, the script was running synchronous. I just confirmed, connected to fixed server 42, with RDP, and the script ran asynch. _____ From: Ryan Lambert [mailto:rlambert@xxxxxxxxxxxxxxx] Sent: Tuesday, August 26, 2003 12:47 PM To: thin@xxxxxxxxxxxxx Chad, Just curious. You said this was affecting RDP connections as well. From: Schneider, Chad M. [mailto:CMSchneider@xxxxxxxxx] Sent: Monday, August 25, 2003 12:38 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: POST MF SP3 asynchronous logons Slow logons are for both ICa and RDP. Waiting for the script to finish. What would Metaframe PTA have to do with login times via RDP? You sure there isn't something else going on there? -----Original Message----- From: Schneider, Chad M. [mailto:CMSchneider@xxxxxxxxx] Sent: Tuesday, August 26, 2003 11:45 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Post MF SP3 slow logons.... BINGO! That appears to be it. I turn off pass through on the client, and off it goes, running asynch again. Now, I did it logged on as me. That will only alter my appsrv.ini. I need to alter the main appsrv.ini and then any for the connected users. _____ From: Schneider, Chad M. Sent: Tuesday, August 26, 2003 10:35 AM To: 'thin@xxxxxxxxxxxxx' I just thought of something..... During the install of MF SP3 or upgrade to it, you are asked about enabling pass-through. I have told it yes each time, as I would like to use pass-through, some day. We are not using it at this time. Could this be of issue? Can I turn off the pass-through on the servers? I turned it on after learning that if you don't enable it, you can't down the road. Chad Schneider Technology Analyst Bemis IT 920-303-7609 ******************************************************************************** What would colour do to promote your business better? Want to fax, print, copy, scan in both black & white & colour? Call Glen, Wendy or Lynette to organise a personal demonstration and experience the difference a Xerox Baby Imari DCC240 can make to your office. Call today 08 89229000 Katherine customers call NT Technology on 08 89728888 www.csg.com.au ******************************************************************************** NOTICE !!!!!****************************************************************************************** This e-mail message is privileged and confidential and is intended only for the use of the addressee. If you are not the intended recipient:confidentiality and privilege is not waived; please contact us immediately to advise of receipt by you; and you are not to read, disseminate, copy or take any action in respect to the contents of this e-mail. Any views or opinions presented are solely those of the author, except where it is specifically stated by the sender to be views of Connected Solutions Group. This e-mail has been scanned, logged and cleared by Mail Marshal ******************************************************************************************************