The issue with vbs run is its looking for the file in the wrong location (where ever the default path is). If you open a cmd window and don't cd to the directory of your script and run it with the full path you should be able to recreate the problem. I have found scripts so you figure out where the vbs file is so you can run the full path to your exe. I am ooo so I don't have any examples but I bet this is your issue.
Wade -------- Original message -------- From: Stephen V Jameson <[email protected]> Date: 06/05/2013 8:51 AM (GMT-06:00) To: [email protected] Subject: [MDT-OSD] DynamicPackaging running EXE's I am using DynamicPackaging to replace applications when I upgrade to Windows 7. I have my standard SCCM Packages that work very well. I have a package that is "Install NotePad". In SCCM packages I start the install by calling "cscript.exe NotePad.vbs". In the vbs script I use objshell.run "NotepadInstaller.exe /S, 1, TRUE". Then copy some dll's to the notepad folder. This works well in MDT or SCCM., but not in DynamicPackaging. If I have a msi instead of an exe DynamicPackaging works. How can I call an exe inside of a vbs script to made this work?? Steve
