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

        Post a Comment

        Popular posts from this blog

        Create bootable CUC CUCM CUP Image / ISO

        -
        The following script allows you to automatically create a bootable CUCM/CUC/CUP image without the need for any paid for software when you only have access to the update outside of put or the datastore for the new server. I have spent several hours on this, but I just wanted to make it simple. Only really for lab purposes, the checksum will fail due to the ISO being manipulated but essentially once you fill in the variables, you will just be left with a single ISO file in the staging directory. To use; 1. Download the mkisofs.exe file as described in the script 2. Paste script below into Powershell ISE Script Editer 3. Modify the variables 4. Execute the script. Simple. Tested creating an ISO on a Windows 10 machine and running the ISO on a ESXI server. Thanks for this guy Aaron Harrison as per the URL, was helpful in the finding out the mkisofs.exe command syntax. http://www.ipcommute.co.uk/technical-articles/17--creating-isolinux-boot-dvds-with-free-software-cucm-uccx-cups.
        Read more

        Configuring Oracle 12c backups on Veritas Backup Exec 16.

        -
        Image
        This is a short guide to configuring backups of Oracle 12c using Veritas Backup Exec 16. 1.        Establish trust with Oracle Database server within Backup Exec console and ensure agent is installed. 2.         Create a login to the database for backup purposes in Oracl e; Open up a command prompt and run the following command – Sqlplus / nolog Log in with your database admin account as sysdba Connect myusername / mypassword@databasename as sysdba CREATE USER BACKUP IDENTIFIED BY MYPASSWORD; GRANT UNLIMITED TABLESPACE TO BACKUP; GRANT AQ_ADMINISTRATOR_ROLE TO BACKUP; GRANT DBA TO BACKUP; GRANT CONNECT TO BACKUP; ALTER USER BACKUP DEFAULT ROLE ALL; ALTER USER BACKUP DEFAULT TABLESPACE SYSTEM; 3.        Within the Local Users and Groups section of Computer Management on the Oracle database server, add the backup servers windows domain administrator account to the following groups – a.        ORA_OraDB12Home1_SYSBACKUP b.    
        Read more

        CUCM 11.5 - Esxi 6.5 - unable to create VM

        -
        Image
        Hi Guys Had an issue where I was unable to deploy a Cisco Unified Call Manager 11.5 OVA to the VMWare Esxi 6.5 standalone server. The following error would appear during the provision of the VM - "At least one extra disk image was provided that will be ignored". The solution to import the Cisco OVA into VMware is to use VMware's OVFTool. The commands I used worked for also UCCX and Cisco Unity Connect - CUCM Deployment for 2500 Users --------------------------------- ovftool --acceptAllEulas --datastore="datastore1" -dm="thick" --name="CUCM01-PUB" --net:"eth0"="Voice" --deploymentOption="CUCM_2500" "c:\temp\cucm_11.5_vmv8_v1.1.ova" vi://UserName:Password@IPAddress UCCX ---- ovftool --acceptAllEulas --datastore="datastore1" -dm="thick" --name="UCCX1" --net:"eth0"="Voice" --deploymentOption="UCCX_400_Agent" "C:\temp\UCCX_11.
        Read more