How to create a resident remote control only agent for LANDesk Management Gateway clients that do not need a standard agent.

Version 8

     

      Subject
    How to create a resident remote control agent on LDMG clients that do not have/need a standard agent.

     

      Description
    How to create a resident remote control agent on LDMG clients that do not have/need a standard agent.
    I.E. Used for machines that do not need to be managed, that are on the internet and need to be waiting for a remote control connection through a Management Gateway at all times.

    Applies to:
    LANDesk Management Gateway iso or appliance
    LDMS 8.7 and 8.8

     

     

     

      Resolution
    • Download the agent cab file from a management gateway -
    o http://gatewayname
    o example http://ldmg.landesk.com
    o click tools or utilities
    o click support tools
    o click and save LANDesk remote assistance agent (cab)

     

    Steps to install a resident RC agent.

     

    • Copy the contents of the cab to anywhere on the target resident client pc.
    o (For Example C:\Program Files\LANDesk\RCAgent)

     

    • From a run prompt run the following command:
    o issuser.exe /resident /b /lBROKERADDRESS
    o for example issuser.exe /resident /b /lldmg.landesk.com
    o This will install the service to windows
    o NOTE: no space after the /l (l= lower case L)
    o You will need to type the full path to the ISSUSER.exe!!

     

    • To uninstall run the following command
    o Issuser.exe /remove
    o You will need to type the full path to the ISSUSER.exe!!
    o This will uninstall the service AND delete all of the files from the machine.

     

    Note: If the issuser command line is run incorrectly or if changes are needed to an existing resident agent, run the remove command and then re run the resident command line as shown above.

     

      Advanced Settings

     

    Security Type:
    • Choose whether to use NO security (Local Template) or NT Security
    o If NT security is desired then a /y2 is needed at the end of the command line, by default it is local template.
    o If Integrated security is desired then a /y9 is needed at the end of the command line.
    o You can change this at anytime by modifying the security type registry key then restarting the RC agent service
    o hklm/software/intel/landesk/wuser32 - Security type dword
    o If you use NT security the remote controlling users must be in the “HDAllowed Operators” local NT group

     

    Organization
    • If you configure your Management Gateway users with Organizations other than * because you only want them to be able to see machines of a specific Org in the RCViewer then see the example below.
    o In this example we only want our client to be seen by Users with the Severs Organization on the Gateway.
    o issuser.exe /b /oServers /lGatewayName

     

    Example using all switches
    issuser.exe /b /oServers /lGatewayName -y9