1. Access a link to the program on a Web site by using TS Web Access.
2. Double-click a Remote Desktop Protocol (.rdp) file that has been created and distributed by their administrator.
3. Double-click a program icon on their desktop or Start menu that has been created and distributed by their administrator with a Windows Installer (.msi) package.
4. Double-click a file where the file name extension is associated with a RemoteApp program. This can be configured by their administrator with a Windows Installer package
1. RD Session Host: Remote Desktop Session Host (RD Session Host), formerly Terminal Server, enables a server to host Windows-based programs or the full Windows desktop. Users can connect to an RD Session Host server to run programs, to save files, and to use network resources on that server.
2. RD Web Access: Remote Desktop Web Access (RD Web Access), formerly TS Web Access, enables users to access RemoteApp and Desktop Connection through the Start menu on a computer that is running Windows 7 or through a Web browser. RemoteApp and Desktop Connection provides a customized view of RemoteApp programs and virtual desktops to users.
When a user starts a RemoteApp program, a Remote Desktop Services session is started on the RD Session Host server that hosts the RemoteApp program.
3. RD Connection Broker [Optional]: The RD Connection Broker database stores session state information that includes session IDs, their associated user names, and the name of the server where each session resides. When a user with an existing session connects to an RD Session Host server in the load-balanced farm, RD Connection Broker redirects the user to the RD Session Host server where their session exists. This prevents the user from being connected to a different server in the farm and starting a new session.
RD Connection Broker is also used to provide users with access to RemoteApp and Desktop Connection.
4. DC: of course a Domain Controller is needed.
5. Trusted Certificate [Optional]: if you don’t want to get a warning on the certificate you will need to get a commercial certificate. Otherwise you can use an internal generated certificate and configure your Surface to trust the Root/Issuing CA.
6. DNS Record: you will need DNS record Points to your server.
1. Install the required roles: I will use Windows 2012 so on the dedicated machine:
a. Click Add Roles> Select Remote Desktop Services Installation:
b. Then select Standard deployment:
c. Select Session-based desktop Deployment:
d. Under Role services the wizard will install the three roles: RDSH, RDWA and RDCB, as the following snapshot:
e. Click Next.
f. Only if you get the following error continue with the following steps, if you didn’t get error then skip to step i. Error:
“Unable to connect to the server by using Windows PowerShell remoting”
g. Start PoerShell as Administrator, and run the following cmdlet:
Enable-PSRemoting -forceSet-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
h. The following snapshot shows the cmdlets:
i. In RD Connection Broker: select the server name as the following snapshot:
j. Do the same by adding the selected server in the RD WA and RD SH.
k. On the confirmation page click to restart the server after the installation and click Deploy to start the installation.
A bit of a misnamed subject line. For a second I thought it was to actually upgrade the OS from RT to Pro...
Yeah me to. I was super excited to get away from the "gotta get arm supporting OS out ASAP don't worry about quality" experience of RT.
I wasn't expecting a lesson on rdapps, useful never the less. although we already use this at my job.... thanx :P