RemoteApp using two servers, a DC and a member server

warrend110

New Member
Reaction score
0
I just took over an account where they had 2 servers. One domain controller and one member server. The member server was used as a RDP server to allow users from Ohio, Florida and Canada to use Mas 200.

Mass 200 is installed on the domain controller. what is the best way to set it up for users come in through the member server and access the software that is installed on the domain controller?
 
Install MAS90 client on the server they use as the domain controller. Data can be left on the DC if that's where it is now, or moved to the file/app/terminal server. (there are proper steps to take to install applications in terminal server.....it's not like installing software on a regular desktop).
change user /install
change user /execute

Should never...allow end users to log on locally to a DC. Which is basically what terminal server is....allowing them to log on locally.
 
Brian is correct, however you mentioned RemoteApp which means to publish the application as a RDP link. This is a cleaner approach than standard session based remote desktop.

I actually just did this with an office and it is so clean for the end users, they don't know that its not a real program but its running over VPN to the corporate office.

But yes, install program to the member server, install for all users, make sure to install in TS mode if it has one. Then log in with one of hte usernames and make sure it is configured.

You may need to tweak printers for remote desktop as well.
 
Still having issues with this. This is an account I just took over, I was able to install the applications on that server itself and connect and was able to use it.

Now, the main issue are people coming over the internet like Ohio and Canada, when I try to connect remotely, I get an error saying the remote gateway seems to be temporarily unavailable.

I have the IP set up for the remote gateway setup

Any Suggestions...
 
Back
Top