I would like to use this VNC as well, But my scnerio would be different. I use Intel VPRO for controlling the power in my environment. Would be nice to have a way to access the VPRO by VNC in rare instances that a PC was down and not responding. 

Be nice to also be able to control power on PC's with the Intel VPRO, possibly have an online PC at a location control vpro enabled PC's in that subnet or local lan? that would be awesome!

I would also like this. Basicallly in my scenario, if the PC is locked, I couldn't access the files without the users Password, SO I would be able to login while a user was at lunch and do a quick update or other related task without intruding on any prevalent information that i'm not supposed to see.

Hello guys. I was told this is where I should post this.  Basically i'm looking to set individual permissions for my users. Specifically myself and my supervisor prefer to connect as view only to machines first​ before we take control. Here is our scenario.

1st, Employee places a helpdesk case on an issue.
2nd, We connect within 5 minutes of the case being opened as view only.
3rd, We evaluate if the user is still on the stuck page they opened the case on or if the user is working feverishly.
4th, If the user is on the page, we switch to take control and start fixing the issue,
5th, If the user is busy, locked or away from the desk, we then contact the user to find out more information.

View only allows us as technicians to get an in depth look into the problem before we connect to see what is actually going on and how we need to actually fix the issue.

However not everyone in our organization needs this permission.  What I want is a choice to startup in view only or control mode. and I want to lock this down by not allowing everyone to have view only permissions.  My other 15 techs will not need that view only permission.  I'm told right now that Suspend Control At Startup is the only way to accomplish this. But it affects everyone, not just myself and my supervisor, So we need a way to set this just for us since that is how 99% of the time we connect is view only and everyone else is 100% connecting by control.

Also as a side case, When my current solution switches between view only and Control, I can tell at a glance which way my session is. In my current solution the menu bar at the top of a control session turns red if it is view only and the mouse pointer turns to a red circle with a line through it to further indicate it is view only, If in Control mode it stays a grey color. I typically work on up to 15 machines at a time in different sessions, So being able to tell which one is view only and which one is in control is a huge deal for us. 

Also View only allows for us to allow a 3rd party tech into our systems and allows us to go view only so we can work with the tech via phone calls and not disturb his mouse movements. So being able to see that as red as an indicator it is view only is a huge help is us not making a mental mistake and messing up a tech working for us.

Hello guys. I was told this is where I should post this.  Basically i'm looking to set individual permissions for my users. Specifically myself and my supervisor prefer to connect as view only to machines first before we take control. Here is our scenario. 

1st, Employee places a helpdesk case on an issue.

2nd, We connect within 5 minutes of the case being opened as view only.

3rd, We evaluate if the user is still on the stuck page they opened the case on or if the user is working feverishly.

4th, If the user is on the page, we switch to take control and start fixing the issue,

5th, If the user is busy, locked or away from the desk, we then contact the user to find out more information.

View only allows us as technicians to get an in depth look into the problem before we connect to see what is actually going on and how we need to actually fix the issue. 

However not everyone in our organization needs this permission.  What I want is a choice to startup in view only or control mode. and I want to lock this down by not allowing everyone to have view only permissions.  My other 15 techs will not need that view only permission.  I'm told right now that Suspend Control At Startup is the only way to accomplish this. But it affects everyone, not just myself and my supervisor, So we need a way to set this just for us since that is how 99% of the time we connect is view only and everyone else is 100% connecting by control. 

Also as a side case, When my current solution switches between view only and Control, I can tell at a glance which way my session is. In my current solution the menu bar at the top of a control session turns red if it is view only and the mouse pointer turns to a red circle with a line through it to further indicate it is view only, If in Control mode it stays a grey color. I typically work on up to 15 machines at a time in different sessions, So being able to tell which one is view only and which one is in control is a huge deal for us.  

Also View only allows for us to allow a 3rd party tech into our systems and allows us to go view only so we can work with the tech via phone calls and not disturb his mouse movements. So being able to see that as red as an indicator it is view only is a huge help is us not making a mental mistake and messing up a tech working for us. 

This post seems to be kinda dead, Can you tell us more about this being considered for a future release? We are all excited. Personally I am coming from another solution that already had this desktop app, and it is a huge step backwards to not have t his with your solution. So I am hopeful since it has been considered for over 9 months that you guys are very close to at least a beta of this app?