Based on that log output, I suspect that the VS2013 installer would also fail if you manually executed it as System (via psexec /s ). The system account's domain is "NT AUTHORITY", not the local computer name or domain name. It looks like that's a bug in the installer package for VS2013, and people have run into the same problem trying to deploy it via SCCM (see http://social.msdn.microsoft.com/Forums/vstudio/en-US/4db66392-1d67-42bd-8775-9d8ff829724c/deploying-vs-2013-test-professional-with-sccm-2012?forum=vssetup ). Looks like you can get it working by fiddling with the MSI package and making it skip that "CreateUser" action.
↧
