The ConnectWise Control forum has moved to ConnectWise University! This forum has been locked and is in read-only mode. Click here for instructions on how to access the new forum.

Welcome Guest! You can not login or register.



Go to last post Go to first unread
#1 Posted : Tuesday, March 21, 2017 4:20:38 AM(UTC)

Rank: Newbie

Joined: 9/22/2014(UTC)
Posts: 6
Location: Torres Strait

Thanks: 1 times
Is there a way to get a lite-touch image (not to be confused with a SOE with a baked in screen connect installer) connecting to screenconnect?

Here are a few of the ideas i have about this:

1) Leave an open 'support' session with a join code of something like "litetouch" - have MDT launch a screenconnect ACCESS silent runtime which will automatically join the access session.
- If there are two machines being run up at once, one the first machine gets through the first reboot, it will disconnect then connect with the next in line.

2) Install an 'access' session via the litetouch run-up using a custom company name and machine name as default - this will end up with hundreds of old GUID machines under access (but could manually clean up any session that is not 'online' at a later date)

3) Add a new option to the client config - automatically delete the session access upon disconnect, therefore when using that particular method, the machine would disappear from the access list.

4) Carry session details between the litetouch phase and the operating system install phase.
- this would require installing screen connect using command line arguments taking the current GUID logon name and having screen connect automatically rename the machine once a reboot starts

Any feedback on these methodologies would be appreciated.

#2 Posted : Wednesday, March 22, 2017 6:16:58 PM(UTC)

Rank: Member

Medals: ScreenConnect Advisor: Focus Group Member

Joined: 10/28/2015(UTC)
Posts: 42
Location: Sherbrooke

Was thanked: 1 time(s) in 1 post(s)
We use option 2 and it ok for our need, we manually terminale disconnected session every now and then and have done for our Windows 10 transition (about 100 pc over canada) without issue.
The only thing is that we did have some issue with the client not showing the screen, but it depend on the version of ScreenConnect and as we have completed the transition we did not took more time to evaluate it newer version fix it.

We did need to inject in the image .net framework, ScreenConnect client and a startup script with the necessary key to have the system start
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.