2 Replies Latest reply on Dec 26, 2013 10:00 AM by tdavenport

    CSA Agent as On-Demand Remote Client without a pop-up....

    ecoidan Specialist

      CSA 4.3

      LDMS 9.5 SP1


      Installed Virutal CSA 4.3 and followed article http://community.landesk.com/support/docs/DOC-29460 to correct the issue with the 404 error about the On-Demand Remote Client. Everything works but when the on-demand remote client is used the remote system does NOT show in the "Remote Control Agents" listed on the CSA.  This would be true because the default On-Demand RC Client does not conatined the source files for HTML5.


      RDP to Core Server

      - opened Console

      - went to Configure / Manage Cloud Services Appliances

      - Clicked on TAB "Remote Control Agent"

      - Created CSA Agent with RC settings that enabled HTML5 RC.


      I manually excuted the CSA Agent on remote system and filled out the ID Code 1 / ID Code 2 sections.  That systems showed in the CSA under HTML Agents and was able to remote control via HTML to that system. SWEET!


      I took my CSA Agent and put it in place of the On-Demand Agent "http://community.landesk.com/support/docs/DOC-29460" and tried again on remote system. As long as you fill out  ID Code 1 / ID Code 2 sections  you can Remote via HTML. 


      Soooooo, how do I modify that CSA Agent to autopass switches to populate the ID Code fields. Less work the user has to do the better, I just want the user to click the Install Now button the CSA and away it goes.


      This would really be the ideal on-demand agent for helping users without having to install the remote viewer when I am at home or at remote locations.