Configuring Windows 7 Remote Assistance

How to configure Windows Remote Assistance within a Domain Environment

On the Server

1. Create a new Group Policy called 'Remote Assistance' and link it to a Container called 'Test - Remote Assistance'.

2. Apply the following settings in the 'Remote Assistance' Group Policy within the following section Computer Configuration\Policies\Administrative Templates\System\Remote Assistance;
    1. Allow only Vista or Later connections - Enabled
    2. Turn on session logging - Enabled
      [Stored in Documents\Remote Assistance Logs\]
    3. Customize Warning Message - Enabled
      { Please minimize or close any applications that display confidential information before accepting any requests for Remote Assistance.  }
    4. Solicited Remote Assistance - Disabled
      [this prevents requests for Remote Assistance being sent from the client machine]
    5. Offer Remote Assistance - Enabled
    6. Offer Remote Assistance - Permit remote control of this computer: Allow helpers to remotely control the computer.
    7. Offer Remote Assistance - Helpers: YourDomain\Domain Admins
    8. Offer Remote Assistance - Helpers: YourDomain\Helpdesk Administrators
      3. Move the client computer in to the Container called 'Test - Remote Assistance' within Active Directory.

      On the Client
      1. Perform 'gpupdate /force' from Command Prompt.
      2. Reboot
        [it may not be necessary to reboot. You could perform a 'gpresult /h c:\report.html /f' to check whether the policy has successfully applied]
      3. Ask someone to login.
        On the Technician's Computer

        There are two methods to connect to a remote computer;

        Method A:
        1. Open Run and type 'msra /offerra'
        2. Type in the IP Address / Computer Name of the remote machine
        3. Thats it... Your client should receive a notification which they need to accept.

        Method B:
        1. Open Run and type 'msra /offerra 10.1.1.1
          [10.1.1.1 being the IP Address of the clients machine. This can also be a host name]
        2. That's it... Your client should receive a notification which they need to accept.
        Testing
        1. I have tested remoting into a computer as a user and being refused access. 
        2. I have tested remoting into a computer as an domain administrator and being granted access.
        3. I have tested trying to request Remote Assistance from a client machine and being notified that the feature is unavailable.
        A Time Saving Approach

        It is possible to make this even more efficient in your organization.  If the asset number is unique across all of your sites within the Computer Name, you could create a VB Script which searches through Active Directory looking for the asset number in the computer name. Once returned, the script could then run the following command, 'msra /offerra computername'. All you would need to ask your client for is their asset number. A much more professional service, and all free curtsry of Microsoft.

        Thoughts 

        Hope this helps you as I struggled researching this on the internet even if it was pretty basic to setup. The only part which really threw me was the 'msra /offerra command' as it took a while to figure it out. You could type 'run msra /?' to read GUI help menu from Run.

        This is provided without any warranty.

        Comments

        Popular posts from this blog

        Create bootable CUC CUCM CUP Image / ISO

        Configuring Oracle 12c backups on Veritas Backup Exec 16.

        Configuring Cisco CME Voice Gateway (VG) for incoming and outgoing calls using Sipgate trunk