Link to home
Start Free TrialLog in
Avatar of piattnd
piattnd

asked on

Accessing RemoteApps externally with .local internal domain

Experts:

I've been running around in circles for a while on this one.  I've been working with a client to migrate them to RemoteApps, but their internal domain is domain.local.  The problem this is creating is none of the internal names are publishable, so external clients cannot resolve names unless I deploy hosts file entries to them.  This causes a problem because a requirement for them is to go to a random lobby computer and be able to use RemoteApps from there.

I did find a section that allows you to reconfigure the URL used to access the RDWeb page, and that works, but as soon as you try to launch an application, it again tries to access the path it was shared with, which has to be the server name of which the exe runs on, which has .local.

Anyone have any ideas?
Avatar of piattnd
piattnd

ASKER

I'm going to leave this question open for a few days, but I found a workaround for anyone that finds themselves in the same position.

If you go to "https://remote.server.com/RDWeb" in chrome, you can login and see the apps to launch.  When you click an app to launch, it downloads the RDP file.  You can edit that file in notepad and adjust the .local server name to the public DNS name that you've chosen.  As long as you have a DNS record that's been published to the world, everything should work just great.
ASKER CERTIFIED SOLUTION
Avatar of Gareth Gudger
Gareth Gudger
Flag of United States of America 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
SOLUTION
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
Avatar of piattnd

ASKER

I had found the same resolution as suggested prior to me seeing this post.  Awarding partial points.