Deploy Office 2010 error 30099
I'm not sure where to look on this or if there is more verbose logging that can be setup.
I'm looking at trying to upgrade a few machines from 2007 to 2010. I went through this article to get the initial .MSP file made - https://www.adminarsenal.com/blog/remotely-install-office-2010-part-1-office-customization-tool/
The only other configuration I did in OCT was what was in that article and this article: https://www.adminarsenal.com/blog/remotely-activate-office-microsoft/
When trying to do the deploy it goes through the file copy process and a few seconds later it fails with the following error:
setup.exe returned error code 30099
Searching around a bit I haven't been able to find reliable information on the error. When login to a box and run the commandline myself (setup.exe /adminfile mymsp.msp ) it goes through.
This is deploying Office 2010 x32 to a machine that has 2007
I still have a few things to test but wondering if anyone has seen something like this. I can push install any other package provided by adminarsenal
Comments
Please take a screenshot of your Install step.
Attached
That looks great.
How much free space does your target have?
I have tried on a couple different machines and looking at around 40GB (ish) free. It doesn't seem to be a free space issue. When I watch the adminarsenal directory live I can see it go through the copy process.
Also, thank you for taking the time to respond on this. I feel like I'm missing something obvious, this is my first time trying to test building a package.
Office is a real pain in the butt sometimes. It's probably not liking something to do with the upgrade from 2007 to 2010.
Are you trying to install them side-by-side, or remove 2007 and install 2010 in its place?
Well, I remoted to one box and copied the office install directory along with MSP file. I executed from the command line and while watching the process it pulled out 2007 before putting in 2010. The only changes I made in OCT were the ones mentioned in the above links which were basic suppression of dialogs and installation key. Also an after install calling of a vbs script for pushing activation.
I'm going to stand up a different image today that has no office or other software to see if that is successful. I probably should have started at this point but when I saw success running from the command line I thought it might be something with how I'm configuring the package.
When trying to automate office upgrades with PDQdeploy is it a better strategy to have a separate uninstall and then a follow-up install?
When I have to push office to something without re-imaging , I try to clean off the old versions before I put new on....but 98.5% of the time in my case if something goes wrong with anything software related on a machine I just kick off an Image and let FOG and PDQ bring all the software it needs back up to date and in a working order. That's a 30 second fix and the problem resolves itself and I can focus on more important things. Like.....Powershell, and this forum. Haha.
I second @Stephens "Pain in the butt" statement.
Let us know how it does standing up the image and testing but I would almost bet money that it wants a full clean uninstall of Office 2007 and then a clean install of Office 2010.
Your inclination to add an uninstall step seems valid to me.
Thanks guys, will keep you posted.
While I was standing up an image I was doing some testing. I think I narrowed it down to needing to be runas deploy user (interactive). When I changed that it started going through.
I tested on a fresh box and it worked and then did a few tests on other machines which also seemed to work. I made a few modifications to the MSP to fix activation and suppression of the first run wizard thing.
I stumbled upon the setting to interactive when I saw a workaround to unrelated errors here -https://support.adminarsenal.com/hc/en-us/articles/220509667-Deploy-Office-2016-using-the-Microsoft-Office-Customization-Tool
Because I'm installing silently it doesn't engage the user so I think I have a workable solution. Thanks again guys for chiming in on this, hopefully this will help someone else if they get that weird 30099 error.