A remote desktop session may experience a long delay when you try to log off an Advanced Client computer

After you install the Microsoft Systems Management Server (SMS) 2003 Advanced Client software on a Terminal Server computer, it may take several minutes for you to log off a Terminal Services session on the Advanced Client computer. Additionally, changes to your profile may not be saved.

This problem may occur if another user tries to log on to a Terminal Server session while you are trying to log off a Terminal Server session. In this scenario, logoff notifications are completed synchronously. For example, if User A tries to log off a session when User B tries to log on to a new session, the logoff is blocked until the logon is completed. The logon may be delayed to process logon scripts.

Additionally, the problem may occur if the following conditions are true:

• No users are logged on to the Advanced Client computer local console.
• A user tries to log off a Terminal Services session on that Advanced Client computer.
  
  Note This condition does not require that either of the users be a specific user. Any user who logs on through a Terminal Services sessions will experience this problem as long as no one is logged on to the local console.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

When you install this hotfix, the SMS site services stop and restart, and the hotfix starts an SMS site reset.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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.

Installation information

This hotfix updates the Client Configuration Manager (CCM) Framework component to version 2.50.2726.0102. This hotfix contains an Advanced Client update and a management point framework update. You must update all management points with the new framework. As part of the installation, this hotfix performs a site reset to automatically update all the management points in the SMS hierarchy. If you delay the SMS site reset, you must manually perform a site reset or remove and then add the management points. You must reset each site where you apply this hotfix. To apply the hotfix silently, use the /s switch on the command line.

You must apply this hotfix at primary and secondary sites. Because of new architecture in SMS 2003, you must create a new package and a new program to advertise this hotfix to the Advanced Client computers. As part of the Setup program, this hotfix can create the package and advertisement automatically. Microsoft recommends that you let the Setup program create the package and advertisement for you.

To install this hotfix, follow these steps:

1. Download the hotfix file, and then run the self-extracting executable file to create the Sms2003-rtm-kb831962-x86-enu.exe file.
2. Copy Sms2003-rtm-kb831962-x86-enu.exe to a folder on your SMS primary or secondary site server computer.
3. Click Start, point to All Programs, point to Systems Management Server, and then click SMS Administrator Console.
4. Expand Site Database.
5. Right-click Collections, point to New, and then click Collection.
6. In the Name box, type:
   Advanced Clients for 831962
7. Click the Query Rule Properties button.
8. In the Name box, type:
   Advanced Clients for 831962
9. Click Edit Query Statement.
10. On the General tab, click the Show Query Language button.
11. Paste or type the following query in the Query statement box:

    select * from SMS_R_System 
    	inner join SMS_G_System_SMS_ADVANCED_CLIENT_STATE 
    	on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceID = SMS_R_System.ResourceId 
    	where SMS_R_System.ClientType = 1 
    	and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Name = "CcmFramework" 
    	and (SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version < "2.50.2726.0102" 
    	or SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version in ( "2.50.2726.4","2.50.2726.5",
            "2.50.2726.18", "2.50.2726.1", "2.50.2726.16" ))

    To use this query, you must have at least one Advanced Client computer in your inventory to create the database classes.
12. Click OK three times.
    
    This query identifies Advanced Client computers that do not have this hotfix installed. And this query identifies management points that also have the Advanced Client installed.
13. Run Sms2003-rtm-kb831962-x86-enu.exe on the SMS site server computer.
14. After the files are copied, click Yes, I want to create a package and program now, and then click Next.
15. Click Next to accept the default package and default program name.
16. Click Yes to perform a site reset.
17. In the SMS Administrator Console, expand Packages.
18. Right-click the KB831962 - Advanced Client Hotfix package, point to All Tasks, click Distribute Software, and then click Next.
19. Click to select the check box for your distribution points, and then click Next.
20. Click Next to advertise the program.
21. Click Next to select the program for the advertisement.
22. Click Advertise this program to an existing collection, and then click Browse.
23. Click the Advanced Clients for 831962 collection, and then click OK.
24. Click Next two times.
25. Click Advertise the program only to members of the specified collection, and then click Next.
26. Complete the Software Distribution Wizard.

To perform a silent installation of this hotfix, follow these steps:

1. Click Start, and then click Run.
2. Type cmd, and then click OK.
3. Locate the folder that contains the Sms2003-rtm-kb831962-x86-enu.exe file.
4. Type the following command, and then press ENTER:
   SMS2003-RTM-KB831962-X86-ENU.exe /s

If you cannot install the Advanced Client part of this hotfix, view the Advanced Client log files on the client computer. The Advanced Client log files are in the $Systemroot%\System32\Ccmsetup and the %Systemroot%\System32\Ccm\Logs folders.

Important Advertisement status for this hotfix may be reported incorrectly if you have distributed additional Advanced client hotfixes. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about finding the version number of your SMS 2003 installation, click the following article number to view the article in the Microsoft Knowledge Base: For more information about SMS International Clients Packs, click the following article number to view the article in the Microsoft Knowledge Base: For more information about standard terminology used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base: