Re: OSDSWDExec.exe and Zero Touch

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Ben,

I think you can define whether you want to use the standard SMSPKGx$ share
used by SMS or choose yourself the location for the source files via UNC when
you create the OSD Deployment Package...by default SMS assumes that using the
SMSPKGx$ share is what you want but you have the choice not to...
--
I''ll fix that for you!


"Bob Mac Neill (MSFT)" wrote:

> I'll have to look into the usage of Server shares vs. DP vs. Share
> Distribution folder within OSDSWDExec.
> To clarify your Packages aren't pushed to DPs at all?
>
> We have tested: Run SWD Program for program with no source, Run SWD Program
> stored on a Share distribution folder & Run SWD Program when Custom Shares
> are used for DP as well as regular cases.
>
> Regards,
>
> Bob | SMS | OS Deployment
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "BDav" <ben.davies@xxxxxxxxxxxx> wrote in message
> news:97ea09f4ae5fee466c0dca1936b9fa1e@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Hi All,
> >
> > I am having problems with using the dynamic package execution that is
> > functionality of Zerotouchinstallation.vbs. I have put the following
> > command line in Customsettings.ini:
> >
> > Packages1=ZZZ0004E-Install - SWBB
> >
> > When the StateRestore phase comes about, the following is logged:
> >
> > OPENING TRUSTED SQL CONNECTION to server ZDC1NM004 and database SMS.
> >
> > Successfully opened connection to database.
> >
> > About to issue SQL statement: SELECT * FROM v_Program WHERE PACKAGEID =
> > 'ZZZ0004E' AND PROGRAMNAME = 'Install - SWBB'
> >
> > Successfully queried the database.
> >
> > Obtained CommandLine value from SQL: CommandLine = msiexec.exe /i
> > "PRO11.msi" /m MSI1SFC4 /L*V
> > C:\WINDOWS\Debug\Apps\MicrosoftOffice2003_11.0_B02_SWBB.log
> > TRANSFORMS=MicrosoftOffice2003_11.0_B02.MST REBOOT=ReallySuppress
> > ALLUSERS="2" /qb!
> >
> > About to execute command: OSDSWDEXEC.EXE "ZZZ0004E:Install - SWBB"
> > msiexec.exe /i \"PRO11.msi\" /m MSI1SFC4 /L*V
> > C:\WINDOWS\Debug\Apps\MicrosoftOffice2003_11.0_B02_SWBB.log
> > TRANSFORMS=MicrosoftOffice2003_11.0_B02.MST REBOOT=ReallySuppress
> > ALLUSERS=\"2\" /qb!
> >
> > WARNING - Non-zero return code from command, rc = -2147467259
> >
> >
> > The package fails to execute, even though it obtains all the correct info.
> > This is the OSDSWDExec log file:
> >
> > Running \\zrsspd001\packages$\SMSPKG\ZZZ00122\OSDSWDEXEC.EXE
> >
> > PackageID: ZZZ0004E
> >
> > ProgramID: Install - SWBB
> >
> > Trying OSD package DP first
> >
> > Shared environment successfully initialized
> >
> > CHECK FAILED: false (Error = 80070003)
> >
> > CHECK FAILED: (PathFolderExists(sWorkingDir)) (Error = 800700B7)
> >
> > Folder does not exist. \\zrsspd001\packages$\SMSPKG\ZZZ0004E
> >
> > Could not get package location on OSD package DP. Code 0x800700b7
> >
> > Using site code: , Management Point:
> >
> > CHECK FAILED: false (Error = 80004005)
> >
> > Could not find any DP. Code 0x80004005
> >
> > CHECK FAILED: GetPackageLocationFromMP(sPackageID, sWorkingDir) (Error =
> > 80004005)
> >
> >
> > We use Server Shares for our distribution points, so we create the folder
> > name where the source files are located, then set that path up in the
> > package. The directory that it is attempting to find the source files does
> > not exist so clearly that is why it is failing. Does anyone know of a fix
> > for this as it appears to be a bug of the OSDSWDExec that it assumes that
> > the files will be in SMSPKG.
> >
> > Any help would be much appreciated!
> >
> > Cheers!
> >
>
>
>
.



Relevant Pages

  • Re: Distribution Point directory structure question
    ... > When you create a package, SMS lets you choose on a package-by-package basis ... > if you want to get source files at all, and if so, where to get them from. ... > share anywhere on the network and point SMS there. ... > SMS will create a compressed version of the source files on the site server. ...
    (microsoft.public.sms.admin)
  • Re: Distribution Point directory structure question
    ... When you create a package, SMS lets you choose on a package-by-package basis ... if you want to get source files at all, and if so, where to get them from. ... SMS will create a compressed version of the source files on the site server. ...
    (microsoft.public.sms.admin)
  • Re: actxprxy.dll How to register on clients
    ... Here's a clip from myitforum.com (good resource for sms questions) ... You create packages without source files by not selecting the checkbox ... entitled 'This package contains source files' when you setup your package ... You could specify as your command line ...
    (microsoft.public.windows.server.general)
  • Re: actxprxy.dll How to register on clients
    ... Here's a clip from myitforum.com (good resource for sms questions) ... You create packages without source files by not selecting the checkbox ... entitled 'This package contains source files' when you setup your package ... You could specify as your command line ...
    (microsoft.public.windowsxp.general)
  • Re: actxprxy.dll How to register on clients
    ... Here's a clip from myitforum.com (good resource for sms questions) ... You create packages without source files by not selecting the checkbox ... entitled 'This package contains source files' when you setup your package ... You could specify as your command line ...
    (microsoft.public.windows.inetexplorer.ie6.browser)