Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows.
When you log off from a Windows Remote Access Service client, any Remote Access connections are disconnected automatically. If the Remote Access Service client is running an earlier version of a Windows-based operating systems, such as Windows 2000 or Windows XP, a user can enable a registry key to remain connected.
For more information about how to use the KeepRasConnections registry key, click the following article number to view the article in the Microsoft Knowledge Base:
158909 How to keep RAS connections active after logging off
registry key does not exist in Windows Vista or in Windows Server 2008. Therefore, to maintain Remote Access connections after you log off Windows Vista or Windows Server 2008, you must add a
registry key with the corresponding values under the following registry subkey.
registry key does not appear in the registry unless you add it.
If you add this registry key, and then set the default value to 0x1, Windows does not close Remote Access connections when you log off from the system.
By default, only administrators and the operating system have WRITE permission for this registry key.
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 the problem described in this article. 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.
Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.
No prerequisites are required.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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 item in Control Panel.
Windows Vista and Windows Server 2008 file information notes
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Windows Vista SP1 and Windows Server 2008 SP1
Service Pack 1 is integrated into Windows Server 2008.
The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.
For all x86-based versions of Windows Server 2008 and Windows Vista
For all x64-based versions of Windows Server 2008 and Windows Vista
For all supported Itanium-based versions of Windows Server 2008
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information for Windows Server 2008 and for Windows Vista
Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista
Windows Vista Ultimate, Windows Vista Home Premium, Windows Vista Home Basic, Windows Vista Enterprise, Windows Vista Business, Windows Vista Service Pack 1, Windows Server 2008 Standard, Windows Server 2008 Enterprise, Windows Server 2008 Datacenter, Windows Server 2008 Datacenter without Hyper-V, Windows Server 2008 Enterprise without Hyper-V, Windows Server 2008 Standard without Hyper-V, Windows Web Server 2008