Travis,
I had the exact same issue. Working with USAF SDC images, which is a standard desktop configuration built on a OS. Usually with a lot more security settings enabled/configured. In this case, I could get to vCenter via the Windows 7 SDC I was using, but not the Windows 10 one. I opened my security policies and compared every single item and found the culprit! In your security policy settings (local or GPO) go to Computer Configuration> Windows Settings>Security Settings>Local Policies>Security Options. Look for "Network Security: Configure encryption types allowed for Kerberos", and edit it. My Windows 10 machine had RC4_HMAC_MD5 unchecked. Checking/enabling this resolved my issue.
This setting (and the "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing") are set because the AF network is going to fully FIPS compliant encryption. There might be a way to change what VMware accepts on the otherside so limiting your network to FIPS compliant algorithms still lets you use SSO for VMware, but for me, I'm on a development network, so I just pushed out the above fix via GPO for the time being. I disabled the System Cryptography policy as well as it was preventing some other software from working, but for VMware SSO, you probably only need the Kerberos encryption one.
Hope this helps.
