Thanx for reading this and hopefully you’ll have some better insight on how to do this better.
I’m trying to deploy an .EXE file to end users systems to upgrade MS Office 2003 from Office XP. We have a script that was created that handles all our custom settings and confirgurations and tested it on a number of local machines.
The problem comes when I try to deploy it via BigFix. I went through the Software Deployment Wizard and set the relevance criteria. I get the proper number of systems reporting back as needing the upgrade but when I set it to deploy, the deployment runs properly but for some reason the script doesn’t update the Office application correctly and the user gets an error message.
Hopefully this makes sense, I’ve been working on trying to solve this for a couple of days now and my head is now spinning.
When you run your EXE through BigFix you have to consider that it will be running under the SYSTEM account and will have the SYSTEM accounts permissions/rights on the local machine. This is a frequent sore spot.
If you are doing your upgrade using an MSI administrative install from a network share, the SYSTEM account will not have access to that share and it would fail to run.
Is your Office deployment per user or per machine? If it is a per user deployment, you might have to have the Update.EXE run with the user logged on and under the user’s context.
Either way, you might test out using the RunAsCurrentUser utility mentioned in this thread: