So your run command in the vbs includes the full path to your exe? Wade
-------- Original message -------- From: Stephen V Jameson <[email protected]> Date: 06/05/2013 12:57 PM (GMT-06:00) To: [email protected] Cc: [email protected] Subject: RE: [MDT-OSD] DynamicPackaging running EXE's Thanks Wade, I have a line in the vbscript that writes the current directory to a file and some other debug stuff. If I run this package as a regular SCCM package (as download and execute), the current directory is C:\Windows\.....\cache\... and everything works just fine. If I run this package thru a task sequence and DynamicPackaging (reading from the SQL database to see what is installed), the current directory is \\distribution point\packageID. So in both cases the vbscript starts but the objshell.run(notepad.exe) does not run in the DynamicPackaging. I just tried opening a cmd window and running the exe from a full path and it works. Now what?? Steve [Inactive hide details for "Atkinson, Wade A" ---06/05/2013 10:22:46 AM---The issue with vbs run is its looking for the file in]"Atkinson, Wade A" ---06/05/2013 10:22:46 AM---The issue with vbs run is its looking for the file in the wrong location (where ever the default pat From: "Atkinson, Wade A" <[email protected]> To: "[email protected]" <[email protected]> Date: 06/05/2013 10:22 AM Subject: RE: [MDT-OSD] DynamicPackaging running EXE's Sent by: [email protected] ________________________________ 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
<<inline: graycol.gif>>
