Skip to main content

I've read through the (other post) about installing the VL version of Office 2016 multiple times, but I can't seem to come up with a working install.



I've tried installing the VL version downloaded from the Microsoft VL site which is 15.18 and I've tried the 15.19.1 installer and the serializer. Either way I get an installation in which none of the applications will launch. All give a similar error to the one copied below. I've seen one other person post this exact error, but didn't see a response to the issue.



The current test configuration is simple. It only includes OS X 10.11.4, scripts to set the time and join WiFi, and the Office installer and serializer. After being enrolled in Casper a policy runs that joins it to the domain and creates a local admin account. That's it.



If I use Casper Remote to push the exact same installer to the computer that ran during imaging the applications work. If I push updates to the computer for the 15.20 versions of all apps except Outlook (15.19.1 for it)...the apps work.



I would appreciate any help.



Process:               Microsoft Word [1674]

Path:                  /Applications/Microsoft Word.app/Contents/MacOS/Microsoft Word

Identifier:            com.microsoft.Word

Version:               ???

Code Type:             X86 (Native)

Parent Process:        ??? [1]

Responsible:           Microsoft Word [1674]

User ID:               501



Date/Time:             2016-03-30 10:34:51.167 -0500

OS Version:            Mac OS X 10.11.4 (15E65)

Report Version:        11

Anonymous UUID:        658BB8A2-D913-EDA0-EA0C-9442B131535B



Sleep/Wake UUID:       C1041521-4CA3-4F0F-8A73-975DB1D3A55E



Time Awake Since Boot: 1700 seconds

Time Since Wake:       450 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:

0x8feee000 - 0x8ff2267f  dyld (360.21) <872065EE-ED21-3B30-96A5-2CC56D735FB7> /usr/lib/dyld



Model: MacBookAir7,2, BootROM MBA71.0166.B08, 2 processors, Intel Core i5, 1.6 GHz, 4 GB, SMC 2.27f2

Graphics: Intel HD Graphics 6000, Intel HD Graphics 6000, Built-In

Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x483943434E4E4E384A544D4C41522D4E544D

Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x483943434E4E4E384A544D4C41522D4E544D

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (7.21.95.175.1a6)

Bluetooth: Version 4.4.4f4 17685, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

Serial ATA Device: APPLE SSD SM0256G, 251 GB

USB Device: USB 3.0 Bus

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

Thunderbolt Bus: MacBook Air, Apple Inc., 27.2

This article should help a bit:



https://macmule.com/2015/12/11/microsoft-office-2016-for-mac-serialisation-changes/



As for me, in our config, we have the MS packages install post-img. I have the Volume installer and a custom xml file (to remove auto update and OneNote) in a package and a post install script to run the installer (set to rank 2). Then the serializer package installs (set to rank 3). Hope this helps!

When you say you install "post-img" do you mean Office isn't included in your configuration used by Casper Imaging? Does it install via a Policy?

No, i just have both the serializer and the Volume installer as marked as Install on boot drive after imaging. Actually, for good measure i have all my packages outside of the OS marked that way. But thats a personal preference.

This worked. Thank you so much for the quick reply. I'm pretty new to Casper and had never used this option. Selecting it for the Office installer and Office Serializer allowed it to work as expected.

Selecting Install on boot drive after imaging for Office 2016 for Mac is one of the handful of times you'll need to do this for a third-party Apple installer package.



The only reason you need to do it here is for the licensing. The sub-package that handles the serialization relies on the boot drive's hardware information to create the license file. This may not necessarily be the target disk you're imaging. Enabling Install on boot drive after imaging ensures the licensing file is created on the target machine.

Reply


Terms & ConditionsCookie settings