今天開機又發生 Disk IO 大量被吃光的問題！ 真是怪了，不是才關掉 連接用户體驗和遙測服務 了嗎? 微軟真的很糟糕，還有一個 Windows 客戶經驗改進計劃 會拖慢…. 一樣把他關了吧，除了讓你電腦不要變慢之外，不會發生甚麼事情的!!!
【前言】 #include /* * Your warranty is now void. * * I am not responsible for bricked devices,dead pets, thermonuclear * war, or the current economic crisis causedby you following these * directions. YOU are choosing to make thesemodificiations, and * if you point your finger at me for messingup your device, We will * laugh at you. Loud and hard. */ 本文所介紹的所有內容全部都有可能破壞您的保固！
teamviewer 用到的 port
開放 TCP/UDP Port 5938
- TCP/UDP Port 5938: TeamViewer prefers to make outbound TCP and UDP connections over port 5938 – this is the primary port it uses, and TeamViewer performs best using this port. Your firewall should allow this at a minimum.
The following ports are not used by TeamViewer running on Android, Windows Mobile, or BlackBerry.
- TCP Port 443: If TeamViewer can’t connect over port 5938, it will next try to connect over TCP port 443.Note: port 443 is also used by our custom modules which are created in the Management Console. If you’re deploying a custom module, eg. through Group Policy, then you need to ensure that port 443 is open on the computers to which you’re deploying. Port 443 is also used for a few other things, including TeamViewer update checks.
- TCP Port 80: If TeamViewer can’t connect over port 5938 or 443, then it will try on port TCP 80. The connection speed over this port is slower and less reliable than ports 5938 or 443, due to the additional overhead it uses, and there is no automatic reconnection if the connection is temporarily lost. For this reason port 80 is only used as a last resort.