Microsoft RDS Team published an article about logon attempt failed messages when connecting through RD Gateway. Single Sign-On (SSO) was working well internally, but externally (by using Remote Desktop Gateway), it was not working and resulted in continuous logon attempt failed error messages: To start working on this issue, first test to see if you are being redirected by going to the
Pankaj Pande published an article on RDS Microsoft blog describing how to restrict users from accessing local drives on a RD session. Currently, when a user creates an RDP session or a RemoteApp program, they can see, and in some cases transverse, drives C and D of the RD Session Host server. They can also save anything on the desktop,
Microsoft has published some documents that you can use to evaluate and deploy Microsoft RemoteFX within your environment. Following is a list of all the RemoteFX documents that were published to coincide with the Windows Server 2008 R2 with Service Pack 1 release. The following documents were created for Microsoft RemoteFX: Deploying Microsoft RemoteFX on a Single Remote Desktop Virtualization
Microsoft has published an interesting whitepaper related to the business value of Remote Desktop Services. RDS can be a cost-effective solution for any type of organization, particularly those with a mobile workforce, structured task workers, or knowledge workers with a need for flexible desktop or application access, including contractors, offshore workers and office workers who require a free seating environment
Microsoft RDS Team published an article about one of the recurring issues seen in product support: why a client cannot connect. Specifically, errors such as “Unable to RDP,” “Remote Desktop Disconnected,” or “Unable to Connect to Remote Desktop (Terminal server)” are common problems . This article summarizes the various causes for Terminal Server Client (Remote Desktop Client) connection failures and
Microsoft RDS Team published a blog post that describes the new Remote Desktop Services Windows PowerShell cmdlets, introduced in the Windows Server 2008 R2 SP1 timeframe, that configure virtual display adapters for virtual machines on a RemoteFX-enabled RD Virtualization Host server. For a given Virtual Desktop Infrastructure (VDI) host to be able to support many users and target the full range
Microsoft RDS Team published a blog post introduceing the Windows PowerShell cmdlets for configuring Remote Desktop licensing settings on a RemoteFX-enabled RD Virtualization Host server in Windows Server 2008 R2 SP1. Until Windows Server 2008 R2, in a Virtual Desktop Infrastructure (VDI) deployment, the RD Virtualization Host server was not aware of licensing settings because only the RD Session Host server
Microsoft has published an article that introduces the new Centralized Licensing Management work, implemented in Windows Server 2008 R2 Service Pack 1 (SP1) as a part of the RemoteFX feature, for centrally managing the licensing configuration in a Microsoft Virtual Desktop Infrastructure (VDI) deployment. This post assumes that you have a basic understanding of the following: Windows PowerShell Various Remote Desktop
Microsoft published an article with the most frequently asked questions about RemoteFX USB redirection. What are the requirements for RemoteFX USB redirection? RemoteFX USB redirection is only available when connecting to a RemoteFX-enabled Windows 7 SP1 virtual machine (VM) running on a RemoteFX-enabled Remote Desktop Virtualization Host server. For information about the requirements for RemoteFX, see Beta testing RemoteFX in Service
Summary Microsoft, in lab environment, is able to achieve more than 10,000 individual virtual machine (VM) run-time connections over a two-hour period. These tests show the range of scale possible with Remote Desktop Connection Broker (RD Connection Broker). Within the connection process, the overall time measured is overwhelmingly determined by the VM start and protocol connection time. RD Connection Broker
