As I'm sure it has been discussed many times before, the Office 2013 OCT deployment does a horrible job removing all Office 2010 components properly. Even with the option to "remove previous versions of Office before installing" selected, there will still be pieces of Office 2010 lingering behind. It has been reported to me by our support department that this can randomly cause issues with Office 2013.
In these cases, our support group must manually remove the Office 2010 remnants and run a manual repair of Office 2013. Not ideal on 1000 systems.
To bypass all of this mess, I've attempted to add a command line via the Office Config Tool to remove Office 2010 as well as Lync 2010. I have configured OCT to Run a batch filebefore installing Office2013 via the "Add installations and run programs" area. The batch file has 2 lines.
\\<server>\<share>\Office2010\Install\setup.exe /uninstall ProPlus /config \\<server>\<share>\silentuninstall.xml
\\<server>\<share>\Lync2010\LyncSetup.exe /silent /uninstall
Nothing too fancy here. Note that this batch file works as intended if I manually run it from command line on a workstation. So, I know that all of these commands are good. Also note, the sms installer account has access to the server and shares specified in my commands.
This seems like it should be such an easy thing for OCT to pull off, but it just blows right by my batch file as if it doesn't exist. Am I missing something here? What can I do in OCT to ensure that it doesn't ignore this command?
Thanks,
David