Administering Office 2016 for Mac.key

Administering Office 2016 for Mac

Hello, I’m William Smith and a Solutions Architect for 318, Inc., a technology consultancy based in Santa Monica, Calif.

Let’s talk about Administering Office 2016 for Mac.

1 Administering Office 2016 for Mac.key - July 11, 2015

Product Support Lifecycle

Microsoft is releasing Office 2016 for Mac sometime later this year. We know this from back in March. Microsoft is discontinuing support for Office for Mac 2011 in January 2016. We’ve know this since 2010.

Every Microsoft product including Office for Mac has a Product Support Lifecycle. This is a pre-determined length of time Microsoft will provide mainstream support to everyone in the form of product updates, security patches and technical support.


Products Released

Lifecycle Start Date

Mainstream Support End Date

Extended Support End Date

Service Pack Support End Date

Microsoft Office for Mac 2011 Service Pack 1 4/15/11 Not Applicable Not Applicable 7/9/13


Microsoft Office for Mac 2011 Service Pack 3 1/29/13

Support ends 12 months after the next Service Pack releases or

at the end of the product's support lifecycle.



Microsoft Office for Mac Academic 2011 12/9/10 1/12/16 Not Applicable

Microsoft Office for Mac Home and Business 2011 12/9/10 1/12/16 Not Applicable

Microsoft Office for Mac Home and Student 2011 12/9/10 1/12/16 Not Applicable

Microsoft Office for Mac Standard 2011 12/9/10 1/12/16 Not Applicable

Microsoft Office for Mac 2011 https://support.microsoft.com/en-us/lifecycle?p1=15627

Here's a copy of the Office for Mac 2011 product support lifecycle and this is where you'll find that important end date. Historically, Microsoft releases about three major services packs throughout the life of an Office for Mac product. Service packs generally include bug fixes as well as new features. After that, the product goes into maintenance where it’ll receive periodic security updates, compatibility updates to keep up with OS X and some more bug fixes. You generally won't see new features after the last service pack. By that time the developers are already working on the next major version of the product.

3-1 Administering Office 2016 for Mac.key - July 11, 2015

Products Released

Lifecycle Start Date

Mainstream Support End Date

Extended Support End Date

Service Pack Support End Date



Microsoft Office for Mac 2011 Service Pack 3 1/29/13





Microsoft Office for Mac Academic 2011 12/9/10 1/12/16 Not Applicable

Microsoft Office for Mac Home and Business 2011 12/9/10 1/12/16 Not Applicable

Microsoft Office for Mac Home and Student 2011 12/9/10 1/12/16 Not Applicable

Microsoft Office for Mac Standard 2011 12/9/10 1/12/16 Not Applicable

Microsoft Office for Mac 2011 https://support.microsoft.com/en-us/lifecycle?p1=15627

Here's a copy of the Office for Mac 2011 product support lifecycle and this is where you'll find that important end date. Historically, Microsoft releases about three major services packs throughout the life of an Office for Mac product. Service packs generally include bug fixes as well as new features. After that, the product goes into maintenance where it’ll receive periodic security updates, compatibility updates to keep up with OS X and some more bug fixes. You generally won't see new features after the last service pack. By that time the developers are already working on the next major version of the product.


1984 20161986 1988 1990 1992 1994 1996 1998 2000 2002 2004 2006 2008 2010 2012 2014

MacintoshMultiplan

Word 1.0Excel 1.0

Word 3.0Excel Windows

Excel 1.5

Office for Mac • Excel 2.2 • PowerPoint 2.01 • Word 4.0 • Mail 1.37

Excel 3.0Office 1.5 for Mac

Office 3.0 for Mac • Excel 4.0 • PowerPoint 3.0 • Word 5.0 • Mail

Office 4.2 for Mac • Excel 5.0 • PowerPoint 4.0 • Word 6.0 • Mail 3.2

MacBUOffice 98 • Entourage

Microsoft rescues Apple • Five year commitment to develop

Office and IE for Mac

OS XOffice for Mac 2001

Office X • OS X • Exchange support

Office for Mac 2004

Intel Macs • Rosetta • MacBu reaffirms • 5-year commitment

Office for Mac 2008 • No VBA

Office for Mac 2011 • Outlook (Cocoa)

Office for Mac 2016 • Preview • Release

Office for Mac 2011 • Support ends

APEX

2018

A brief history of Office for Mac

The Product Support Lifecycle is a useful tool for predicting the future. Another useful tool is history. How did Office 2016 for Mac get here?

To understand the present, let's look at the past.


1984 1986 1988 1990 1992 1994 1996 1998 2000

MacintoshMultiplan

Word 1.0

Excel 1.0

Word 3.0Excel Windows

Excel 1.5

Office for Mac • Excel 2.2 • PowerPoint 2.01 • Word 4.0 • Mail 1.37

Excel 3.0

Office 1.5 for Mac



MacBU

Office 98 • Entourage



OS X

Office for Mac 2001

In the beginning... Steve Jobs created Macintosh and it was good. That was January 1984 and in April 1984 Microsoft released Multiplan. It was the very first third party application for Macintosh.

Multiplan was later renamed Excel and Excel made its debut on Macintosh. It didn't appear on Windows until two years later. Word also appeared on Macintosh in 1985.

In 1989, Microsoft released the first version of Office for Mac suite. *** 1989! *** It contained the major applications we know today—Excel, Word and PowerPoint. Two years later Microsoft revved Office to support System 7 and Multi-Finder. And into the mid 90s, they continued releasing new versions.


1994 1996 1998 2000 2002 2004 2006 2008 2010

Office 1.5 for Mac



MacBU

Office 98 • Entourage



OS X

Office for Mac 2001


Office for Mac 2004




The late 80s and early 90s, though, were dark for Apple. Jobs had been let go. Windows was dominating the market. Gil Amelio had licensed Mac OS to clone manufacturers. And while the Newton had coined the phrase 'PDA' in popular culture, it's development suffered and it failed to reinvent personal computing as promised. Apple purchased Steve Jobs' company NeXT and brought him back in late 1996 as 'interim' CEO or as he liked to call himself, the iCEO.

At Macworld Expo 1997, Jobs announced the Microsoft deal—a partnership where the company infused Apple with $150 million and made a five-year commitment to develop Office and Internet Explorer for Mac. Bill Gates made a live appearance on the big screen and received a lot of booooooos from the audience that day. But Jobs said some wise words: "We have to let go of this notion that for Apple to win, Microsoft has to lose."

That same year, Microsoft founded the Macintosh Business Unit (or MacBU), which would become the largest Mac software developer outside Cupertino. They also released Office 98 for Mac.


20162004 2006 2008 2010 2012 2014

Office for Mac 2001


Office for Mac 2004




Office for Mac 2016 • Preview • Release

Office for Mac 2011 • Support ends

APEX

2018

For a little while, MacBU had to support both the Classic and the Carbon operating systems simultaneously. That was Apple’s design.

Then half-way through Office’s next product development cycle, Apple announced another major architectural change—a hardware shift from PowerPC to Intel. You can hear everyone at MacBU yelling “Aaaaaaaaaah!, not again!” This forced them to reprioritize development and one of the casualties was the omission of VBA from Office for Mac 2008. It introduced, though, the first Apple Installer package for Office. Later in Office for Mac 2011, we saw the return of VBA, the first fully Cocoa app Outlook and lots of plists that we could manage.

Since then, Microsoft has started embracing additional platforms including iOS and Android and MacBU was reorganized and renamed the Apple Product Experience team or APEX. Their primary objective for Office 2016 for Mac was to get all the applications ported into Xcode—rewriting practically everything. Some of the code in the Office apps was by now 25 years old.


If you've looked at Office 2016 for Mac, your probably thinking it's just a facelift.

For the Mac administrator, there's a lot that's different.


Meh.

If you've looked at Office 2016 for Mac, your probably thinking it's just a facelift.

For the Mac administrator, there's a lot that's different.


Simpler.

We've got a lot to cover but the good news is administering Office 2016 is simpler than earlier versions. However, parts of it are very different.


☐ Remove Office 2011 ☐ Install Office 2016 ☐ Office Architecture ☐ Outlook Architecture ☐ Preferences ☐ Shared Files ☐ Scripting and Automation

We'll start by removing Office 2011 and then installing Office 2016.

Then we'll examine what's different about the architecture of both Office in general and Outlook specifically, since Outlook is the most complex to manage.

We'll look at preferences and management and where to place shared files on a Mac for all users. And finally, we'll cover changes in scriptability and automation.


Remove Office 2011

Office 2011 was the first of the recent version of Office that didn't come with an uninstaller. What we had before that were .app removal tools that required someone with administrator privileges to double-click. They weren't scriptable and they weren't silently executable. Frankly, the lack of an uninstaller wasn't much worse.

The only way to programmatically remove and undo Office 2011 is to use a script. You can run scripts using Apple Remote Desktop's Send UNIX command, payload-free Apple Installer packages, through Casper's Self Service or most any other Mac management tool available.


Remove Office 2011




Remove Office 2011




Remove Office 2011




Remove Office 2011

The script must quit any running processes, move fonts and delete several files. I don't recommend running it while a user is logged in to a Mac. Instead, run the script while the Mac is sitting at a login window or as part of a login or logout process when you know none of the files are in use.


Remove Office 2011

‣ Quit daemons ‣ Remove applications ‣ Remove Automator actions ‣ Delete and replace fonts ‣ Remove plug-ins and preferences ‣ Delete package receipts

The script must quit any running processes, move fonts and delete several files. I don't recommend running it while a user is logged in to a Mac. Instead, run the script while the Mac is sitting at a login window or as part of a login or logout process when you know none of the files are in use.


Remove Office 2011

#!/bin/shosascript -e 'tell application "Microsoft Database Daemon" to quit'osascript -e 'tell application "Microsoft AU Daemon" to quit'osascript -e 'tell application "Office365Service" to quit'rm -R '/Applications/Microsoft Communicator.app/'rm -R '/Applications/Microsoft Lync.app/'rm -R '/Applications/Microsoft Messenger.app/'rm -R '/Applications/Microsoft Office 2011/'rm -R '/Applications/Remote Desktop Connection.app/'rm -R '/Library/Application Support/Microsoft/'...

http://www.officeformachelp.com/office/install/remove-office/

I have two versions of a script to do all of this—a shell script and an AppleScript. You'll find them at the URL below. You can download a copy of these slides later from the PSU MacAdmin site.


✔ Remove Office 2011 ☐ Install Office 2016 ☐ Office Architecture ☐ Outlook Architecture ☐ Preferences ☐ Shared Files ☐ Scripting and Automation

Let's move to installing Office 2016.

Here's one way things just got simpler.


❌Remove Office 2011 ☐ Install Office 2016 ☐ Office Architecture ☐ Outlook Architecture ☐ Preferences ☐ Shared Files ☐ Scripting and Automation

You don't need to remove Office 2011.


Install Office 2016

Run Office 2016 and Office 2011 side by side.

Install Office 2016


You can run Office 2016 side-by-side with Office 2011. They share no common files and no common preferences.

What they do share are common Process Names. In Activity Monitor you'll see "Microsoft Excel" twice or "Microsoft Outlook" twice if you're running both versions of the application. Therefore, if you do any scripting or troubleshooting that calls applications by process name, be mindful that you call it by the full path to the application or build in a means to verify which application you're touching.

Otherwise, for pilot testing Office 2016 in your environment or for those users who insist the new version of Office doesn't have that critical feature they need to do their jobs, you can have applications from both versions installed and running at the same time.

Rainbows and unicorns for everyone!


Install Office 2016


Install Office 2016


You can run Office 2016 side-by-side with Office 2011. They share no common files and no common preferences.

What they do share are common Process Names. In Activity Monitor you'll see "Microsoft Excel" twice or "Microsoft Outlook" twice if you're running both versions of the application. Therefore, if you do any scripting or troubleshooting that calls applications by process name, be mindful that you call it by the full path to the application or build in a means to verify which application you're touching.

Otherwise, for pilot testing Office 2016 in your environment or for those users who insist the new version of Office doesn't have that critical feature they need to do their jobs, you can have applications from both versions installed and running at the same time.

Rainbows and unicorns for everyone!


Install Office 2016

Command line sudo /usr/sbin/installer \

-pkg /private/tmp/OfficePreview.pkg \-target /

Command line installation for Office 2016 works for the most part like it did for Office 2011. Please, use this method of installing Office rather than manually installing it and repackaging. Microsoft won't support repackaging and it's not a clean way of doing things.

For this to work, you must have the installer package copied to a Mac. In this case, I've copied the OfficePreview.pkg file to the /private/tmp directory. Why do I copy it to /private/tmp? This location stores temporary items and anything in here gets deleted automatically when the Mac restarts.

This is a simple command and something every Mac admin should get comfortable using because so many applications come as Apple Installer packages.1. The sudo command means "superuser do" or basically "run as root". You have to have administrator privileges to install Office.2. The command we're using is called "installer" and it lives in the hidden /usr/sbin" directory on your Mac. This is the equivalent of double-clicking a package

file and running Apple's GUI Installer application.3. Where you see these backslashes at the end of the lines, I'm just denoting that I'm breaking up this one-line command onto multiple lines for easier reading. If

you type this entire command as one line, you don't need these backslashes.4. I use "-pkg" to denote that what's coming after it is the path to my package. Again, I've copied the OfficePreview.pkg file into the hidden /private/tmp folder on

my Mac.5. Finally, I use "-target" to denote where I'm installing this package and the forward slash means "install here on this computer's boot drive."Hit the return key and in a minute or two you'll have Office installed. If you're running this command from your Mac to another Mac, you can do this without interrupting a user who's logged in or you can do it while no one is logged in.


Install Office 2016










Install Office 2016










Install Office 2016










Install Office 2016










Install Office 2016










Install Office 2016

Combo Updates 15.00 + 15.11.1 = 15.11.1

or15.10 + 15.11.1 = 15.11.1

Historically, updates to Office have been combo updates and we shouldn't really expect that to change. That means one updater package should update all or most earlier versions so that you're only ever having to run one installer and one or maybe two updates to deploy a fully up-to-date copy of Office.


Install Office 2016

Combo Updates sudo /usr/sbin/installer \

-pkg /private/tmp/Microsoft_Excel_15.11_Updater.pkg \-target /

And Office updates come in Apple Installer format too, so you can run them just as you'd run the Office installer.


Install Office 2016

-applyChoiceChangesXML

With the Apple installer command line tool and Office 2011, we had the option of adding "-applyChoiceChangesXML" to our install command line. This allowed us to point to a plain text file with a little bit of XML information for telling the installer "I want these items installed but not these other items."


Install Office 2016<?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>outlook</string> </dict></array></plist>

It looked something like this. This is a simplified view of a choice changes XML file you can generate and edit using the installer command line tool. Don't worry about trying to read this. Just note these three lines.

By including them in my XML, I’ll be modifying whether I install Outlook as you can see on the last line. By default, the integer in the first line would've been "1" to tell the installer "Go ahead and install Outlook". But if I change the "1" to a "0", I'd be telling the installer "Don't install Outlook".


Install Office 2016<?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>outlook</string> </dict></array></plist>

It looked something like this. This is a simplified view of a choice changes XML file you can generate and edit using the installer command line tool. Don't worry about trying to read this. Just note these three lines.

By including them in my XML, I’ll be modifying whether I install Outlook as you can see on the last line. By default, the integer in the first line would've been "1" to tell the installer "Go ahead and install Outlook". But if I change the "1" to a "0", I'd be telling the installer "Don't install Outlook".


Install Office 2016

This is the equivalent of double-clicking the Office 2011 installer, choosing the Customize option and de-selecting Outlook.


Install Office 2016


-pkg /private/tmp/OfficeInstaller.pkg \-target / \

-applyChoiceChangesXML /private/tmp/mychoices.plist

I'd have to deploy this file alongside my Office Installer and call it at the same time I ran the installer command. This is a great way to omit unwanted items such as fonts, proofing tools or Lync and it makes for a much cleaner install than deploying everything and deleting files after the fact.

However…


Install Office 2016

The Office 2016 Preview installer doesn't offer any choices. It's all or nothing.

The choices are still there if you use the command line installer to view them, but if Microsoft doesn't offer the option here in the GUI Installer then you probably shouldn't try to apply any choice changes using the command line installer. Maybe they'll make choices an option in the final release or offer some sort of alternative. We’ll see.


✔ Remove Office 2011 ✔ Install Office 2016 ☐ Office Architecture ☐ Outlook Architecture ☐ Preferences ☐ Shared Files ☐ Scripting and Automation

Most folks won't care that everything gets installed, but some might once they see Office 2016's new file architecture.


Office Architecture

Footprint

The most noticeable difference between Office 2011 and Office 2016 is their footprints—the amount of drive space Office uses. It's right there in the installer windows.


Office Architecture

6.39 GB1.69 GB

Office 2011 Office 2016

Office 2011 consumes a little more than 1.5 GB of drive space whereas Office 2016 consumes nearly 6.5 GB. Schools or other institutions that try to save money by purchasing those 128 GB MacBook Airs are going to see those drives fill up just a little faster.

What's happening?


Office Architecture

Office 2011 Office 2016Microsoft Office 2011

Additional Tools

Microsoft Document Connection.app

Microsoft Excel.app

Microsoft Outlook.app

Microsoft PowerPoint.app

Microsoft Word.app

Office

Microsoft Excel.app



Microsoft Word.app

Microsoft OneNote.app

On the left you'll see Office 2011 installs into a single folder in the Applications folder and everything related to Office is installed inside. Note that bottom folder in the Microsoft Office 2011 folder simply called “Office”. It contains a collection of shared frameworks and other shared resources that each application uses.

On the right you'll see Office 2016 installs just the Office applications into the Applications folder.

Everything that was in the old Office folder is now inside the application bundle here. And here. And here. And here. And here.

Can anyone guess how big that single "Office" folder is? About 1.1 GB.


Office Architecture


Additional Tools


Microsoft Excel.app



Microsoft Word.app

Office

Microsoft Excel.app



Microsoft Word.app







Office Architecture


Additional Tools


Microsoft Excel.app



Microsoft Word.app

Office

Microsoft Excel.app



Microsoft Word.app







Office Architecture


Additional Tools


Microsoft Excel.app



Microsoft Word.app

Office

Microsoft Excel.app



Microsoft Word.app







Office Architecture


Additional Tools


Microsoft Excel.app



Microsoft Word.app

Office

Microsoft Excel.app



Microsoft Word.app







Office Architecture


Additional Tools


Microsoft Excel.app



Microsoft Word.app

Office

Microsoft Excel.app



Microsoft Word.app







Office Architecture

Office 2011 Office 2016Library

Fonts

Microsoft Excel.app



Microsoft Word.app

Microsoft OneNote.appMicrosoft

Adding to this, the 350 MB font collection with 155 Microsoft fonts is also installed in each application bundle.

This has the advantage or disadvantage that only the Office apps will be able to access these fonts. (I come from a print and publishing background and personally think that’s fantastic for any company needing to manage their font libraries!)


Office Architecture

Office 2011 Office 2016Library

Internet Plug-Ins

Microsoft Excel.app



Microsoft Word.app

Microsoft OneNote.appSharePointBrowserPlugin.plugin

SharePointWebKitPlugin.webplugin

And SharePoint functionality that use to need browser plug-ins is also now built into the applications.

Everything that had been scattered throughout your Mac system is now in each self-contained application.


Office Architecture

WTF!?

I probably know what's going through your mind right now, but if you think about it, these changes give us a few advantages, which may outweigh these bloated application bundles.


Office Architecture

Save disk space?Move the apps to another drive.

Need to save disk space? Copy the applications to an external hard drive and run them from there.


Office Architecture

Remove Office 2016?Drag it to the Trash.

Need to uninstall Office? Just drag the applications to the Trash and empty it.


Office Architecture

Sandboxed

And self-contained applications can be sandboxed. The Office 2016 applications are sandboxed.

Can anyone think of other examples where applications are self-contained and sandboxed?

While Microsoft has made no announcements regarding the Mac App Store, they're perfectly poised to distribute individual applications this way. I'm sure they'll have to weigh the ease of distribution and a larger audience with having to give up 30% of their revenue, but if they ever decide to go this route, they're ready.

If you remember our history lesson from earlier, Microsoft has struggled to keep up with Apple's frequent changes. Here's an example where they're finally keeping up. We'll see later where sandboxing may pose some challenges, though.


Office Architecture

Localized

Here's another example of how administering Office 2016 will be simpler.

Microsoft has released prior versions of Office in about 15 languages. Let me make that a little clearer... They released 15 different installers of Office, one for each language.

Office 2016 is now one installer localized for 15 languages.


Office Architecture

To demonstrate this, I can open the Language & Region system preferences and change my preferred language from English to French. Doing so, changes my entire Finder interface, System Preferences, etc., from English to French.


Office Architecture

When I launch Word 2016, my ribbon and menus and all my dialogs now appear in French. Conversely, when I launch my U.S. English edition of Word 2011 with my language preferences set to French, I still see English menus and dialogs.

If you support multiple countries or multiple languages, you only need install one set of bits to get all the languages now.


Office Architecture

Package Receipts

One last thing I'd like to mention is package receipts, which are commonly used by software deployment systems like Casper and munki. Receipts contain information left by the Apple Installer about what's been installed.


Office Architecturepkgutil --pkgs=com.microsoft.*

I ran the pkgutil command on my laptop where I've had Office 2011 installed since late 2013. That's when I purchased my new laptop.

Can anyone guess how many receipts I had just for Office 2011?

Over two years, Microsoft had deposited nearly 1000 uniquely named package receipts on my computer. Because they were all uniquely named, they were pretty useless to my deployment server. It saw every receipt as a unique install.


Office Architecture

com.microsoft.lync.all.meetingjoinplugin.pkg.14.0.9com.microsoft.mau.all.autoupdate.pkg.2.3.2com.microsoft.mau.all.autoupdate.pkg.2.3.6com.microsoft.merp.all.errorreporting.pkg.2.2.6com.microsoft.merp.all.errorreporting.pkg.2.2.9com.microsoft.office.all.automator.pkg.14.3.6com.microsoft.office.all.automator.pkg.14.3.7.updatecom.microsoft.office.all.automator.pkg.14.3.8.updatecom.microsoft.office.all.automator.pkg.14.3.9.updatecom.microsoft.office.all.automator.pkg.14.4.1.updatecom.microsoft.office.all.automator.pkg.14.4.2.updatecom.microsoft.office.all.automator.pkg.14.4.3.updatecom.microsoft.office.all.core.pkg.14.3.6com.microsoft.office.all.core.pkg.14.3.7.updatecom.microsoft.office.all.core.pkg.14.3.8.updatecom.microsoft.office.all.core.pkg.14.3.9.updatecom.microsoft.office.all.core.pkg.14.4.1.updatecom.microsoft.office.all.core.pkg.14.4.2.updatecom.microsoft.office.all.core.pkg.14.4.3.updatecom.microsoft.office.all.core.pkg.14.4.4.updatecom.microsoft.office.all.core.pkg.14.4.5.updatecom.microsoft.office.all.core.pkg.14.4.7.updatecom.microsoft.office.all.core.pkg.14.4.8.updatecom.microsoft.office.all.core.pkg.14.4.9.updatecom.microsoft.office.all.core.pkg.14.5.0.updatecom.microsoft.office.all.core.pkg.14.5.1.updatecom.microsoft.office.all.core.pkg.14.5.2.updatecom.microsoft.office.all.fonts.pkg.14.3.6com.microsoft.office.all.fonts.pkg.14.3.7.updatecom.microsoft.office.all.fonts.pkg.14.3.8.updatecom.microsoft.office.all.fonts.pkg.14.3.9.updatecom.microsoft.office.all.fonts.pkg.14.4.1.updatecom.microsoft.office.all.fonts.pkg.14.4.2.updatecom.microsoft.office.all.fonts.pkg.14.4.3.updatecom.microsoft.office.all.fonts.pkg.14.4.4.updatecom.microsoft.office.all.fonts.pkg.14.4.5.updatecom.microsoft.office.all.fonts.pkg.14.4.7.updatecom.microsoft.office.all.fonts.pkg.14.4.8.updatecom.microsoft.office.all.fonts.pkg.14.4.9.updatecom.microsoft.office.all.fonts.pkg.14.5.0.updatecom.microsoft.office.all.fonts.pkg.14.5.1.update

com.microsoft.office.all.fonts.pkg.14.5.2.updatecom.microsoft.office.en.clipart.pkg.14.3.6com.microsoft.office.en.clipart.pkg.14.3.7.updatecom.microsoft.office.en.clipart.pkg.14.3.8.updatecom.microsoft.office.en.clipart.pkg.14.3.9.updatecom.microsoft.office.en.clipart.pkg.14.4.1.updatecom.microsoft.office.en.clipart.pkg.14.4.2.updatecom.microsoft.office.en.clipart.pkg.14.4.3.updatecom.microsoft.office.en.clipart.pkg.14.4.4.updatecom.microsoft.office.en.clipart.pkg.14.4.5.updatecom.microsoft.office.en.clipart.pkg.14.4.7.updatecom.microsoft.office.en.clipart.pkg.14.4.8.updatecom.microsoft.office.en.clipart.pkg.14.4.9.updatecom.microsoft.office.en.clipart.pkg.14.5.0.updatecom.microsoft.office.en.clipart.pkg.14.5.1.updatecom.microsoft.office.en.clipart.pkg.14.5.2.updatecom.microsoft.office.en.query.pkg.14.3.6com.microsoft.office.en.query.pkg.14.3.7.updatecom.microsoft.office.en.query.pkg.14.3.8.updatecom.microsoft.office.en.query.pkg.14.3.9.updatecom.microsoft.office.en.query.pkg.14.4.1.updatecom.microsoft.office.en.query.pkg.14.4.2.updatecom.microsoft.office.en.query.pkg.14.4.3.updatecom.microsoft.office.en.query.pkg.14.4.4.updatecom.microsoft.office.en.query.pkg.14.4.5.updatecom.microsoft.office.en.query.pkg.14.4.7.updatecom.microsoft.office.en.query.pkg.14.4.8.updatecom.microsoft.office.en.query.pkg.14.4.9.updatecom.microsoft.office.en.query.pkg.14.5.0.updatecom.microsoft.office.en.query.pkg.14.5.1.updatecom.microsoft.office.en.query.pkg.14.5.2.updatecom.microsoft.office.en.required.pkg.14.3.6com.microsoft.office.en.setupasst_resources.pkg.14.3.6com.microsoft.office.en.silverlight.pkg.14.3.6com.microsoft.office.en.solver.pkg.14.3.6com.microsoft.office.en.solver.pkg.14.3.7.updatecom.microsoft.office.en.solver.pkg.14.3.8.updatecom.microsoft.office.en.solver.pkg.14.3.9.updatecom.microsoft.office.en.solver.pkg.14.4.1.updatecom.microsoft.office.en.solver.pkg.14.4.2.updatecom.microsoft.office.en.solver.pkg.14.4.3.update

com.microsoft.office.en.solver.pkg.14.4.4.updatecom.microsoft.office.en.solver.pkg.14.4.5.updatecom.microsoft.office.en.solver.pkg.14.4.7.updatecom.microsoft.office.en.solver.pkg.14.4.8.updatecom.microsoft.office.en.solver.pkg.14.4.9.updatecom.microsoft.office.en.solver.pkg.14.5.0.updatecom.microsoft.office.en.solver.pkg.14.5.1.updatecom.microsoft.office.en.solver.pkg.14.5.2.updatecom.microsoft.office.en.sounds.pkg.14.3.6com.microsoft.office.en.vb_resources.pkg.14.3.6com.microsoft.office.en.word_resources.pkg.14.3.6com.microsoft.office.en.word_resources.pkg.14.3.7.updatecom.microsoft.office.en.word_resources.pkg.14.3.8.updatecom.microsoft.office.en.word_resources.pkg.14.3.9.updatecom.microsoft.office.en.word_resources.pkg.14.4.1.updatecom.microsoft.office.en.word_resources.pkg.14.4.2.updatecom.microsoft.office.en.word_resources.pkg.14.4.3.updatecom.microsoft.office.en.word_resources.pkg.14.4.4.updatecom.microsoft.office.en.word_resources.pkg.14.4.5.updatecom.microsoft.office.en.word_resources.pkg.14.4.7.updatecom.microsoft.office.en.word_resources.pkg.14.4.8.updatecom.microsoft.office.en.word_resources.pkg.14.4.9.updatecom.microsoft.office.en.word_resources.pkg.14.5.0.updatecom.microsoft.office.en.word_resources.pkg.14.5.1.updatecom.microsoft.office.en.word_resources.pkg.14.5.2.updatecom.microsoft.office.en.word_templates.pkg.14.3.6com.microsoft.office.en.word_wizards.pkg.14.3.6com.microsoft.office.en.word_wizards.pkg.14.3.7.updatecom.microsoft.office.en.word_wizards.pkg.14.3.8.updatecom.microsoft.office.en.word_wizards.pkg.14.3.9.updatecom.microsoft.office.en.word_wizards.pkg.14.4.1.updatecom.microsoft.office.en.word_wizards.pkg.14.4.2.updatecom.microsoft.office.en.word_wizards.pkg.14.4.3.updatecom.microsoft.office.en.word_wizards.pkg.14.4.4.updatecom.microsoft.office.en.word_wizards.pkg.14.4.5.updatecom.microsoft.office.en.word_wizards.pkg.14.4.7.updatecom.microsoft.office.en.word_wizards.pkg.14.4.8.updatecom.microsoft.office.en.word_wizards.pkg.14.4.9.updatecom.microsoft.office.en.word_wizards.pkg.14.5.0.updatecom.microsoft.office.en.word_wizards.pkg.14.5.1.updatecom.microsoft.office.en.word_wizards.pkg.14.5.2.update

pkgutil --pkgs=com.microsoft.*





Office Architecture

com.microsoft.lync.all.meetingjoinplugin.pkg.14.0.9com.microsoft.mau.all.autoupdate.pkg.2.3.2com.microsoft.mau.all.autoupdate.pkg.2.3.6com.microsoft.merp.all.errorreporting.pkg.2.2.6com.microsoft.merp.all.errorreporting.pkg.2.2.9com.microsoft.office.all.automator.pkg.14.3.6com.microsoft.office.all.automator.pkg.14.3.7.updatecom.microsoft.office.all.automator.pkg.14.3.8.updatecom.microsoft.office.all.automator.pkg.14.3.9.updatecom.microsoft.office.all.automator.pkg.14.4.1.updatecom.microsoft.office.all.automator.pkg.14.4.2.updatecom.microsoft.office.all.automator.pkg.14.4.3.updatecom.microsoft.office.all.core.pkg.14.3.6com.microsoft.office.all.core.pkg.14.3.7.updatecom.microsoft.office.all.core.pkg.14.3.8.updatecom.microsoft.office.all.core.pkg.14.3.9.updatecom.microsoft.office.all.core.pkg.14.4.1.updatecom.microsoft.office.all.core.pkg.14.4.2.updatecom.microsoft.office.all.core.pkg.14.4.3.updatecom.microsoft.office.all.core.pkg.14.4.4.updatecom.microsoft.office.all.core.pkg.14.4.5.updatecom.microsoft.office.all.core.pkg.14.4.7.updatecom.microsoft.office.all.core.pkg.14.4.8.updatecom.microsoft.office.all.core.pkg.14.4.9.updatecom.microsoft.office.all.core.pkg.14.5.0.updatecom.microsoft.office.all.core.pkg.14.5.1.updatecom.microsoft.office.all.core.pkg.14.5.2.updatecom.microsoft.office.all.fonts.pkg.14.3.6com.microsoft.office.all.fonts.pkg.14.3.7.updatecom.microsoft.office.all.fonts.pkg.14.3.8.updatecom.microsoft.office.all.fonts.pkg.14.3.9.updatecom.microsoft.office.all.fonts.pkg.14.4.1.updatecom.microsoft.office.all.fonts.pkg.14.4.2.updatecom.microsoft.office.all.fonts.pkg.14.4.3.updatecom.microsoft.office.all.fonts.pkg.14.4.4.updatecom.microsoft.office.all.fonts.pkg.14.4.5.updatecom.microsoft.office.all.fonts.pkg.14.4.7.updatecom.microsoft.office.all.fonts.pkg.14.4.8.updatecom.microsoft.office.all.fonts.pkg.14.4.9.updatecom.microsoft.office.all.fonts.pkg.14.5.0.updatecom.microsoft.office.all.fonts.pkg.14.5.1.update

com.microsoft.office.all.fonts.pkg.14.5.2.updatecom.microsoft.office.en.clipart.pkg.14.3.6com.microsoft.office.en.clipart.pkg.14.3.7.updatecom.microsoft.office.en.clipart.pkg.14.3.8.updatecom.microsoft.office.en.clipart.pkg.14.3.9.updatecom.microsoft.office.en.clipart.pkg.14.4.1.updatecom.microsoft.office.en.clipart.pkg.14.4.2.updatecom.microsoft.office.en.clipart.pkg.14.4.3.updatecom.microsoft.office.en.clipart.pkg.14.4.4.updatecom.microsoft.office.en.clipart.pkg.14.4.5.updatecom.microsoft.office.en.clipart.pkg.14.4.7.updatecom.microsoft.office.en.clipart.pkg.14.4.8.updatecom.microsoft.office.en.clipart.pkg.14.4.9.updatecom.microsoft.office.en.clipart.pkg.14.5.0.updatecom.microsoft.office.en.clipart.pkg.14.5.1.updatecom.microsoft.office.en.clipart.pkg.14.5.2.updatecom.microsoft.office.en.query.pkg.14.3.6com.microsoft.office.en.query.pkg.14.3.7.updatecom.microsoft.office.en.query.pkg.14.3.8.updatecom.microsoft.office.en.query.pkg.14.3.9.updatecom.microsoft.office.en.query.pkg.14.4.1.updatecom.microsoft.office.en.query.pkg.14.4.2.updatecom.microsoft.office.en.query.pkg.14.4.3.updatecom.microsoft.office.en.query.pkg.14.4.4.updatecom.microsoft.office.en.query.pkg.14.4.5.updatecom.microsoft.office.en.query.pkg.14.4.7.updatecom.microsoft.office.en.query.pkg.14.4.8.updatecom.microsoft.office.en.query.pkg.14.4.9.updatecom.microsoft.office.en.query.pkg.14.5.0.updatecom.microsoft.office.en.query.pkg.14.5.1.updatecom.microsoft.office.en.query.pkg.14.5.2.updatecom.microsoft.office.en.required.pkg.14.3.6com.microsoft.office.en.setupasst_resources.pkg.14.3.6com.microsoft.office.en.silverlight.pkg.14.3.6com.microsoft.office.en.solver.pkg.14.3.6com.microsoft.office.en.solver.pkg.14.3.7.updatecom.microsoft.office.en.solver.pkg.14.3.8.updatecom.microsoft.office.en.solver.pkg.14.3.9.updatecom.microsoft.office.en.solver.pkg.14.4.1.updatecom.microsoft.office.en.solver.pkg.14.4.2.updatecom.microsoft.office.en.solver.pkg.14.4.3.update

com.microsoft.office.en.solver.pkg.14.4.4.updatecom.microsoft.office.en.solver.pkg.14.4.5.updatecom.microsoft.office.en.solver.pkg.14.4.7.updatecom.microsoft.office.en.solver.pkg.14.4.8.updatecom.microsoft.office.en.solver.pkg.14.4.9.updatecom.microsoft.office.en.solver.pkg.14.5.0.updatecom.microsoft.office.en.solver.pkg.14.5.1.updatecom.microsoft.office.en.solver.pkg.14.5.2.updatecom.microsoft.office.en.sounds.pkg.14.3.6com.microsoft.office.en.vb_resources.pkg.14.3.6com.microsoft.office.en.word_resources.pkg.14.3.6com.microsoft.office.en.word_resources.pkg.14.3.7.updatecom.microsoft.office.en.word_resources.pkg.14.3.8.updatecom.microsoft.office.en.word_resources.pkg.14.3.9.updatecom.microsoft.office.en.word_resources.pkg.14.4.1.updatecom.microsoft.office.en.word_resources.pkg.14.4.2.updatecom.microsoft.office.en.word_resources.pkg.14.4.3.updatecom.microsoft.office.en.word_resources.pkg.14.4.4.updatecom.microsoft.office.en.word_resources.pkg.14.4.5.updatecom.microsoft.office.en.word_resources.pkg.14.4.7.updatecom.microsoft.office.en.word_resources.pkg.14.4.8.updatecom.microsoft.office.en.word_resources.pkg.14.4.9.updatecom.microsoft.office.en.word_resources.pkg.14.5.0.updatecom.microsoft.office.en.word_resources.pkg.14.5.1.updatecom.microsoft.office.en.word_resources.pkg.14.5.2.updatecom.microsoft.office.en.word_templates.pkg.14.3.6com.microsoft.office.en.word_wizards.pkg.14.3.6com.microsoft.office.en.word_wizards.pkg.14.3.7.updatecom.microsoft.office.en.word_wizards.pkg.14.3.8.updatecom.microsoft.office.en.word_wizards.pkg.14.3.9.updatecom.microsoft.office.en.word_wizards.pkg.14.4.1.updatecom.microsoft.office.en.word_wizards.pkg.14.4.2.updatecom.microsoft.office.en.word_wizards.pkg.14.4.3.updatecom.microsoft.office.en.word_wizards.pkg.14.4.4.updatecom.microsoft.office.en.word_wizards.pkg.14.4.5.updatecom.microsoft.office.en.word_wizards.pkg.14.4.7.updatecom.microsoft.office.en.word_wizards.pkg.14.4.8.updatecom.microsoft.office.en.word_wizards.pkg.14.4.9.updatecom.microsoft.office.en.word_wizards.pkg.14.5.0.updatecom.microsoft.office.en.word_wizards.pkg.14.5.1.updatecom.microsoft.office.en.word_wizards.pkg.14.5.2.update


820+ Receipts





Office Architecture

com.microsoft.package.Fontscom.microsoft.package.Frameworkscom.microsoft.package.Microsoft_AutoUpdate.appcom.microsoft.package.Microsoft_Excel.appcom.microsoft.package.Microsoft_OneNote.appcom.microsoft.package.Microsoft_Outlook.appcom.microsoft.package.Microsoft_PowerPoint.appcom.microsoft.package.Microsoft_Word.appcom.microsoft.package.Proofing_Toolscom.microsoft.pkg.licensing


If I run that same command on a computer that's only ever had Office 2016 installed, I see a total of 10 package receipts even after applying several product updates. This list should give you a very good idea about what's in the installer file.


Office Architecture

package-id:com.microsoft.package.Microsoft_Outlook.app

version: 15.11volume: /location: Applicationsinstall-time: 1435964376

date -r 1435964376Fri Jul 3 17:59:36 CDT 2015

pkgutil --pkg-info com.microsoft.package.Microsoft_Outlook.app

I can run the "--pkg-info" option on any of the receipts and get the current version number of an application along with the install time in UNIX epoch time. And if I need, I can use the date command to translate epoch time to something more readable.


✔ Remove Office 2011 ✔ Install Office 2016 ✔ Office Architecture ☐ Outlook Architecture ☐ Preferences ☐ Shared Files ☐ Scripting and Automation

Let's spend just a little bit of time talking about Outlook.

If you've installed the Office Preview and poked around Outlook, you've probably been pretty UNimpressed. When the Preview first shipped in March, the most noticeable new feature was the weather in Calendar view.


Meh.

Since March, Microsoft has released some updates to give us a few more features such as side-by-side calendars and propose new meeting time but for the most part it looks pretty much like Outlook 2011 with a facelift.

But there are a few things you should know.


Outlook Architecture

Outlook 2011: ~/Documents/Microsoft User Data

Outlook 2016: ~/Library/Group Containers/UBF8T346G9.Office/Outlook

Outlook is now sandboxed and therefore its preferences and files are now stored in a sandboxed location.

Outlook 2011 kept its mail in the Microsoft User Data folder in a user's Documents folder. Outlook 2016 now keeps that data in a location registered by Apple to Microsoft. Notice that it's no longer in the Documents folder but rather in the use's hidden Library folder. No longer should a user accidentally delete his mail data. He'd have to consciously navigate to this hidden folder and dig deep inside to find his mail and delete it.


Database


Microsoft Entourage, Outlook's predecessor, introduced the monolithic database. How we hated the monolithic database because it was a pain manage, unwieldy to back up and prone to corruption.

Does anyone miss those days?

Outlook 2011 took us away from that by splitting out the data from the database. This was much easier to manage and back up. It was still prone to corruption every once in a while but we had the Database Utility to handle that.


Database


That's all changed with Outlook 2016.

It no longer stores mail data in a proprietary Microsoft database. It now uses SQLite, whose code is in the public domain and already installed on your Mac. SQLite enables any software developer to store and access local database files without a server. Apple uses SQLite to store several of its application databases.

Microsoft excluded the Outlook 2011 database from Time Machine because it was too big to copy without it changing in the middle of a backup. The SQLite database files are now much smaller and Outlook is now Time Machine friendly. That means you shouldn't have to worry about a database rebuild after restoring from a backup.

If your database does get corrupted, Outlook will handle the repair. It won't ask you. It'll just do it. And there is no more Database Utility for you to run. I've been using Outlook 2016 since its early betas and have yet to see a repair or rebuild.


Database


‣ SQLite ‣ Time Machine friendly ‣ No more Database Utility ‣ Profile Manager is embedded in

Outlook's application bundle ‣ No more Database Daemon

That's all changed with Outlook 2016.

It no longer stores mail data in a proprietary Microsoft database. It now uses SQLite, whose code is in the public domain and already installed on your Mac. SQLite enables any software developer to store and access local database files without a server. Apple uses SQLite to store several of its application databases.

Microsoft excluded the Outlook 2011 database from Time Machine because it was too big to copy without it changing in the middle of a backup. The SQLite database files are now much smaller and Outlook is now Time Machine friendly. That means you shouldn't have to worry about a database rebuild after restoring from a backup.

If your database does get corrupted, Outlook will handle the repair. It won't ask you. It'll just do it. And there is no more Database Utility for you to run. I've been using Outlook 2016 since its early betas and have yet to see a repair or rebuild.


Mail Setup


I'll talk quickly about automatically configuring email for your users.


Mail Setup


Exchange: Autodiscover or Outlook Exchange Setup script

POP and IMAP: /Applications/Microsoft Outlook.app/Contents/Resources/autoConfigDB.xml

First, I'd hoped to demo a new version of my Outlook Exchange Setup script today. After Microsoft made some changes to Outlook 2016, the automatic setup broke. However, I'm fairly confident I can get it working again and actually be a little more efficient at setup. I strongly encourage you to get Autodiscover working in your environment if you can so you don't have to use this script.

As for POP and IMAP setup, modifying the autoConfigDB.xml file inside the Outlook application bundle still works. You can add your organization's POP or IMAP email settings to this file so that users simply need to enter their email address and password to connect to their mail. Outlook will handle completing the server addresses, ports, etc. This isn't ideal since it means modifying a resource that may get updated by Microsoft in the future, but it still works.


Exchange Online Archive


I won't get into detail about this but I will point out that Outlook 2016 now supports Exchange Online Archive both with Office 365 and Exchange Server 2013. If you're not familiar with this feature, look into it.

Exchange Online Archive requires your Exchange administrator to enable and configure archiving per user. He'll set defaults such as "archive all mail older than two years". That mail gets moved into another mailbox, which automatically appears in Outlook. However, that mail doesn't sync. It's searchable while Outlook is online and connected to Exchange and the user can download archived mail, but once Outlook quits that cache is deleted. This is a fantastic method of keeping user mailboxes to manageable sizes.


http://outlook.uservoice.com/forums/293343-outlook-for-mac


My last word about Outlook is that we all want parity with Outlook for Windows. Who knows if we'll ever see that. The APEX group, however, is publicly asking customers to post their feature requests and vote on them to prioritize their schedule.

I encourage you to visit Uservoice.com, review feature requests, vote on them and submit your own if you don't see a feature you want.


✔ Remove Office 2011 ✔ Install Office 2016 ✔ Office Architecture ✔ Outlook Architecture ☐ Preferences ☐ Shared Files ☐ Scripting and Automation

And now, it's time to kill some unicorns.

I stood here last year extolling the virtues of Office 2011 and how manageable it was when using Configuration Profiles. I demonstrated how we could eliminate automatic updates and all those startup and welcome screens the first time a user launches an application. All of that relied on plists. Apple's Profile Manager and Casper and practically any management server uses plists.


✔ Remove Office 2011 ✔ Install Office 2016 ✔ Office Architecture ✔ Outlook Architecture ☐ Preferences ☐ Shared Files ☐ Scripting and Automation

And now, it's time to kill some unicorns.

I stood here last year extolling the virtues of Office 2011 and how manageable it was when using Configuration Profiles. I demonstrated how we could eliminate automatic updates and all those startup and welcome screens the first time a user launches an application. All of that relied on plists. Apple's Profile Manager and Casper and practically any management server uses plists.


Preferences

/Library/Group Containers/UBF8T346G9.Office/

MicrosoftRegistrationDB.reg

From what I've found, practically every user configurable preference for Excel, OneNote, PowerPoint and Word, is now stored in a SQLite database file called MicrosoftRegistrationDB.reg.

Given that OS X's management system is based on plists, MCX and Configuration Profiles, that means for the most part Office 2016 is unmanageable. Even if we could cobble together some SQLite commands to change settings in this file or simply copy a preconfigured file to every user folder, we can't override users from changing their settings while using the applications. All we'd be doing is resetting defaults.

I've written a sternly worded email to Microsoft about this. I'm afraid, though, it may be too late to change their design.


Preferences

Manage Third Party Applications with Profiles http://macadmins.psu.edu/conference/resources/

The lack of management applies only to the Office applications. We do at least still have the ability to manage Microsoft AutoUpdate using a Configuration Profile to prevent it from asking users to update their software.

For that, I'll point you to my presentation from last year.


✔ Remove Office 2011 ✔ Install Office 2016 ✔ Office Architecture ✔ Outlook Architecture ✔ Preferences ☐ Shared Files ☐ Scripting and Automation

Just a quick note about shared files or resource files such as company letterheads in Word or branded slide decks for PowerPoint.


Shared Files

Word menu > Preferences > File Locations

Launch Word 2016 and choose Word > Preferences > File Locations. Your user has the ability to specify certain file locations such clipart pictures and Workgroup templates. You can place your organization's letterhead, FAX cover letter, PowerPoint template or custom Excel sheets in these locations so they appear in your users's templates menus.

Word is the only application where you can set these preferences right now.


Shared Files~/Library/Group Containers/UBF8T346G9.Office/

User Content

Chart Templates.localized

Document Elements.localized

SmartArt Graphics.localized

Startup.localized

Style Sets.localized

Templates.localized

Themes.localized

Users

Shared

Shared Files

To create this location, navigate to the Office Group Container folder and locate User Content. Copy the User Content folder to a common location such as /Users/Shared and rename it to something like Shared Files. Then give everyone read/write permissions or just the person responsible for managing your template files.

Note the sub-folders have a hidden .localized file extension. You want to preserve that, which is why you're copying the entire folder.


Shared FilesTemplates.localized

Excel

PowerPoint

Word

Some of these folders, such as Templates, need you to create sub-folders for each application.


Shared FilesTemplates.localized

Excel

PowerPoint

Word

Company Letterhead.dotx

Weekly Summary.xltx

Company Presentation.potx

Save your company template files in each application folder.


Shared Files

And then when your users launch their applications, they'll see the templates window. Your company templates appear here.


Shared Files

And then when your users launch their applications, they'll see the templates window. Your company templates appear here.


Shared Files

MicrosoftRegistrationDB.reg

I'd suggest you set up this location for your users but the preferences aren't really that easy to manage. You could probably package the MicrosoftRegistrationDB.reg file along with the Shared Files folder and push that to machines to install at first run if you need to set up multiple Macs.


✔ Remove Office 2011 ✔ Install Office 2016 ✔ Office Architecture ✔ Outlook Architecture ✔ Preferences ✔ Shared Files ☐ Scripting and Automation

Lastly, let's talk a little about scripting and automation. In particular, I'm referring to AppleScripts and add-ins.


Scripting and Automation

Remember, Office applications are now self-contained and sandboxed.

Microsoft is no longer providing Automator actions for Office.



Remember, Office applications are now self-contained and sandboxed.

Microsoft is no longer providing Automator actions for Office.



The AppleScript menu in each application is gone too now.



The AppleScript menu in each application is gone too now.



That doesn't mean the applications aren't still scriptable! They are! In fact, you can still open the Script Editor application and enable the system-wide AppleScript menu. If you create folders for each Office application and place your scripts there, you'll see only your scripts that work with that application.






~/Library/Scripts/Applications/Microsoft Outlook




~/Library/Scripts/Applications/Microsoft Outlook



Office Architecture

Sandboxing

But you may have to do a little rewriting depending on what processes you're calling. Sandboxing is going to affect how your AppleScripts interact with multiple applications. Depending on what you're trying to do, running a script from within one application may or may not let you transfer data or control another sandboxed application.

Functionality isn't broken. You just have to play by stricter rules. Before deploying Office 2016 to production, test any and all AppleScripts.


✔ Remove Office 2011 ✔ Install Office 2016 ✔ Office Architecture ✔ Outlook Architecture ✔ Preferences ✔ Shared Files ✔ Scripting and Automation

History shows Office has been around as early as the Macintosh but Apple's thrown Microsoft a few curve balls by re-architecting not only its operating system but also its hardware in a very short time. Microsoft is catching up with Office 2016 by completely rewriting it in Xcode.

While we may not see many new features in the applications themselves, the rework done under the hood in both Office and applications like Outlook is substantial. That rework, through, requires some trade-offs such as lack of reminders while Outlook is quit and even lack of manageability. Most of the functionality our users need is still there but Mac admins have to go about how they support Office a little differently going forward.


Q & A


William Smith 318, Inc. Santa Monica, CA

[email protected] http://talkingmoose.net @meck

Administering Office for Mac 2016 Feedback: http://j.mp/psumac2015-90
