Ask a questionAsk a question
 

QuestionRDS Virtualization Host VDI

  • Thursday, October 29, 2009 8:43 PMjmp13 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I have a connection broker, session host, web access and the virtualization host setup on R2. I have two Windows 7 VM clients on the VH host. When I login into the web access and access the desktop, I get the following error: remote desktop cannot verify the server belongs to the server farm  - there is no farm it is trying to connect to one of the Windows 7 clients. I have the connection broker setup to be virtualization redirection not a farm. I follwed the RDS guides and I believe I have everything setup correctly. Any suggestions?

All Replies

  • Friday, October 30, 2009 11:22 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hello,

     

    Thanks for posting in our forum.

     

    Based on my experience, the issue is generally caused by incorrect configurations of the virtual desktop pools. To narrow down the problem’s scope, please collect the following information to us:

     

    ·          Collect the MPS logs using the following tool:

    Microsoft Product Support Reports
    http://www.microsoft.com/downloads/details.aspx?FamilyID=cebf3c7c-7ca5-408f-88b7-f9c79b7306c0&displaylang=en

     
    In the Select the diagnostics you want to run phase, please check General and Server Components. After the collection process finished, save it as a .cab file and send it to us.

    ·          On the server, enable the following Event Viewer logs:

    Application and Services Logs\Microsoft\Windows\Terminal Services-SessionBroker
    Application and Services Logs\Microsoft\Windows\Terminal Services-SessionBroker-Client
    Application and Services Logs\Microsoft\Windows\Terminal Services-TSV-
    VmHostAgent

    Reproduce the issue and check the logs above. Save the related errors and send to us.

     

    For your convenience, I have created a workspace for you.  You can upload the information files to the following link.  (Please choose "Send Files to Microsoft")

     

    Workspace URL: (https://sftasia.one.microsoft.com/choosetransfer.aspx?key=82a8c446-790f-496d-a35b-ff93ccbdd216)

    Password: Qi7Pdnb9x3LB

     

    Note: Due to differences in text formatting with various email clients, the workspace link above may appear to be broken.  Please be sure to include all text between '(' and ')' when typing or copying the workspace link into your browser.

     

    We will investigate further in this case once getting the information. Thanks.

     

    Lionel Chen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfd@microsoft.com

  • Tuesday, November 03, 2009 3:40 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

    As the thread has been quiet for a while. I wonder if you need any further helps from me. If so, please feel free to write here.

    Thanks for your cooperaiton. Have a nice day.

    Lionel Chen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfd@microsoft.com

  • Tuesday, November 03, 2009 11:40 PMjmp13 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    How do you see the configuration of a pool? There is no option to see it via the GUI. Is there a powershell command?
  • Wednesday, November 04, 2009 10:04 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hello,

     

    Thanks for your feedback, JMP13.

     

    In TechNet Script Center, there are series of scripts querying different scopes of the RDS-V configurations information:

     

    Verify RDV Host configuration

    http://gallery.technet.microsoft.com/ScriptCenter/en-us/d838f634-b448-4cee-882f-4ecaea33db6a

     

    Verify virtual machine configuration for RDV

    http://gallery.technet.microsoft.com/ScriptCenter/en-us/2fc05f02-50b5-45d4-87f7-72bf906e4203

     

    Verify Redirection configuration

    http://gallery.technet.microsoft.com/ScriptCenter/en-us/2d89d330-5249-4115-a3bd-c42c0e13ef36

     

    Please also send these information to the workspace and we’ll check the reason why the RDS Connection Broker judge the environment as a farm rather than VDI environment.

     

    Hope it helps and thanks for your cooperation again.

     

    ·         Lionel Chen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfd@microsoft.com

  • Friday, November 06, 2009 3:05 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

    How's going with the case now? Do you need any further helps from me? Please let me know. Thanks.

     

    ·         Lionel Chen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfd@microsoft.com


  • Friday, November 06, 2009 4:22 PMjmp13 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Where in the Connection Broker is a farm setup? Is that the RemoteApp Source section?
  • Friday, November 06, 2009 4:42 PMjmp13 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I also see event id 1306 and 1296 in the session-broker-client log on the session host serve.r
  • Monday, November 09, 2009 9:16 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hello JMP13,

     

    It’s nice to hear from you again.

     

    Regarding your question on how to setup Connection Broker farm, please refer to the following article:

     

    Checklist: Create a Load-Balanced RD Session Host Server Farm by Using RD Connection Broker

    http://technet.microsoft.com/en-us/library/cc753891.aspx

     

    It shows 4 phases to create a Load-Balanced RD Session Host Server Farm.

     

    If the issue is still unresolved, please send the MPS records and the event logs to the workspace I created. I will help you troubleshoot the issue based on the information.

     

    Thanks for your cooperation again.

     

    ·         Lionel Chen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfd@microsoft.com

  • Monday, November 09, 2009 4:33 PMjmp13 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    The problem that I am having is when I launch a desktop it is trying to connect the desktop as the farm name which I would think it should connect to the session host. I only have one session host so there is no farm at all.  On the Virtualization Host server, the log TSV-VMHostAgent, I see eventid 4874, failed to update farm name and it has the name of the desktop not the session host. How do I changed that to the session host?
  • Tuesday, November 10, 2009 11:52 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hello JMP13,

     

    Thanks for your feedback.

     

    To investigate further in this case, please help me collect the following information:

     

    ·         The exact event log message of the EventID 4874;

    ·         The steps you used to set the RD Connection Broker. If you were following a document to configure it, please let me know the URL to the document.

    ·         Collect the MPS logs using the following tool:

    Microsoft Product Support Reports
    http://www.microsoft.com/downloads/details.aspx?FamilyID=cebf3c7c-7ca5-408f-88b7-f9c79b7306c0&displaylang=en

     
    In the Select the diagnostics you want to run phase, please check General and Server Components. After the collection process finished, save it as a .cab file and send it to us.

     

    Thanks for your cooperation. I’d like to provide further assistance based on your information.

     

    ·         Lionel Chen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfd@microsoft.com

  • Thursday, November 12, 2009 9:06 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

    How are you? Have you collected the information and how's the status of the issue?

    Please let me know it if possible. Thanks.

     

    ·         Lionel Chen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfd@microsoft.com


  • Thursday, November 12, 2009 5:05 PMjmp13 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    On the session broker - the Terminal Services-SessionBroker-client

    Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.

    Event ID: 1296
    HRESULT = 0x80070490

    Remote Desktop Connection Broker Client failed to redirect the user 

    Evejnt ID: 1306
    HRESULT = 0x80070490

    I was following this http://technet.microsoft.com/en-us/library/dd772706(WS.10).aspx.
     I have no error messages in the other log files.

  • Wednesday, November 18, 2009 8:38 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hello JMP,

     

    Thanks for your feedback and sorry for replying late.

     

    In your case, I notice that you have installed all the server roles into the same server. That may cause the virtual desktop pool fail to work, according to the following thread:

     

    http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/013d0be4-0814-4fc6-b0ef-d2329381092c

     

    To use the virtual desktop pool features, I recommend you to install virtualization host role and other roles on separate servers. Otherwise, you can use the personal virtual desktop instead as a workaround. For more information, please refer to the Step-by-step Guide on Deploying Virtual Desktop.

     

    Please let us know the result. Thanks.

     

    ·         Lionel Chen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfd@microsoft.com

  • Wednesday, November 18, 2009 6:02 PMjmp13 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I have seperate servers for each of the roles. I even started over and getting the same messages.
  • Friday, November 20, 2009 7:44 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hello JMP,

     

    Thanks for your feedback.

     

    Based on a series of tests, I recommend you to check the session host role of your environment. As the session host is treated as a farm member, I suspect the issue is related to incorrect setting of the server mode. In such a case, please check it via the following steps:

     

    1.     On the server with Session Host role, click Start,  Administrative Tools, Remote Desktop Services and select the Remote Desktop Session Host Configuration.

    2.     In the Remote Desktop Session Host Configuration, under the Edit Settings area, double-click Member of farm in RD Connection Broker.

    3.     Click Change Settings under RD Connection Broker tab.

    4.     Confirm that Virtual machine redirection is selected and the correct name is listed at RD Connection Broker server name. If not, please correct them.

    5.     Check the issue again.

     

    Thanks for your cooperation and patience again.

     

    ·         Lionel Chen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfd@microsoft.com

  • Friday, November 20, 2009 3:12 PMjmp13 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    That setting is setup with Virtual machine redirecton with the name of the connection broker.  I am getting the 1296 and 1306 errors above.

  • Tuesday, November 24, 2009 2:03 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hello JMP,

     

    Thanks for your feedback.

     

    Based on the current situation, please use the following steps to test your server and collect important logs:

     

    1.     Confirm that at least the RD Connection Broker role is separate from other VDI roles.

    On the RD Connection Broker server, perform the steps below:

    2.     Start services.msc and restart the service Remote Desktop Connection Broker, test the issue again. If the doesn’t work still, go on with the following steps.

    3.     Navigate to the follow folder: C:\Windows\System32\winevt\logs and copy all the logs starting with Microsoft-Windows-TerminalServices to a new folder MyLog.

    4.     Collect the MPS logs using the following tool:

    Microsoft Product Support Reports
    http://www.microsoft.com/downloads/details.aspx?FamilyID=cebf3c7c-7ca5-408f-88b7-f9c79b7306c0&displaylang=en

     
    In the Select the diagnostics you want to run phase, please check General and Server Components. After the collection process finished, save it as a .cab file and copy it to the folder MyLog.

    On the DNS Server of your domain, perform the following step:

     

    5.     Start DNS Manager and expand Forward Lookup Zones, right-click the domain where your VDI environment is located, and select Export List. Then save the list to the folder MyLog

    After all the steps above, update the files in MyLog to the workspace I created for you:

     

    Workspace URL: (https://sftasia.one.microsoft.com/choosetransfer.aspx?key=82a8c446-790f-496d-a35b-ff93ccbdd216)

    Password: Qi7Pdnb9x3LB

     

    Thanks for your cooperation again.

     

    ·         Lionel Chen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfd@microsoft.com

  • Thursday, November 26, 2009 6:12 AMLionel Chen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello JMP,

    How are you?

    I am waiting for your response and would like to help you. Please leave me a note at your convenience.

    Thanks.

     Lionel Chen

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfd@microsoft.com