Consider the following scenario:
- You deploy a Virtual Desktop Infrastructure (VDI) environment in a network.
- You enable the Remote Desktop Virtualization Host (RD Virtualization Host) role service on the Windows Server 2012-based computers.
- You try to log on to a virtual machine that is running Windows 8 or Windows Server 2012 in the VDI environment.
- The previous corresponding remote session to the RD Virtualization Host does not log off.
- You may receive the following error message when you try to manually logoff the session in the Server Manager console:RD Connection Broker failed to process the connection request for user <domain>\<userid>.
Failed while checking for disconnected session.
Error: User is trying to connect to the same Pool more than once simultaneously.
This issue occurs because the host computer does not receive a notification that the previous session has ended during the logoff operation. Therefore, the previous session does not log off successfully.
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.
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, submit a request to 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 website: 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.
PrerequisitesTo apply this hotfix, you must be running Windows Server 2012.
Registry informationTo apply this hotfix, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
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
Article ID: 2795531 - Last Review: Mar 13, 2013 - Revision: 1
Windows Server 2012 Datacenter, Windows Server 2012 Datacenter, Windows Server 2012 Essentials, Windows Server 2012 Foundation, Windows Server 2012 Foundation, Windows Server 2012 Standard, Windows Server 2012 Standard