Now that I'm one for one with my last MST, I decided to go ahead and try to create a transform for Attachmate Extra!. Anyway, it only installs while logged in. It wont install "Assigned" through GPO.

This is version 8 "Extreme". Anyway I used Install Tailor to create an MST. Then I went and edited the MST with Install Editor. The only thing I changed was "Administrator Options" and changed the Install type to "Per Machine".

I am assigning the MSI/MST through GPO. When I reboot the machine it tries to install Extra but it fails. If I log in and run the MSI manually (with the transform), it installs correctly.

I turned on GPO logging and get the following entires...

[font="Courier New"]Found 0 applications locally that are not included in the set of applications from the Active Directory.
Application Attachmate EXTRA! X-treme 8 from policy Install_Extra 8 Extreme is set for installation because it is assigned to this computer policy.
Assigning application Attachmate EXTRA! X-treme 8 from policy Install_Extra 8 Extreme.
Calling the Windows Installer to advertise application Attachmate EXTRA! X-treme 8 from script C:\WINDOWS\system32\appmgmt\MACHINE\{c80b6ae8-b6ff-41a6-a787-bd40398e9d45}.aas with flags 69.
The assignment of application Attachmate EXTRA! X-treme 8 from policy Install_Extra 8 Extreme succeeded.

Calling the Windows Installer to install application Attachmate EXTRA! X-treme 8 from policy Install_Extra 8 Extreme.
The install of application Attachmate EXTRA! X-treme 8 from policy Install_Extra 8 Extreme failed. The error was : %1603

Removing application Attachmate EXTRA! X-treme 8 from the software installation database.
Calling Windows Installer to remove application advertisement for application Attachmate EXTRA! X-treme 8 from script C:\WINDOWS\system32\appmgmt\MACHINE\{c80b6ae8-b6ff-41a6-a787-bd40398e9d45}.aas.
The removal of the assignment of application Attachmate EXTRA! X-treme 8 from policy Install_Extra 8 Extreme succeeded.


Windows Installer Error 1603 just says "Fatal Error". I tried to turn on Installer Logging be adding "Logging"/"voicewarmup" to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer but it doesn't appear to be dropping a log file in %TEMP%. Is this the correct registry key and directory?

I know that this application does create some folders in the user's "My Documents" so is it possible that it can't do what it needs to do because there IS no user? I was under the impression that any "user" configuration portion of the install would fire off when the user logs in. This seems to be how Office and other applications handle it.

Anyway, hope this made sense. If anybody could shed some light on this I'd appreciate it.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
First off, bookmark the Windows Installer Error Reference on MSDN:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/windows_installer_error_messages.asp

Error 1603 is The file [2][3] is being held in use by the following process: Name: [4], Id: [5], Window Title: '[6]'.

You're correct about the user data portion, but that's only if the install meets Windows Installer standards. If the vendor added custom actions (Some applicaiton developers can't seem to resist getting "fancy" like that), and the CA assumes that a user ID is up and available, it will fail when deployed per-machine with nobody logged in. I bet that's what is happening.

I don't know about that registry key for the log, I use another distribution tool which always captures the log. But you need to get an install log because it will tell you exactly what file the problem is occurring in and what's holding it in use.
Answered 09/16/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity