Basically we need to use a custom config.xml file to instruct the setup program to perform a quiet uninstallation. The Setup command-line options reference for Office 2013 on TechNet has a helpful section describing uninstallation. Silent UninstallationĪs we did in the Customizing Setup post, we will consult the Office 2013 documentation to help us. Next time, we’ll use our new Applications along with our Offscrub package to build a task sequence for deployment. Then we’ll walk through the Application-building process.
That takes a little bit of work, and so we’ll do that first.
This provides Software Center with the ability to remove it, thus giving users an “app store” experience. One of my rules for a Configuration Manager Application is that it must have an uninstallation command. There is just one bit of housekeeping to take care of first. It’s been a long process, but it’s finally time to build the Application objects in System Center Configuration Manager for Microsoft Office and its sibling programs.