+1
Not a bug

Acquire wake lock shouldn't 'wake lock' the host screen

jhardwick 2 years ago updated by anonymous 2 years ago 6

I frequently use the wake lock when I'm waiting on machines to complete updates, etc remotely.


However, if I walk away from my desktop I still want the screensaver/lock to kick in.


I don't see why the two are tied together.

ConnectWise Control Version:
Server Affected:
Host Client Affected:
Guest Client Affected:

Answer

Answer
Fixed

This issue should be resolved in the forthcoming 6.6 release of ConnectWise Control.

Waiting for information

Good afternoon,


I moved your post over to the bug forum for additional review. Please update this thread with the following information:


1) Version of ConnectWise Control you're using

2) Host operating system

3) Guest operating system


Regards,

Ben

Planned

Good morning,


I was able to replicate this behavior in our dev environment; it appears that when the host executes the command to acquire a wake lock on the guest machine, a wake lock is acquired for the host's machine as well.


I have registered an issue with development, and it's currently under investigation.


Cheers,

Ben

Cool, thank you.

Answer
Fixed

This issue should be resolved in the forthcoming 6.6 release of ConnectWise Control.

Not a bug