The original SCCM package command line is "cscript.exe xxx.vbs". Most of the time the failure is 0x80070103.
Steve From: Daniel Ratliff <[email protected]> To: "'[email protected]'" <[email protected]>, "'[email protected]'" <[email protected]> Date: 05/30/2013 02:49 PM Subject: RE: [MDT-OSD] Dynamically Installing Applications with SCCM 2007 R2 Sent by: [email protected] Yeah we have to do that for all our OSD pieces. -----Original Message----- From: Mark Mears [[email protected]] Sent: Thursday, May 30, 2013 05:35 PM Eastern Standard Time To: [email protected] Subject: Re: [MDT-OSD] Dynamically Installing Applications with SCCM 2007 R2 Try using the command line of cscript.exe VBScript.vbs and see if that improves things. Thanks, Mark Sent from my iPhone On May 30, 2013, at 5:21 PM, Stephen V Jameson <[email protected]> wrote: I am upgrading our XP computers to Windows 7 and using application replacement / upgrade with PackageMapping the SQL database. All of my applications work just fine from MDT Lite Touch or from SCCM. When I built the apps, they were all set to download and execute on the client and I checked the "Allow this program to be installed from the install software task sequence ..." box one the program. When I quere the PackageMapping table, I get the proper package listing of sitecode0001:program name. This works for programs if they are setup.exe but not xxx.vbs. Does anybody know the trick to get xxx.vbs programs to work? Steve 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.
<<inline: graycol.gif>>
