again, the setting on the TS over-rides anything on the "package" about download and execute or run from DP.
Now, if you are asking how to rewrite you code to run from DP then fine, but do not think that because it runs as an advertised package that it will run during OSD when you have the TS set for DL&E On Thu, Jun 6, 2013 at 10:28 AM, Stephen V Jameson <[email protected]>wrote: > Here is a piece of the code: > > strpath = objshell.currentdirectory > objoutputfile.writeline "Current directory is : " & strpath > errLevel = objshell.run ("notepad.exe /S", 1, TRUE) > > this will fail with an errLevel code of 1 but the current directory is > correct and the notepad.exe is in the current directory > > If I have an msi like this > strpath = objshell.currentdirectory > objoutputfile.writeline "Current directory is : " & strpath > errLevel = objshell.run ("msiexec.exe /q /i product.msi") > > this will work > > All of my SCCM packages are set to download and execute. The upgrade > tasksequence is set to run from the distribution share. I have tried to > run this application from the distribution share as well but the result is > the same. > > Steve > > > > [image: Inactive hide details for "Atkinson, Wade A" ---06/05/2013 > 02:54:40 PM---So your run command in the vbs includes the full path]"Atkinson, > Wade A" ---06/05/2013 02:54:40 PM---So your run command in the vbs includes > the full path to your exe? Wade > > From: "Atkinson, Wade A" <[email protected]> > To: "[email protected]" <[email protected]> > Date: 06/05/2013 02:54 PM > Subject: RE: [MDT-OSD] DynamicPackaging running EXE's > Sent by: [email protected] > ------------------------------ > > > > 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 > > > > [image: 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 > >
<<graycol.gif>>
