Systems Management

Care to share your command lines and/or installation scripts for OWC11? It sounds like whatever you're running for Office Web Components is not waiting for the executable to finish before reporting exit code 0 to the sequencer engine.

This is all I am using for the command line: owc11.exe /quiet

The only parameters that a /? is showing for the .exe is /quiet and /extract:path

Blake,

A couple of things to look at..

The Office Web Components executable extracts an .MSI file - you might get a bit more info if you log the installation of that file - the task sequence will be launching the MSI rather than an .exe that is then launching an MSI.

The other thing, could anything else be deploying software to the machine outside of the task sequence? Anti-virus agent that's pulling down a program that is then installing? Or how about an package that's advertised to all computers, your machine will be available for this deployment even though the task sequence is still in control of the machine.

Hope this helps,

Dunnpy

ORIGINAL: aslander

This is all I am using for the command line:     owc11.exe /quiet

The only parameters that a /? is showing for the .exe is /quiet and /extract:path



You might consider extracting the MSI out of it, and calling the MSI directly. There's a pretty good chance that OWC's executable terminates before the MSI install is complete. I'm not 100% certain on OWC, but I do know that many other (poorly designed) programs behave this way. SCCM only tracks the executable you have specified on the command line, so once the owc11.exe ends, SCCM thinks that the program is complete.

You also mentioned some other programs in your chain do this. Are they all .exe's with quiet/silent modes enabled?

Echo?

[:D]

Okay, it does in fact extract a MSI file, but not to the normal folder (Local Settings\Temp).

Instead, OWC11 extracts the files to c:\Program Files\MSECache\owc11_12\

I found the MSI and some other files in there, so I will see if changing the package to that MSI will fix the issues. I'll keep you guys posted, thanks for the help so far!

Not much luck, it works fine from the command line. I am using:

msiexec.exe /i owc11.msi /qn

this works fine when I try it from command prompt on a test system, but fails during the task sequence with the following error:

Windows Installer per-user elevation of this program ("10000031" - "Install v2") failed for advertisement "10020014". The operating system reported error 1619: This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. This program was started. Please check the status of this program to determine whether or not it was completed sucessfully Possible causes: The version of Windows Installer on the computer is less than version 2.0, or the setup program does not support Windows Installer per-user elevated rights installations. Possible solutions: Update the version of Windows Installer on the computer to version 2.0 or later, or contact the software vendor that supplied the install program to determine if a version of setup that supports per-user elevated rights is available.

I presume that, although you don't show it, you're specifying the full path to the MSI in the command line?

Try tossing an ALLUSERS=1 into the command line there. As far as I recall, SCCM can't elevate to a user account when you begin a command from the system account. It sounds like OWC is defaulting to looking for a user account to install from, ALLUSERS=1 should take care of that.




VBScab: Unfortunately you can't really specify full paths with SCCM, the Distribution Point model necessitates relative paths. The best you can do from OSD is to use the %SMSDP% variable, which points the task sequence to whichever DP you've downloaded the image from. I believe you'd still need to append the package name after it as well, making it pretty painful to use when relative paths work (nearly) as well.

I'll give that a shot and let you guys know. Thanks

I was intrigued by your use of ALLUSERS=1in an msiexec command line to elevate user privileges. Does the ALLUSERS=1help with current user settings being applied during an install? In the past I have separated out the current user settings and applied them “as the logged on user”, but of course, this is a pain, so I’m hoping this an option for future deployments. Thank you for your patience!

use of ALLUSERS=1in an msiexec command line to elevate user privileges Tootle on over to MSDN/TechNet and have a read on the ALLUSERS property.