This script isn't to rip them off it's to make up for their skewed license prices. It's possible there'll be some types of traffic that appear on only the incoming connection, which you can then block with the Windows Firewall to prevent those connections from working.As my lengthy intro comments state, I LOVE TeamViewer. What I would do in this situation is to install Wireshark on a client computer and profile the network traffic involved in both an incoming connection with the client listening, and in an outgoing connection to work on a different computer. In short, I don't think it'll be easy to block the TeamViewer application from accepting incoming connections, while still allowing it to start outgoing ones. You would also need to set up a rule (either with Windows Firewall or elsewhere on your network) to block traffic going to, but then your users wouldn't be able to use the tool themselves. However, in the specific case of TeamViewer, they provide a client program that a user can run which connects to TeamViewer's servers and routes incoming connections along that path thus, an incoming firewall wouldn't be sufficient. If you're working with Windows computers that are on a domain, you can use Active Directory Group Policies to configure the Windows Firewall on those computers to block the appropriate incoming ports. In most cases, the network paths that applications use are asymmetrical that is, you can block the appropriate port on incoming traffic to prevent incoming connections, but allow traffic on that port to leave to permit outgoing ones.

Teamviewer shutdown