Internet Information Services (IIS) administrators may choose to disable weaker protocols such as SSL3 and TLS 1.0, either for compliance reasons or to reduce exposure to attacks such as POODLE. Typically, protocols can be enabled and disabled through registry keys on the server, as described at https://support.microsoft.com/en-us/kb/245030.
However, disabling SSL3 and TLS 1.0 also breaks the client-side functionality of some IIS management tools, such as IIS Manager (inetmgr.exe) and Web Deploy (msdeploy.exe). Using Visual Studio to publish through Web Deploy is also affected. The specific symptom in that situation is a failure to connect to the server, which triggers the following error:
The information in the "More Information" section describes how to make those tools work when SSL3 and/or TLS 1.0 disabled. The exact steps depend on the operating system and version of the .NET Framework that's installed on the computer.
Note These changes should be implemented only on the client (where inetmgr.exe/msdeploy.exe/Visual Studio are running) and not on the server (where IIS web server is running).
However, disabling SSL3 and TLS 1.0 also breaks the client-side functionality of some IIS management tools, such as IIS Manager (inetmgr.exe) and Web Deploy (msdeploy.exe). Using Visual Studio to publish through Web Deploy is also affected. The specific symptom in that situation is a failure to connect to the server, which triggers the following error:
The underlying connection was closed: An unexpected error occurred on a send.
The information in the "More Information" section describes how to make those tools work when SSL3 and/or TLS 1.0 disabled. The exact steps depend on the operating system and version of the .NET Framework that's installed on the computer.
Note These changes should be implemented only on the client (where inetmgr.exe/msdeploy.exe/Visual Studio are running) and not on the server (where IIS web server is running).