How to Install Windows 2008 Terminal Server (Remote Desktop Services) with Remote Application Sharing

How to Install Windows 2008 Terminal Server (Remote Desktop Services) with Remote Application Sharing
Terminal Services has been renamed for Windows Server 2008 to Remote Desktop Services.

After installing Server Standard or Enterprise 2008, you will need to add the Remote Desktop Services Role to the Server.

1) Open Server Manager

2) Select Roles

3) Select Add Roles

4) Click next on the first Screen

5) From the Selection List select Remote Desktop Services

You will be presented with a selection of different defined options under this role. Standard Terminal Services is covered under 'Remote Desktop Session Host'

6) Select Remote Desktop Session Host (formerly Terminal Server)

7) Install

You will need to restart the Server after the installation.

Remote Application Sharing

You can run Software in Terminal Services mode using the Remote Desktop Services RemoteApp Manager. For example, Quick Books (an accounting software used by small businesses) can be accessed from another office without having to log on to the terminal server under an RDP session. Instead, you can send a link to the application which will run in Terminal Server, or Remote Application, mode.

You will need to install the software you wish to run on the Server first.

To configure Remote application sharing on the Terminal Server:

1) Open Administrative Tools, Remote Desktop Services, RemoteApp Manager

2) From the selection list on the right hand side, select Add RemoteApp Programs

3) In the RemoteApp Wizard, click Next

4) Select the program or programs that you wish to run and click Next

5) Click Finish

(Note: Remote Users need to have a user account in your Domain you log onto)
Create an Remote Desktop Shortcut to your RemoteApp

1) From the list of RemoteApp Programs, select your program, e.g. Quick Books

2) From the slection list on the right hand side, select Create .rdp File

3) The RemoteApp Wizard will open again - click Next

4) Select the location to save the package. The default is C:\Program Files\Packaged Programs

5) Select the server name. This is the external dns address of your Domain e.g. serverts.domainname.com that resolves to your location.

6) Select the Server Port. The default is 3389 for Remote Desktop. If you have Port Redirection enabled on the local router, you should change the port to the port assigned to the Terminal Server.

7) Leave the other settings as default

8) Click Next and Finish
You can e-mail this shortcut to your clients, or make it available for download through FTP. When the user double clicks on the icon, they will be prompted a variant of teh Remote Desktop Window, be prompted for their Username and Password for your domain. The application will open in Terminal Services, with all the appearances of opening on the local computer.

Use Kaseya to Boot in to Safe Mode with VNC Access

Have you ever had trouble with a Remote PC, maybe with a virus, or a driver corruption, where you just needed to get into Safe Mode but didn't want to arrange a site visit?

The following Kaseya Scripts will add the VNC Client and the Kaseya Agent to the startup registry for Safe Mode, then restart the machine (with a 2 minute warning to the User) that machine is about to reboot into Safe Mode.

The Script edits boot.cfg so that the next time the machine restarts it boots into Safe Mode with Networking.

--

Script Name: Boot Into Safe Mode With VNC (PT1)
Script Description: [posted by geoff@lynxcomputing.com]
Edits the Registry to include WinVNC and KaseyaAgent in safe mode services. Edits boot.ini. Reboots into Safe Mode after 2 mins - Remote Controllable!

IF True
THEN
Set Registry Value
Parameter 1 : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\WinVNC4\
Parameter 2 : Service
Parameter 3 : REG_SZ
OS Type : 0
Pause Script
Parameter 1 : 10
OS Type : 0
Set Registry Value
Parameter 1 : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\KaseyaAgent\
Parameter 2 : Service
Parameter 3 : REG_SZ
OS Type : 0
Pause Script
Parameter 1 : 10
OS Type : 0
Send Message
Parameter 1 : This Machine Will ReBoot Into Safe Mode in 2mins. Please Save All Open Documents.
Parameter 2 : 1
OS Type : 0
Pause Script
Parameter 1 : 120
OS Type : 0
Write Script Log Entry
Parameter 1 : The Machine Was Sent A Command To ReBoot Into Safe Mode
OS Type : 0
Execute Shell Command
Parameter 1 : bootcfg /Raw "/safeboot:network /sos /bootlog /noguiboot" /id 1
Parameter 2 : 1
OS Type : 0
Pause Script
Parameter 1 : 10
OS Type : 0
Reboot
OS Type : 0
ELSE

--

Hey Presto! The PC reboots, the agent comes back online, and you have remote access to the PC in Safe Mode.

Now you need to restart the machine into normal mode. You'll need another script that changes boot.cfg to restart the machine normally.

--

Script Name: Boot Into Safe Mode With VNC (PT2)
Script Description: [posted by geoff@lynxcomputing.com]
Restores Boot.ini to standard. Reboots into Windows (Instant).

IF True
THEN
Execute Shell Command
Parameter 1 : bootcfg /Raw "/noexecute=optin /fastdetect" /id 1
Parameter 2 : 1
OS Type : 0
Pause Script
Parameter 1 : 10
OS Type : 0
Write Script Log Entry
Parameter 1 : The Machine Was ReBooted into Windows
OS Type : 0
Reboot
OS Type : 0
ELSE

--

Posted by Geoff


Follow Lynx on Twitter
http://twitter.com/geoff_lynx
http://twitter.com/CiaranJKenny