can't get Headless Install to work

[neoswarm]

don't know if this is something you can help.....

Windows 7 Pro
VSTO Outlook 2010 32 bit

My client needs a headless install (to allow IT admins install on other machines).....when I try to launch the installer from the SYSTEM user shell, i get the error:

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.

Attached is my setup.aip file

I was able to get the headless installer to work if I:
* removed the moved prerequisites packages from pre-install to feature based and
* created only a 32 bit installer (it's currently mixed 32/64) and
* change to an MSI installer (previously .exe)

I'm pretty sure the boostrapper files are decompressing the MSI to the wrong c:\windows\SYSTEM32\config\systemprofile\appdata directory ---- CAN I CONTROL WHERE THOSE FILES GET DECOMPRESSED? If so, how can I do that?

thanks!
mike

p.s....here's the steps how I'm testing it:
• Download pstools from MSFT
o http://technet.microsoft.com/en-us/sysi ... 96649.aspx
o All you have to do is unzip it
• Open a admin cmd shell (right click on cmd and choose runas)
• CD to wherever you unzipped pstool
• Run "psexec.exe –s –i cmd"
o This will launch a cmd shell as the SYSTEM user
• In this new command shell, CD to wherever you have the RT OP installer
• Launch the installer from SYSTEM user shell

[Daniel]

Hello,

Unfortunately, this behavior is caused by a bug in Advanced Installer. It reproduces when a mixed 32/64-bit installation package is launched under SYSTEM account. What happens is that the bootstrapper seems to not extract its contents in the correct location, when a per-user extract location is used. This probably happens because its running under the system account, we don't know yet, but we will investigate and fix this.

In the meantime the solution for you is to use a per-machine extract location, which you can change in "Media -> Configuration -> Extract Location" field. For example you can use a per-machine extract location like this:

Code: Select all

[TempFolder]install

Let us know if this helped.

All the best,
Daniel

[neoswarm]

Okay thanks!

I think I have a work-around for this.....but will use this solution as a fall-back if necessary.

Happy debugging!
mike

[Daniel]

You're welcome. I'm glad you got this working.

All the best,
Daniel