Pages

Thursday, March 18, 2010

RD Web Access is emply...

I have run into three reasons why your RD Web Access page would show no RemoteApps, Personal VMs, or VM Pools.

1. check to make sure the Conneciton Broker (or RDSH server, depending on how you are set up) is added to the Windows Authorization Access Group in AD.

2. If you try to make RDSH and RDCB co-exist on the same machine and make the RDSH part of a farm (I have seen people do this for testing and also because they did not want to virtualize and split these role services out). If you do this, when you choose a connection broker in RDWA, RDWA will show no apps. This also breaks RemoteApp and Desktop Connection. Dont try to combine these roles unless RDSH is in redirection mode only. Take the leap and virtualize and split these two role services up if RDSH is in app mode! :)

3. I had this happen to me. My Connection Broker had an unexpected shutdown. After this my RD Web Access portal came up empty, and the event logs on the connection broker (I have more than one RemoteApp/PersonalVM/Pooled VM resource so I use RD Connection Broker)

Event ID:11
RD Web Access was unable to contact pyramid.ash.local, which is the server that is specified as running the RemoteApp and Desktop Connection Management service. Ensure that the name of the server that is specified as running the RemoteApp and Desktop Connection Management service is entered correctly, and that the server is running and available on the network. Error code: 1722.

Of course this was not true. I rebooted the RD COnnection Broker, and then refreshed my RD Web Access page. This did not fix it. I then re-added the RD Connection Broker to RD Web Access Configuration tab, and wha-la. All was fine.

Friday, March 12, 2010

Microsoft RD Virtualization Host and Pooled or Personal VMs - Obscure errors and Fixes


A snippet from the upcoming Microsoft Windows Server 2008 R2 Remote Desktop Services Resource Kit:

I ran into a few obscure errors when implementing RD Virtualization Host with pooled and personal VMs, so I thought I would share them with you and save you some troubleshooting time!


WAKING THE VM…

When a user tries to access a pooled or personal VM they may get this message: “Waking the VM…” and an  eventual timeout.   Meanwhile, you can clearly see the VM "waking up fine in Hyper-V Manager...

There are a few reasons for this, all of which stem from not having the endpoint (the VM) configured correctly. You will receive this cryptic message for the following reasons:
  • The endpoint has not been prepped properly. You will experience this situation when any of the prep work was not done including the exceptions in the firewall, the registry entry adjustments, or the wmic commands
  • The endpoint was prepped properly but the Rollback snapshot was taken before the prep work was finished and had reverted the endpoint to a state that is no longer prepped properly.

    UNABLE TO VERIFY SETTINGS IN THE RDP FILE...

    Another scenario that gives obscure event log errors is one in which the Connection Broker has issues connecting the client to the requested endpoint VM. The user tries to initiate a connection to a pooled or personal VM.  They receive an error message saying that the connection could not be established because the Connection Broker was unable to verify the settings in the RDP file. On the Connection Broker the following two errors are logged in the TerminalServices-SessionBroker-Client event log:
       
              Event ID 1296:
             Remote Desktop Connection Broker Client failed while getting redirection packet from Connection
             Broker.
            User : ASH\kristin
            HRESULT = 0x80070490

    followed by:

           Event ID: 1306:
           Remote Desktop Connection Broker Client failed to redirect the user ASH\kristin.
           HRESULT = 0x80070490

    Remedy this situation, re-running the Configure Virtual Desktops Wizard on the RD Connection Broker server.  You do not need to change any of the settings (unless they are wrong of course). Just re-run the wizard with the same settings as you had before, and the Connection Broker will resume working properly.