Solved

RemoteApps on Windows Server 2012

Posted on 2013-05-29
13
5,336 Views
Last Modified: 2013-06-17
I have a RDS Farm of 6 RD Session Host and 1 broker. The RD host are access via a NLB virtual IP. I am using RemoteApps.

When i click the remote app, it seems to try to log into the broker servers instead of the RD host server. Where can I changes this.
SNAG-Program-0000.jpg
0
Comment
Question by:eMarketer75
  • 7
  • 6
13 Comments
 
LVL 56

Expert Comment

by:Cliff Galiher
Comment Utility
This is how RDS works in the 2012 era. In short, you don't change this.
0
 

Author Comment

by:eMarketer75
Comment Utility
Really? But the computer that is shown in "Remote Computer' is just a RD Broker. When I try to connect I get the following error.

error
0
 
LVL 56

Accepted Solution

by:
Cliff Galiher earned 500 total points
Comment Utility
Yes, the broker issues a redirect based on rules and internal logic, so all connections start with the broker so it can redirect appropriately.

The error you posted would imply a broken setup. Either with the broker or with the server the broker redirected the connection to. Event logs and diagnostics logs will provide far more information.
0
 

Author Comment

by:eMarketer75
Comment Utility
I checked the event log after I access remote app via the web and this is what i get.

Log Name:      Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational
Source:        Microsoft-Windows-TerminalServices-SessionBroker-Client
Date:          6/5/2013 10:42:05 AM
Event ID:      1306
Task Category: RD Connection Broker Client processes request from a user
Level:         Error
Keywords:      
User:          NETWORK SERVICE
Computer:      TSBROKER1.domain.local
Description:
Remote Desktop Connection Broker Client failed to redirect the user domain\jdoe.
Error: NULL
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-TerminalServices-SessionBroker-Client" Guid="{2184B5C9-1C83-4304-9C58-A9E76F718993}" />
    <EventID>1306</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>104</Task>
    <Opcode>13</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2013-06-05T14:42:05.459331500Z" />
    <EventRecordID>61</EventRecordID>
    <Correlation ActivityID="{7751BA40-03A4-435F-A7BD-815080D1800D}" />
    <Execution ProcessID="2332" ThreadID="3840" />
    <Channel>Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational</Channel>
    <Computer>TSBROKER1.domain.local</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <UserData>
    <EventXML xmlns="Event_NS">
      <param1>domain</param1>
      <param2>jdoe</param2>
      <param3>NULL</param3>
    </EventXML>
  </UserData>
</Event>
0
 
LVL 56

Expert Comment

by:Cliff Galiher
Comment Utility
Which says it failed to redirect. It doesn't say WHY. There would be a different event or log file to indicate what failed.
0
 

Author Comment

by:eMarketer75
Comment Utility
Just notice this message:

Log Name:      Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational
Source:        Microsoft-Windows-TerminalServices-SessionBroker-Client
Date:          6/5/2013 10:42:05 AM
Event ID:      1296
Task Category: RD Connection Broker Client processes request from a user
Level:         Error
Keywords:      
User:          NETWORK SERVICE
Computer:      TSBROKER1.domain.local
Description:
Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : domain\jdoe
Error: Remote Desktop Connection Broker is not ready for RPC communication.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-TerminalServices-SessionBroker-Client" Guid="{2184B5C9-1C83-4304-9C58-A9E76F718993}" />
    <EventID>1296</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>104</Task>
    <Opcode>13</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2013-06-05T14:42:05.459331500Z" />
    <EventRecordID>60</EventRecordID>
    <Correlation ActivityID="{7751BA40-03A4-435F-A7BD-815080D1800D}" />
    <Execution ProcessID="2332" ThreadID="3840" />
    <Channel>Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational</Channel>
    <Computer>TSBROKER1.domain.local</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <UserData>
    <EventXML xmlns="Event_NS">
      <param1>domain</param1>
      <param2>jdoe</param2>
      <param3>Remote Desktop Connection Broker is not ready for RPC communication.</param3>
    </EventXML>
  </UserData>
</Event>
0
Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

 
LVL 56

Expert Comment

by:Cliff Galiher
Comment Utility
Looks like your broker is misconfigured. RPC issues. Firewall perhaps.
0
 

Author Comment

by:eMarketer75
Comment Utility
In windows server 2012 there is not much to configure with RD Broker. I can ping the session host from the Broker. There is no firewall in between, since its on the same subnet. The windows firewall on the broker is disabled.

When connecting via RDC, the broker seems to be working.
0
 
LVL 56

Expert Comment

by:Cliff Galiher
Comment Utility
I am just going on the event log. The load balancer may be doing something to the packets in a non-conforming way. Without really digging in (which is not feasible in a self-help environemtn such as EE) it would be pure speculation on my part.

At any rate, the answer to your original question is still the same. The broker is SUPPOSED to be in the loop. And is TRYING to do what it is intended to do. Something else is causing the redirection process to fail, as indicated by the logs.
0
 

Author Comment

by:eMarketer75
Comment Utility
The session host are configured with Windows NLB, is that. Is that a best practice?
0
 

Author Comment

by:eMarketer75
Comment Utility
Should i disable the NLB on the session host
0
 
LVL 56

Expert Comment

by:Cliff Galiher
Comment Utility
Windows NLB on the farm  server should work fine, as long as it is configured properly.
0
 

Author Closing Comment

by:eMarketer75
Comment Utility
It seems that the error was caused by something in group policy. I block all group policies to the RDP servers and it started to work. Not sure which gpo broke it.
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Join & Write a Comment

At the beginning of the year, the IT world was taken hostage by the shareholders of LogMeIn. Their free product, which had been free for ten years, all of the sudden became a "pay" product. Now, I am the first person who will say that software maker…
Remote Desktop Shadowing often has a lot of benefits. When helping end users determine problems, it is much easier to see what is going on, what is being slecected and what is being clicked on. While the industry has many products to help with this,…
In this Micro Tutorial viewers will learn how to use Windows Server Backup to create full image of their system. Tutorial shows how to install Windows Server Backup Feature on Windows 2012R2 and how to configure scheduled Bare Metal Recovery backup.…
How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

5 Experts available now in Live!

Get 1:1 Help Now