ian.integra-xp wrote:My solution is based on bits from several places:
I didn't like any of the above in isolation but combined they work well.
so, what I did was take:
*the screenconnect webservice mentioned above, no changesand I rewrote the PS to be a bit more helpful. It depends on all the above though.
*the EDF + deploy script + GUID detection script mentioned above
*the little chunck of PS mentioned above
Its a simple powershell module which takes two parameters, the url and the guid. It connects to the webservice on the screenconnect site and requests a a url for the machine with guid xxxxx. It then launches the exe from the url.
As per the thread on ltg, I added a menu option to CC to launch the powershell script, passing the url and guid.
The script creates a file in your profile which stores your login credentials to the screenconnect server. If you change your password you need to delete it.
The script also contains some redundant code which displays a winforms interface. Its a work in progress.
Users browsing this forum: No registered users and 1 guest