I'm getting ready to un-install Norton Zone, I do not want a program running on my system that I can not control the way its startup or stop it from running. To me this is basically Hijacking my system and I've never had a service on any computer that the System Administrator could not control the Start Up or Stop the service from running. I can not believe that so many seem to be alright with this behavior.
I'm getting ready to un-install Norton Zone, I do not want a program running on my system that I can not control the way its startup or stop it from running. To me this is basically Hijacking my system and I've never had a service on any computer that the System Administrator could not control the Start Up or Stop the service from running. I can not believe that so many seem to be alright with this behavior.
One possible suggestion.
As Norton Zone users may also have a Norton security product on their system, could it be the Norton Tamper Protection controlling access to any and all ccsvchst processes? Try turning off Tamper Protection and see if you can stop the service.
Be sure to reactivate the Tamper Protection, and if it had allowed you to change the service setting, see if it now reenables the service when turned back on.
It's not my other Norton Security Programs, I'm using those on all 4 of my computers and I can stop, start, disable any part of the NORTON 360 IS program as Administrator. Norton Zone is the only program that I've never, never was not able to control, the only way you can stop it is to uninstall and I' m not to far away from doing that.
I recall seeing on another thread that this decision was made because part of the intent of the service is to allow users to be sure that the version of any given file was synched across multiple platforms. This inherently requires the service to be running at all times. Of course some of us may have different needs that make control of running processes a priority, so I understand what you guys are saying as well.
I wonder if an option could be provided in Settings to allow the user to turn off "synchronization protection," which would then let the service be killed without it automatically restarting? Or maybe to enable the user to simply shut the Zone down altogether from within the program, with a warning that this will disable synchronization protection?
DistEd2 wrote:I recall seeing on another thread that this decision was made because part of the intent of the service is to allow users to be sure that the version of any given file was synched across multiple platforms. This inherently requires the service to be running at all times. Of course some of us may have different needs that make control of running processes a priority, so I understand what you guys are saying as well.
I wonder if an option could be provided in Settings to allow the user to turn off "synchronization protection," which would then let the service be killed without it automatically restarting? Or maybe to enable the user to simply shut the Zone down altogether from within the program, with a warning that this will disable synchronization protection?
Much like the control offered in NIS and the other products. You can turn features off, when valid reasons exist, and then turn them back on when the incident is past.
The ability to pause the sync doesn't seem to fill that bill too well.