/build/static/layout/Breadcrumb_cap_w.png

Visual Studio Premium 2013

Hey,

i want to deploy VS2013 silent with SCCM to an Windows 8 Client and have a question.

The silent installation failed with an unkown error code, which i can see in the AppEnforce.log (exit code 34371)

To test the installation i decided to start the powershell script manually and got the following review as result.

VS2013 seems to work, i could start it without any issues.

Did anyone know something about this and have an advice for me?

 

Please help!

 


1 Comment   [ + ] Show comment
  • download the iso again. - Sidhugadu 9 years ago

Answers (2)

Answer Summary:
Posted by: Sidhugadu 10 years ago
3rd Degree Black Belt
1

Issues with the source. try to redownload the ISO and everything should be fine.

Posted by: rileyz 10 years ago
Red Belt
0

Did you install those pre-reqs first?

I would suggest you install the pre-reqs instead of the package installing it for you, it adds in a lot more work, but if you add it into SCCM as a install task then you can check it as part of the logging (from sccm).

When you let the package install the pre-reqs, it can be a bit hit and miss weather it installed the pre-reqs ok, like in this case.

On a side note, if you use powershell to do the install, your hiding the reporting from SCCM, so your not getting the best from SCCM reporting.

 

Anyway, for the above - get a clean machine and take note of what is in the add/remove programs. Install VS 2013 and see what pre-reqs it installed. Once you know that you can add that as part of the install before VS2013 installs, should cover off your problem.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ