There is a broader question - why would the technician want to prohibit the user fr om stopping the Host when they wish to do so? Provided that they know what the Host is about.
because the user may not own the computer (as you mention below) they may be an employee. or in my specific case they are my children. do you have any idea how mischievous and curious children are? or for that matter employees? they can also be very smart when it comes to technology when they want to be. but at this time due to the many issues I've seen in version 6 I can not and would not use it in a business environment nor would I feel comfortable recommending it to my customers at this time. so this really does not effect me or my customers directly. but its the principle of it that I disagree with.
If the user wants to stop the Host running on their PC using services.msc, then:
- they are an advanced user, apparently, if they know about services.msc and use it to stop the Host at all costs
I would not call a user advanced because they are aware of services.msc..
they don't want the Host running on their computer, so they are perfectly in their own right stopping it
again not if they do not own the computer.
So we are getting back to the question implicitly posed in the blog post/news about this update: if the software use is perfectly legitimate and the user knows they have a remote access software installed on their PC, why would they want to stop it?
many reasons.. for 1 perhaps they use the computer for non business activity and "think" RUT is used to spy on them?? when in fact it's used to connect when necessary to resolve issues.
But if they want to stop it, why would anyone prohibit them from doing so? Except only in a business setting wh ere computers do not belong to employees - but it should be handled by policies on the network/Active Directory level.
I am a computer consultant. a huge amount of our customers are SMB. many of my customers do not have the resources to manage and secure their network properly, when we recommend GP, strict firewall policies, block local admin access etc. it ultimately requires more administrative resources, (time, knowledge and money..) they do not have the time to deal with user requests like installing basic software on the users pc etc etc) they also don't have the money to call me every time something like this happens. unfortunately this is reality. especially in the SMB market. I can recommend and preach a high security environment until I'm blue in the face but it is ultimately their decision,
Yes, you can hide the Host menu or protect the Host settings, but that's mostly to prevent the user from messing with the settings inadvertently. These features have nothing to do with truly prohibiting the user from being the ultimate master of their own PC If it's not their PC, they are not supposed to be an administrator on it, and hence they won't be able to stop the service if they have insufficient privileges.
see my reply above.
we could argue this point until we're blue in the face.. its ultimately your software and you can change it and alter it any way you wish.. hopefully the changes you make provide a better experience for your customers..