Docstoc

Server 2008 and Remote Desktop Services

Document Sample
Server 2008 and Remote Desktop Services Powered By Docstoc
					Using ACT! with Server 2008 and Remote Desktop Services (formerly known as
“Terminal Services”)

What is it?
Remote Desktop Services is one of the components of Microsoft Windows (both server and client
versions) that allows a user to access applications and data on a remote computer over a network.
Terminal Services is Microsoft's implementation of thin-client terminal server computing, similar to
Citrix, where Windows applications, or even the entire desktop of the computer running terminal
services, are made accessible to a remote client machine. From a user perspective, published
applications are integrated seamlessly, feeling, and behaving like local applications.

Components:
Remote Desktop Connection
    Remote Desktop Connection, (RDC) commonly referred to as Remote Desktop, is the client
      application for Terminal Services. It allows a user to remotely log in to a networked computer
      running the terminal services server.
    RDC presents a desktop interface of the remote system, as if it were accessed locally.

RemoteApp
    RemoteApp (or TS RemoteApp) is a special mode of Terminal Services, available only in Remote
      Desktop Connection 6.1 and above (with Windows Server 2008 being the RemoteApp server),
      where a remote session connects to a specific application only rather than the entire Windows
      desktop.
    The UI for the RemoteApp is rendered in a window over the local desktop, and is managed like
      any other window for local applications.
    The end result of this is that remote applications behave largely like local applications.
    The task of establishing the remote session, as well as redirecting local resources to the remote
      application, is transparent to the end user.
    Multiple applications can be started in a single RemoteApp session, each with their own
      windows
    A RemoteApp can be packaged either as a .rdp file or distributed via an .msi Windows Installer
      package

Advantages:
        Single Install
        Access to full Program Features
        Accessible via Windows and MAC

Using ACT! with Remote Desktop Services

Publishing ACT! on RDS
    1.   Go to Start -> Administrative Tools -> Terminal Services and select TS RemoteApp Manager
    2.   Go the Action menu and select Add RemoteApp Programs
    3.   Click Next
    4.   Select ACT! by Sage Premium and click Next
    5.   Review the settings and select Finish
Deploying ACT! as the Published Application

Each method has its own set of advantages based on your desired user experience.

Method 1 - .rdp File
  1. Open the TS RemoteApp Manager
  2. Highlight the ACT! by Sage entry under RemoteApp Programs
  3. From t he Action menu, select Create .rdp File
  4. Click Next on the RemoteApp Wizard screen
  5. Select the location to save the .rdp file and edit the Terminal server or Gateway settings
     if necessary
  6. Review the Settings and click Finish
  7. The created .rdp file can now be deployed to your users

Main Advantage: Nothing “installed” Each user is given a single shortcut to launch when
needed.

Method 2 – Windows Installer Package
  1. Open the TS RemoteApp Manager
  2. Highlight the ACT! by Sage entry under RemoteApp Programs
  3. Under the Action menu, select Create Windows Installer Package
  4. Click Next on the RemoteApp Wizard screen
  5. Select the location to save the .msi file and edit the Terminal server or Gateway settings
     if necessary
  6. Select where you would like a shortcut created during install
  7. Review the Settings and click Finish
  8. The .msi file can now be deployed to users as a standalone installation file or pushed via
     a group policy

Main Advantage: For a user, this appears to be a seamless, installed program. The shortcut will
reside on their desktop and/or start menu and they will simply open the program and they
would any other locally installed program.

Method 3 – Web Access
Note: You must install the TS Web Access role service on the server that you want users to
connect to over the Web to access RemoteApp programs. For more information on installing
the TS Web Access role, please see Install the TS Web Access Role Service

Once the TS Web Access service has been installed, there are four things that must be set up for
a user to access the application from a client computer.

   1. Enable the RemoteApp program for TS Web Access
         a. To do this, click the program name, and then click Show in TS Web Access in the
             Actions pane.
   2. Specify the Data Source for TS Web Access.
         a. On the TS Web Access server, click Start, point to Administrative Tools, point to
             Terminal Services, and then click TS Web Access Administration.
         b. Log on to the site by using either the local Administrator account, or an account
             that is a member of the local TS Web Access Administrators group. (If you are
             already logged on to the computer as one of these accounts, you are not
             prompted for credentials.)
         c. On the title bar, click the Configuration tab.
         d. In the Editor Zone area, in the Terminal server name box, enter the name of the
             terminal server that you want to use as the data source.
         e. Click Apply to apply the changes.

   3. Configure the TS Web Access Server to Allow Access from the Internet
         a. Enable Windows authentication On the TS Web Access server
                  i. Click Start, point to Administrative Tools, and then click Internet
                     Information Services (IIS) Manager.
                 ii. In the left pane of Internet Information Services (IIS) Manager, expand
                     the server name, expand Sites, expand Default Web Site, and then
                     highlight TS.
                iii. In the middle pane, under IIS, double-click Authentication.
                iv. Ensure that Windows Authentication is set to Enabled. If it is not, right-
                     click Windows Authentication, and then click Enable.

   4. Install Remote Desktop Connection (RDC) client version 6.1 on the client machine.
          a. You must download and install the appropriate RDC client for your OS
               i.e.: Remote Desktop Connection (Terminal Services Client 6.1) for Windows XP
          b. Once the RDC client has been installed, users will now be able to access the
               published ACT! application via the web.

Main Advantage: Users are able to access their programs via a web interface. All programs
available to that user are shown and launched from a single interface.


Using Outlook with ACT!

Publishing Outlook on RDS
   1. Use the above steps to publish Outlook

Deploying Outlook as the Published Application
   1. Use one of the three described methods to deploy Outlook
Recording History in ACT!
   1. ACT! 2010
          a. There is nothing different that needs to be done to record history. The
              ACT.Outlook.Service automatically starts when the user logs in, which allows the
              user to record history as expected.
   2. ACT! 2009
          a. The ACT.Outlook.Service does not start automatically when the user logs in.
          b. 2 Methods may be used for starting the service
                   i. Method 1: Publishing the ACT.Outlook.Service
                         1. Follow the instructions above for publishing the service.
                         2. The downside to this method is it requires user interaction. If a
                             user neglects to launch the service, they will not be able to record
                             history.
                 ii. Method 2: A logon/logoff script that will start and stop the
                      ACT.Outlook.Service for each user
                         1. Logon Script
                                 a. Create the ActService.cmd file and save it to C:\Program
                                     Files\ACT\ACT for Windows using the script commands below.
                                b. Launch the Local Group Policy Editor by going to Start / Run and
                                     entering GPEDIT.MSC
                                c. Under User Configuration, expand Windows Settings and
                                     highlight Scripts (Logon/Logoff)
                                d. Right click on Logon and select Properties
                                e. Click Add
                                f. Browse to the ActService.cmd and click OK
                                g. Click OK to close the Logon Properties Dialog
                          2. Logoff Script
                                a. Create the ActServiceKill.cmd file and save it to C:\Program
                                     Files\ACT\ACT for Windows using the script commands below.
                                b. Launch the Local Group Policy Editor by going to Start / Run and
                                     entering GPEDIT.MSC
                                c. Under User Configuration, expand Windows Settings and
                                     highlight Scripts (Logon/Logoff)
                                d. Right click on Logoff and select Properties
                                e. Click Add
                                f. Browse to the ActServiceKill.cmd and click OK
                                g. Click OK to close the Logoff Properties Dialog

Using Word and Excel with ACT!
   1. Users will be able to merge to Word or export to Excel once they are installed on the
      server. These applications do not have to be published for users to have access within
      ACT!

Helpful Links
  1. Terminal Services in Windows Server® 2008: http://technet.microsoft.com/en-
     us/library/cc770412(WS.10).aspx
  2. RDC client requirements for Terminal Services Web Access in Windows Server 2008:
     http://support.microsoft.com/kb/943887/en-us
  3. Remote Desktop Connection Client for Mac 2:
     http://www.microsoft.com/mac/products/remote-desktop/default.mspx
  4. How to use Group Policy to remotely install software:
     http://support.microsoft.com/kb/816102


Script Commands
  1. Logon:
     @echo off
     "C:\Program Files\ACT\Act for Windows\ACT.Outlook.Service.exe"
  2. Logoff:
     @echo off
     taskkill /F /FI "USERNAME eq %username%" /IM Act.Outlook.Service.exe > nul

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:14
posted:10/20/2011
language:English
pages:5