![]() That’s it! All the other options are the same as with a regular deployment, you just add the Supersedence-information (so Office 2013 SP1 can be successfully removed while installing Office 2016). Replacement Deployment Type: Microsoft Office Professional Plus 2016 installer ![]() Old Deployment Type: Microsoft Office Professional Plus 2013 SP1 installer This application supersedes the following applications: With all the parameters done, you can now deploy Office 2016 using Office 2013 as Supersedence (see screenshot below) :Īll of the fields aren’t visible in the screenshot, but the fields are: This in turn means it won’t be successful. If you don’t specify a xml file, the uninstallation won’t be silent. You’ll then use this xml file when you specify the uninstall string for Office 2013 SP1 in SCCM. This file contains only the following information: (The reason for this is also a bug, see my Office 2013 deployment post). I’m already using “custom.xml” (together with OCT) for the installation part, so I’ve created a custom2.xml for the uninstallation part. 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. This shortcut will then be deployed as a dependency.(You should also remove all the Skype for Business shortcut entries in OCT). With functional I mean a shortcut that has been manually created from C:\Program Files (x86)\Microsoft Office\Office16\lync.exe. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |