I feel like it’s important to make an effort to stop the SH services on a machine you do not wish to monitor any longer. Leaving it out there and just blocking it continues to eat ram and cpu on the machine, it continues to try to talk to your server forever more, and it possibly leaves the client open to vulnerabilities in the future (what could possibly go wrong with a service that is internet accessible and has system level access and is never receiving any more updates?)
@Darrell_Swafford mentioned that “stop” just stops services until they reboot, but that’s not true. It will actually stop the service and remove the program from the remote machine. Our procedure for removing a machine is to “stop” it, then “forget” it. If the machine is not on or the client has already moved on we will send their new it company (cc’ing owner of our x-client) an email that they want to uninstall it, or at the very least stop and disable the service on the computer.
Blocking should really be a last resort after all efforts to stop and or remove the service from the machine have failed.