I've built a new package to deploy Office 2013 Standard, but it isn't deploying correctly.
We have an existing Office 2010 deployment package that works well, so I used it as a template for the 2013 package. Just updated the .msp and the batch file to point at the new stuff. I've attached a copy of the batch file I'm using to run it all.
Basically it does the following...
- Unpack a .zip to C:\media\office2013win\
- Copy the .MSP to C:\media\office2013win\updates\
- Run setup.exe
If I run the batch file manually, it does exactly what I expect it to.
If I use LANDesk to deploy the batch file it will download all the files correctly, unpack things to C:\media\, and then just kind of hang there doing nothing.
It appears that setup.exe, even with a .msp that's configured to run silently, isn't actually running completely silently. Despite the .msp attempting to completely suppress the UI, I'm still getting a brief splashscreen when setup.exe kicks off. This did not happen with 2010. I'm guessing that setup.exe is still trying to run in some semi-interactive manner, which is causing issues since it is running as the LocalSystem account.
I can confirm that the .msp is being processed, since the right options are installed with the right license key. But it doesn't seem to be running completely silent.
Has anyone else run into this issue? Does anyone else have a working Office 2013 deployment package? Is there something obvious I'm doing wrong?