In early 2004, we would think that Network Access Protection (NAP) was the panacea of the network. We can isolate Windows Server 2016 devices that we think are suspicious until they are considered to meet our Windows Server 2016 specifications (updated to the latest version with the latest patches) and scan these devices to make Windows Server 2016 free of any malicious programs , Then we can recognize this Windows Server 2016 device and decentralize this Windows Server 2016 device to our network to give all permissions at the same time. We can designate a network and a server in a certain area to repair Windows Server 2016 server. On repairing Windows Server 2016 server, we can download anti-virus protection and patches. Even if a Windows Server 2016 vendor brought a virus-laden laptop into the network, he gave a 30-minute speech and disappeared without a trace. We do n’t have to spend 3 days to clean up the mess. (The vendors here sometimes also represent telecommuting employees). Whatever the reason, Windows Server 2016 NAP never reached its peak, which may be due to the following reasons: Windows Server 2016NAP has never had a unified standard, with Juniper using one standard and Cisco using another. It is feasible to collect statistics from all manufacturers, but it will take time and effort. In fact, there are many ways to achieve the same purpose. For example, you can prevent Windows Server 2016 DHCP from assigning addresses, perform port restrictions on the switch, use custom access control lists, and so on. Users also object to Windows Server 2016NAP, because they don't want their computers to work properly at home, but they spend a lot of time patching them once they get them in the office. So Windows Server 2016NAP is destined to die before it exists. Hey, like Microsoft's response, the industry has moved away from Windows Server 2016 network access detection and protection. NAP has been deprecated in Windows Server 2016, and it is unlikely to continue to be developed in the future.