The most common scenario for this is that ASP.NET 4.5 is not installed/enabled on IIS, which is causing our application code not to be executed at all.

Note that it must be ASP.NET 4.5, which is a separate role/feature than .NET.

Note also that you may only have .NET 4.6 available as a feature; that's also OK, since it replaces .NET 4.5.

Hi Travis; thank you for the very detailed write-up.

Basically it would seem that, in any situation, a 403 is issued when you try to push a NuGet package?

In this case, it's likely that something is intercepting the request and issuing a 403. I think that a "nuget push" does a PUT, which is often blocked by things like WebDAV. So I would make sure it's disabled, and that the load balancer isn't disabling it.

This is definitely on our roadmap; stay tuned!

This is the first request for such a feature; after v5 ships, we may consider putting this on the roadmap as a feature, depending on if anyone else requests it.

These sorts of features may not be worth doing, because they are added complexity, more things to test, and only save a little bit of time during initial set-up.

It's not clear when that error is occurring, but

• if it's when requesting a key, then you go to my.inedo.com, and then request a key there
• if it's when downloading SQL Server, then download from Microsoft and install

You can use your same license key in this case, it's no problem! The licensing agreement for BuildMaster and Otter explicitly permit dedicated dev/test instances.

ProGet requires a separate server... but if it's just a temporary migration then it's also OK too.

This is OS & .NET Framework dependent.

Many users have reported that setting the follow registry will resolved this issue:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 
Value: SchUseStrongCrypto 
Data: 1

Note that this will involve a reboot. See this guide on TLS in .NET for more information