Simple Office 2013 MSi

[nblinstrub]

We use LANDesk Management Suite to deploy packages to our 25,000 computers. Packages are installed running as the Local System Account.

I have built packages for Microsoft Office Professional Plus 2013 and Office Standard 2013. I used the project wizard, finding it the most successful for the type of installs we usuallyt build.

PROBLEM: The packages (single-file MSIs) run flawlessly when installed from a network share, a website, or the local file location the file is downloaded by a LANDesk install. I installed the package on Windows 7 64-bit logged in as myself (an Active Directory account that is a member of the local Administrators group).

Our LANDesk deployments install packages as the Local System Account.

My package installs the "installer," which puts the Office administrative install in a typical Program Files location, but the final action, which just runs the "setup.exe" to install Office, never executes when deployed by LANDesk (as the Local System account).

[Daniel]

Hello and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.

Please keep in mind that custom actions scheduled during "Wizard Dialogs Stage" or "Finish Dialogs Stage" (UI execution stages) are executed only when the installation is launched with Full UI. So, if you will install your package in silent mode or with basic UI your custom action (scheduled in "Finish Dialogs Stage" ) will not be executed. However, can you move your "LaunchApplication" custom action after "Install Execution Stage -> Finish Execution -> InstallFinalize" standard action and see if the behavior still persist?

All the best,
Daniel