In order for Office 2013 SP1 to be silently removed via SCCM before you install Office 2016, you have to be sure that the uninstall string is correct and a custom xml-file is in place. The remove previous version-feature works with Office 2010 however, which means I don’t have to create a supersedence relation for that version (luckily).Ĭhecking parameters for Office 2013 uninstallation: In this case the changes were about uninstalling Office 2013 SP1, as a fully patched Office 2013 SP1 WON’T get uninstalled even though I’ve chosen to remove previous versions in the OCT(see my (unanswered) post at ). As with Office 2013, I basically followed a (very good) guide from with some changes for our environment. Instead I got to fiddle with SCCM’s supersedence and dependencies. The deployment part was quite straight forward after the customization part was done. Skype for Business – example shortcut entry.ĭeploying Office 2016/Removing Office 2013/2010 See later chapter about dependencies.įig 3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |