Step-By-Step: Enabling Remote Application Access

Hello Folks,

I’m In South Carolina right now enjoying the sun and the golf courses.PR-Wizard_thumb[5]

However, like any IT professionals, I sometimes have to access my systems and tools to address certain issues remotely. You may need remote access to address other scenarios such as:

  • Provide access to applications to devices that are unmanaged.
  • Deliver one or more apps instead of desktop
  • Secure corporate data
  • Simplify application deployment

In Windows Server 2012, the Microsoft Virtual Desktop Infrastructure (VDI) deployment is a scenario-based installation that allows you to install, configure, and manage your virtual desktops from a central location. With the VDI deployment scenario, you are presented with two deployment types:

  • Standard deployment – allows you to deploy Remote Desktop Services across multiple servers
  • Quick Start Installs all the necessary Remote Desktop Services role services on one computer to let you install and configure them in a test environment.

There are two deployment scenarios:

  1. Virtual machine-based desktop deployment – allows users to connect to virtual desktop collections that include published RemoteApp programs and virtual desktops
  2. Session-based desktop deployment – allows users to connect to session collections that include published RemoteApp programs and session-based desktops

Let me run you Step-by-Step through the setup in my lab.

On the server that will be exposed to the internet,

  • Open Server Manager.
  • Click Add roles and Features.


  • On the Before You Begin page, click Next.


  • On the Installation Type page, click Remote Desktop Services installation, and then click Next.


  • On the Deployment Type page, click Quick Start, and then click Next.


  • On the Deployment Scenario page, click Session-based desktop deployment, and then click Next.


  • On the Server Selection page, select the server that will host the services, click Add (the right arrow button), and then click Next.


  • Check the Restart the destination server automatically if required check box, and then click Deploy. Note: The installation and configuration will take approximately 4 minutes. Please wait for this to complete before proceeding.


  • When the installation has completed, click Close.



couple things that need to be done in productions is to assign a trusted certificate and setup a proper licence server.  but other than that, That’s it.

All you need is to expose port 80 and 443 to the internet to be able to access the RDWeb page.  In my case I'm traveling light with my Microsoft Surface and I have access to all my tools.



When I'm back we’ll look at publishing applications.  but in the mean time set it up for yourself.

Why don’t you try it for yourself by downloading Windows Server 2012


Right now I have to get back to my vacation. They’re calling us to Tee number one for our golf game.





Pierre Roman, MCITP, ITIL | IT Pro Advisor
Twitter | Facebook | LinkedIn


More Information

Windows Server 2012 Virtual Desktop Infrastructure

Direct Access

Windows Server 2012 Virtual Labs

Comments (1)

  1. Chrissj says:

    Thanks Pierre for the post. I tried it at home and it rocks! Now I can rub 32 or 64-bits software on any internet connected device. Awesome!!!

Skip to main content