Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6233
  • Last Modified:

RemoteApps on Windows Server 2012

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
eMarketer75
Asked:
eMarketer75
  • 7
  • 6
1 Solution
 
Cliff GaliherCommented:
This is how RDS works in the 2012 era. In short, you don't change this.
0
 
eMarketer75Author Commented:
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
 
Cliff GaliherCommented:
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
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
eMarketer75Author Commented:
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
 
Cliff GaliherCommented:
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
 
eMarketer75Author Commented:
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
 
Cliff GaliherCommented:
Looks like your broker is misconfigured. RPC issues. Firewall perhaps.
0
 
eMarketer75Author Commented:
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
 
Cliff GaliherCommented:
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
 
eMarketer75Author Commented:
The session host are configured with Windows NLB, is that. Is that a best practice?
0
 
eMarketer75Author Commented:
Should i disable the NLB on the session host
0
 
Cliff GaliherCommented:
Windows NLB on the farm  server should work fine, as long as it is configured properly.
0
 
eMarketer75Author Commented:
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

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now