See my reply to my own post below...I was interested in seeing the difference between the volume license build and the Office 365 build of MS Office 2016. Was referred to Rich's post. Had read it it and was insightful, but wanted to understand Microsoft's logic in creating this weird installer. I think I get it now and posted my findings below. Basically, I figured out how the com.microsoft.office.licensingV2.plist file is generated during installation in the GUI.
Page 7 / 7
@donmontalvo Read up bro, I explained earlier
Posted: 1/5/16 at 5:30 PM by calumhunter I don't understand how people are having so much difficulty with all this. Its about as simple as can be. Take the Microsoft_Office_2016_Volume_Installer.pkg from the VLSC portal and install it any way you like -> DONE OR Take the office 365 installer package from the publicly available MS site i.e. the Retail/non VL version. Install that first, then install the VL serialiser package -> DONE No mess, no fuss. /Shrug
I'll try to clarify a bit more.
The reason someone might choose to use the retail/0365/sku-less version is that this gets updated sooner than the version on the VLSC site.
For example only recently there was the 15.16 version available from MS as 0365/sku-less but the VL version on the VLSC portal was 15.14.
So if you want to be on top of the latest version, always grab the retail/0365/sku-less version then serialise it with your vl serialiser package.
Right but for those of us using VL only, no need to run both the VL installer and VL serializer. Correct?
yes i would like some clarification my self.
Do i just add the install pkg to the install list and the serializer?
Or is the serializer ran after-install?
What if i just build office 2016 into the MAC os image its self can i run the serializer during the imaging process?
If you're installing Microsoft Office 15.17 or higher, there is no need for the serializer during imaging
So i just add the office install pkg to list of programs to be installed during the imaging process and that it?
I dont do anything post install, after the imaging process...
Yes. You can check for it, and it will be activated. The serializer is meant for people who want the latest version of Microsoft Office from O365, then use the serializer to activate it.
Also, if you were using the .plist copying method of activating Office, you'll need to deploy the serializer to re-activate Microsoft Office.
Ok i added the PKG directly to casper not editing and it still will not work it install the application but when i go to launch them i get the below.
#!/bin/sh
√Process: Microsoft Word [735]
Path: /Applications/Microsoft Word.app/Contents/MacOS/Microsoft Word
Identifier: com.microsoft.Word
Version: ???
Code Type: X86 (Native)
Parent Process: ??? [1]
Responsible: Microsoft Word [735]
User ID: 501
Date/Time: 2016-01-13 12:16:00.912 -0500
OS Version: Mac OS X 10.11.2 (15C50)
Report Version: 11
Anonymous UUID: 005799DB-0850-F6C9-F855-B85C80FE7DF7
Time Awake Since Boot: 82 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: @rpath/mbukernel.framework/Versions/A/mbukernel
Referenced from: /Applications/Microsoft Word.app/Contents/MacOS/Microsoft Word
Reason: image not found
Binary Images:
0x8fefb000 - 0x8ff2f5cf dyld (360.18) <25D51D2B-794C-3911-9EEE-B1F0035D7104> /usr/lib/dyld
Model: iMac12,2, BootROM IM121.0047.B1F, 4 processors, Intel Core i5, 2.7 GHz, 4 GB, SMC 1.72f2
Graphics: AMD Radeon HD 6770M, AMD Radeon HD 6770M, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x02FE, 0x45424A3231554538424655302D444A2D4620
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x02FE, 0x45424A3231554538424655302D444A2D4620
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x9A), Atheros 9380: 4.0.74.0-P2P
Bluetooth: Version 4.4.3f4 16616, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: ST31000528AS, 1 TB
Serial ATA Device: HL-DT-STDVDRW GA32N
USB Device: USB 2.0 Bus
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Keyboard Hub
USB Device: Apple Optical USB Mouse
USB Device: Apple Keyboard
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: USB 3.0 FD
USB Device: IR Receiver
USB Device: Card Reader
Thunderbolt Bus: iMac, Apple Inc., 22.1here is my choicechangesXML. It is not installing OUTLOOK (like intended), but I still see 'check for updates' under help menu. I am getting that stupid popup saying
You are opening the application “Microsoft AutoUpdate.app” for the first time. Are you sure you want to open this application?
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<array>
<dict>
<key>attributeSetting</key>
<integer>0</integer>
<key>choiceAttribute</key>
<string>selected</string>
<key>choiceIdentifier</key>
<string>com.microsoft.outlook</string>
</dict>
<dict>
<key>attributeSetting</key>
<integer>0</integer>
<key>choiceAttribute</key>
<string>selected</string>
<key>choiceIdentifier</key>
<string>com.microsoft.autoupdate</string>
</dict>
</array>
</plist>
I think it might be from my Office 2011 installation. I installed office 2011 but I'm guessing it left mau2.0
going to test again.
@talkingmoose wrote:
Run the standalone VL Serializer (also coming in January) just for those installations where you copied a com.microsoft.office.LicenseV2.plist file from machine to machine. This will fix their license files (make them unique to each machine) before Microsoft fixes its bug that allowed you to copy it in the first place.
My apologies if I'm beating a dead horse. But is there any harm in including the VM Serializer on a policy hitting a computer that may not have a captured com.microsoft.office.LicenseV2.plist file?
I'll be in purgatory, and thus will take my answer offline.
TIA,
Don
the VL serialiser package on its own will not create the com.microsoft.office.licence plist
You must install the office suite installer package, or standalone application package first.
This sets up the licence helper files
Then you can use the VL serialiser package to create the V2 plist
If you haven't already, read through this blog
https://clburlison.com/demystify-office2016/
@calumhunter got it, that was the missing piece of the puzzle (along with your below post from a few days ago). I haven't had time to keep up with Slack. So whether the V2 plist exists or not, no harm in running the VL serializer package. This makes policy creation/management much mo' simple. Danke very mucho!
the process is the same. currently the 15.17 serialiser does not remove/overwrite an existing v2.plist but then it doesn't have to yet because the apps still function correctly with a copied v2.plist MS will fix the serialiser to remove/overwrite the v2.plist before the apps fail to work with a copied v2.plist don't concern yourself too much with this. It will be fixed when it needs to be. The process will remain the same as mentioned above. If you wish to be super proactive, run a preflight script to remove the v2.plist before the vl serialiser package installs.
Hi All,
Can anyone tell me why I should Install the VL_Serializer? I am running office 2016 now for a month with no problem (even got a few updates from the auto updater. )
Thanks
If you are using the volume installer from this calendar year there is no need to use it. It was intended to fix the earlier installer which did not license the product correctly.
@powellbc Many thanks for the reply :)
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.