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. Only solution (as I can see it), is to force-copy a “functional shortcut icon” during deployment. After this “fix” (and a test-deployment), my reward was the following message: In Fig 3 target should definitely not be Skype for Business Recording Manger, instead it should be “Skype for Business 2016”. Anyways, I corrected the mistake MS has made. I’m getting very frustrated with all the bugs. Skype for Business shortcut launches “Skype for Business Recording Manager” instead of “Skype for Business”. You also have to add a “ ) and in the Start menu ( \Microsoft Office 2016). below, I’ve added the path/directory \Microsoft Office 2016. This is fixable by editing the shortcut entries. For some weird reason, Office 2016 by default decides to put all of the shortcuts on the start menu WITHOUT a subdirectory – splattered all over the start menu. Additional content/ Configure shortcuts. Features/Set feature installation states:. used a guide from (works very nicely with 2016 also). Setup/Remove previous installations/Remove the following earlier versions of Microsoft Office Programs/ Remove all (here’s a BUGbtw, more on that later on). Setup/Licensing and user interface/ I accept the terms in the License Agreement, Display level: None, No tick in Competition notice, Tick for Suppress modal and No cancel. Setup/Licensing and user interface/ Use KMS client key. Customized the OCT settings according to our needs:. 
From here I ran “setup.exe /admin” to launch the Office Customization Tool (OCT). Fired up a command prompt and navigated to the extracted Office directory. Our version is “Professional Plus” with Volume Licensing. Got a copy of Office 2016 and extracted the iso. I’ll dive right into the steps: Customizing Office 2016 The following procedure describes how to remove any previous versions of Office and corresponding Proofing tools & language packs and replace them with Office 2016 versions. The procedure is theoretically quite the same, but with many different bugs and gotchas. Now I got the honours to do the same for Office 2016. 
I recently deployed Office 2013 SP1 (and wrote a blog post about it).
0 kommentar(er)
