Link to home
Start Free TrialLog in
Avatar of Victor-Max
Victor-Max

asked on

Server 2008 R2 RemoteApp configuration in Workgroup Mode

Hello,

Maybe i'm kicking in a open door but after several hours of searching on the web I didn't find the right solution for configuring RemoteApp on a 2008 R2 RDC Host box.

We have a single server standalone Windows 2008 R2 RDC Hostserver in Workgroup Mode on which we want to use RemoteApp. I followed the (config)Tutorials from MSTerminalServices.org about how to configure Remote Gateway, Terminal Services and RemoteApp. We also installed a multi-domain certificate from Comodo and made the corrections in public DNS. Until this everything works just fine, RDC connections thru Remote Gateway (SSL) and RDWeb works fine but clicking on a published app in RemoteApp the server cannot be found!
All services reside on a single serverbox and further investigation brought us to the RemoteApp Manager where a exclamation mark is at the section "Distribution with Web Access Computers Group is empty". According to Technet documents I should populate the TS Web Access Computers Security Group doing the following:

On the RD Session Host server, click Start, point to Administrative Tools, and then click Computer Management.
In the left pane, expand Local Users and Groups, and then click Groups.
In the right pane, double-click TS Web Access Computers.
In the TS Web Access Computers Properties dialog box, click Add.
In the Select Users, Computers, or Groups dialog box, click Object Types.
In the Object Types dialog box, select the Computers check box, and then click OK.
In the Enter the object names to select box, specify the computer account of the RD Web Access server, and then click OK.
Click OK to close the TS Web Access Computers Properties dialog box.

But there is no Object types "Computers" available! so I can't add anything to this group!

Does anyone have a solution or a walktrough for me to enable RemoteApp on a RDC singleserver in Workgroup Mode?

Best regards,
Victor
Avatar of Steve
Steve
Flag of United Kingdom of Great Britain and Northern Ireland image

the remoteapp system is designed to work on a domain so the groups you are referring to aren't used on our system.

it is possible to configure remoteapp to accept connections from anyone and get it on a workgroup, but you'll struggle if you intend being specific who can access it.

setup users directly on the terminal server in local users & groups and add these users to the 'remote desktop users' group.
Avatar of Victor-Max
Victor-Max

ASKER

Hello totallytonto,

The users who may connect remotely to RemoteApp were already added to the 'remote Desktop users' group and connecting to https://tsg.<domainname>/rdweb works fine, but clicking on a published 'App', the connection is not made (the server cannot be found).
Remote App really wants you to have Active Directory and the DNS server roles installed for it to behave nicely; but, you can easily edit an RDP to launch a program, save it, then send it to your users in any one of a dozen ways.
ASKER CERTIFIED SOLUTION
Avatar of Steve
Steve
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It was eventually an DNS problem, the dns name wasn't correct listed in the DNS server. Thanks to totallytonto we discovered the faulty DNS entry..