Deployment Question Regarding Office

[NullSID]

So I have about 100 pc's with a 64 bit version of Office.

I need to blow away the existing version and install 32 bit Office.

 

I built the uninstall scripts and tested it. Those work fine. My question pertains to updating the existing deployment.

 

I need to make the uninstaller the first step in the program then install new Office.

 

I think I can just add the program, make it dependent on a specific folder/file to run. Has anyone had issues with modifying existing deployments that are attached to a bunch of other collections? My concern is it is going to run on all pc's if I update the deployment.

 

Any suggestions? I thought about copying the existing deployment adding the step and just deploying it to the spec Fix collections affected.

 

Any tips or thoughts would be helpful!

[tregelen]

Anything like that I tend to use (and infact I use it for all my packaging) the PowerShell App Deploy Toolkit http://psappdeploytoolkit.com/

 

See how that goes.

[NullSID]

Ah that's a good idea. I ended up using a Task Sequence to uninstall Office 2010 and install Office 2013 this time. The dependencies are a gigantic pain in the arse sometimes and really difficult to troubleshoot.