Solved

RemoteApps on Windows Server 2012

Posted on 2013-05-29
13
5,498 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 57

Expert Comment

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

Author Comment

by:eMarketer75
ID: 39207544
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 57

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 39208838
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
Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

 

Author Comment

by:eMarketer75
ID: 39222430
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 57

Expert Comment

by:Cliff Galiher
ID: 39222490
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
ID: 39222544
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
 
LVL 57

Expert Comment

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

Author Comment

by:eMarketer75
ID: 39222717
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 57

Expert Comment

by:Cliff Galiher
ID: 39222742
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
ID: 39222753
The session host are configured with Windows NLB, is that. Is that a best practice?
0
 

Author Comment

by:eMarketer75
ID: 39222757
Should i disable the NLB on the session host
0
 
LVL 57

Expert Comment

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

Author Closing Comment

by:eMarketer75
ID: 39253556
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

ScreenConnect 6.0 Free Trial

Explore all the enhancements in one game-changing release, ScreenConnect 6.0, based on partner feedback. New features include a redesigned UI, app configurations and chat acknowledgement to improve customer engagement!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Local Printing Using Remote Desktop Windows 7 sometimes has issues with printing to a local printer using a Remote Desktop Connection (RDC). The 1st step is to verify that printers are checked on the Local Resources tab of the Remote Desktop C…
The reason that corporations and businesses use Windows servers is because it supports custom modifications to adapt to the business and what it needs. Most individual users won’t need such powerful options. Here I’ll explain how you can enable Wind…
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

825 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