If you, like me, are going through a Shibboleth IdP install on a Windows 7 machine, after having configured all the necessary elements you may encounter an Apache Tomcat error that complains it can't bind on port 443.
To diagnose the problem, I ran:
netstat -o -n -a
The output revealed that the process listening on port 443 is has the system id 4, which Task Manager further explained was "NT Kernel & System".
So obviously, you can't kill a system process or you'll receive the famous blue screen of the death! The solution is much easier. The most likely candidate taking up that port is the IIS agent and particularly, the Web Deployment Agent. All you'll have to do to stop the service at fault is:
net stop was /y
Other possible candidates would be: