- #Top msi wrapper with sccm install#
- #Top msi wrapper with sccm software#
- #Top msi wrapper with sccm code#
- #Top msi wrapper with sccm professional#
#Top msi wrapper with sccm install#
net 4.5.1 install is failing somewhere but i cant really figure out why. I351: Removing cached package: netfxfullredist_43, from path: C:\ProgramData\Package Cache\5934DD101414BBC0B7F1EE2780D2FC8B9BEC5C4D\ I319: Applied execute package: netfxfullredist_43, result: 0x80074005, restart: None I000: MUX: Set Result: Return Code=-2147008507 (0x80074005), Error Message=, Result Detail=, Vital=True, Package Action=Install, Package Id=netfxfullredist_43 I000: MUX: Return Code:0x80074005 Msi Messages:0 Result Detail:0 Restart:None I000: MUX: Installation size in bytes for package: netfxfullredist_43 MaxAppDrive: 0 MaxSysDrive: 69464512 AppDrive: 0 SysDrive: 69464512 The log created from the VS installer shows the following errors:Į000: Error 0x80074005: Process returned error: 0x4005Į000: Error 0x80074005: Failed to execute EXE package.Į000: Error 0x80074005: Failed to configure per-machine EXE package.
#Top msi wrapper with sccm code#
Log from SCCM shows failure with exit code 1603. however, when it attempts to run with no user logged in, it fails.
#Top msi wrapper with sccm software#
this works fine when a user is logged in and clicks the Install button in SCCM Software Center. I have the user experience set to install for system whether or not a user is logged in. Vs_testprofessional.exe /quiet /log C:\VS2013TP.log /NoWeb /Full
#Top msi wrapper with sccm professional#
i am trying to set up an unattended deployment of vs 2013 test professional through sccm 2012. Don't assume non-standard things.Im really banging my head here so i hope someone can help. Follow MSI best practices (too many to list here) if you use an MSI which I highly recommend. Make sure your unattended installation procedures work. Don't hide an MSI in an exe having a wrapper exe is OK, just don't hide the MSI. Don't wrap and exe by an MSI, that's just plain lazy. Add things to the All Users Profile when necessary during installation. ConfigMgr uses the local SYSTEM account to run installations and this account has no profile. Don't assume that a profile will be present during installation this includes things like an HKCU registry hive or desktop. Don't require admin access for your app the installer can require admin access though. Some of these have already been called out in the other comments but here's a quick list off the top of my head: 1. Jason | | | Twitter whole-heartedly agree with all of the other comments and would like to stress that your application, more importantly you application installation routine should follow normal Microsoft standards. I whole-heartedly agree with all of the other comments and would like to stress that your application, more importantly you application installation routine should follow normal Microsoft standards.