Visual Studio Community - Deployment using SCCM

[phil_c]

Hi,

 

Has anybody managed to deploy VS Community using SCCM? I have managed to download the entire package using the /layout command and edited the AdminDeployment.XML file as suggested on most websites. I have also adjusted the cache for SCCM clients so the rather large package can be downloaded (which works). But every time it installs I get the following error...

 

Visual Studio Community failed with exit code 2147762176

 

The command I am using is the basic

 

"vs_community.exe" /AdminFile AdminDeployment.xml /quiet /norestart

 

Has anyone seen this or has it installing cleanly?

 

Thanks

[jpaterson]

have you tried the Dreamspark download VS Profressional? Works fine here with program command line....

 

vs_professional.exe /s /noweb /norestart /CEIPConsent /AdminFile Admindeployment.xml /ProductKey #########################

[jpaterson]

Another less hassle way is build a specific golden image from your base image with it already installed.

[JasonNVSD]

Yes I have. The biggest gotcha is that the "AdminFile" parameter requires a complete path. It's really dumb, but it won't look in the working directory or executable directory for it. My install script looks like this:

 

"%~dp0vs_community.exe" /adminfile "%~dp0deploy.xml" /quiet /norestart

 

Also, it requires .NET Framework 4.6 to be installed (4.5 won't work). When I was working on this, 4.6 wasn't even in WSUS, so I got an offline installer and created an Application for this and deployed it ahead of Visual Studio.

[ersatyle]

I'm not using the admin File but just this command line vs_community.exe /Passive /Full /NoRefresh /NoRestart /NoWeb /L %windir%\temp\VisualStudio2015update2.log (I've dowloaded the .iso).

how do you manage the first run dialog or sign in for the community edition? If you don't sign-in with a microsoft account it's in 30 days trial mode?

thanks

[mrbios]

Make an install.cmd file, plonk it in the same dir as your vs_community.exe, and have that install.cmd contains this command:

vs_community.exe /adminfile %~dp0Admin.xml /quiet /norestart /LOG %SYSTEMROOT%\TEMP\VS_2015.log

 

Then tell the SCCM package to run cmd /c install.cmd, rather than running vs_community.exe directly with the same flags.

 

I've no idea why this works, i never had an issue deploying it with 2013, but 2015 seems to be really fussy and broken.

 

EDIT: Just seen this has been boosted from February, oh well, hopefully it's helpful to someone anyway.