1603 is fatal error from the MSI. What does your install log show? I think with VS it's a bunch of HTML logs in Program Files?
Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Tuesday, November 25, 2014 12:41 PM To: [email protected] Subject: [mssms] Deploying Visual Studio 2013 - error 1603 When I try to silently deploy VS Premium 2013, I get "unmatched exit code 1603" in AppEnforce.log. The program partially installs, but will not run. I have .NET 4.5.1 as a dependency, it installs fine. Below is my script that executes the install: @echo off :set location set loc=%~dp0 :install "%loc%vs_premium.exe" /adminfile "%loc%AdminDeployment.xml" /quiet /norestart If I run vs_premium.exe /adminfile AdminDeployment.xml /quiet /norestart locally from an admin command prompt (inside the source folder, natch), it installs fine. My Googling has found many possibilities, but they don't seem to match what I'm experiencing. Any ideas? Best Regards, Mike Murray Desktop Management Coordinator - IT Support Services California State University, Chico 530.898.4357 [email protected]<mailto:[email protected]> The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
