- Office 365 Deployment Tool For Mac Google Drive
- Office 365 Deployment Tool For Mac Google Search
- Office 365 Deployment Guide
Microsoft's Office suite is the de facto standard in productivity for departments in organizations worldwide. Office has found its way onto more computers than Microsoft could have ever predicted. Add to that tablets and smartphones, and licensing costs quickly get out of hand, especially when Google Apps offers much of the same functionality at a fraction of the cost. So what is Microsoft to do? Office 365 is the answer.
A: The following topics were updated: restricting self-provisioning of Office 365 ProPlus, managing streaming updates, and customizing deployment using the Office Deployment Tool. In addition, new videos were added that cover configuring Visio Online and creating a pilot group for testing Office 365 ProPlus updates. Deployment Option 1 - Users sign in to Read&Write with Google or Office 365 Last Modified on 3:50 pm GMT Please note:- If your organization does not use G Suite or Office 365, the Multi-User Setup Tool should be used to setup Read&Write for users that don't sign in. However for your concerns, from the article, we can learn that to deploy Office 2016 via Office 2016 deployment tool and GPOs, we need to uninstall the C2R version of the Office 2013, because the two products are incompatible.
More about Networking
As a systems administrator, there's a solid chance your organization will be upgrading to 365 sooner rather than later, and you're going to want to know how to deploy this since it's not like previous versions of Office.
Let's proceed with the deployment process, which is broken up into three phases to facilitate the procurement of the deployment tool, the configuration of the Office installation files, and the deployment.
SEE:Microsoft Office 365: The smart person's guide
Requirements
- Microsoft Office 365 admin portal setup*
- Microsoft Office 365 license(s) assigned to end users*
- Server share with read permissions to deployment root
- Administrative computer running Microsoft Windows 7 or later
- Office 2016 Deployment Tool or Office 2013 Deployment Tool
* Note: While not required to create the Office 365 deployment share, once the application is deployed, it will require end users to log on in order to access Office applications. Without the admin portal set up or licenses assigned, users will not be able to use Office.
SEE:Four secrets of a successful Office 365 deployment (Tech Pro Research)
Internet access
I. Installing the Office Deployment Tool
1. On the admin station, double-click the EXE download to manage the version of Office you'll be deploying to your organization. Check the box to agree to the licensing terms and click Continue (Figure A).
Figure A
2. Create a new directory or select an existing one for which to extract the contents of the file to, and then click OK (Figure B).
Figure B
3. Upon successfully extracting the files, a confirmation message will appear. The first process has been completed successfully (Figure C).
Figure C
II. Configuring Office for deployment
While it may seem unorthodox to configure an application before it has been installed, rest assured the configuration process (handled by the configuration.xml file extracted in phase I) handles double-duty, as it not only preps the install files that will be downloaded from Microsoft's Office Content Delivery Network (CDN), but it also acts as the guide during the install process in phase III.
1. After extracting the files in phase I, there will be two files in the root directory: Setup.exe and Configuration.xml. Right-click the Configuration.xml file and open it with Notepad to edit it.
2. By default, the XML file comes with a sample deployment structure to get admins started. Between the <configuration></configuration> brackets is the meat and potatoes of the configuration; it is this data that will be used to download the latest Office files from the Microsoft CDN, and control how the installation will occur once deployed over the network (Figure D).
Figure D
3. Some of the more prominent attributes to include are as follows.
- OfficeClientEdition='32' or '64'
This controls whether Office will be a 32-bit or 64-bit installation. - SourcePath='servershare'
This setting indicates the location of the installation files. - Product
This setting will add individual applications to the installation source. - ExcludeApp
This setting will remove individual applications from the installation source and prevent them from being installed during deployment. - Display Level='None'
This setting is carried over from previous Office installations to hide all dialog windows during installation. - AcceptEULA='TRUE'
Another returning setting auto-accepts the EULA for a silent installation.
Microsoft's Office 365 reference guide for Click-to-Run installations offers a great deal of information on what settings may be configured for a truly customizable deployment process.
4. Once the XML file has been configured to best suit your target environment, launch the command line prompt and change directories to the directory where the files were extracted in phase I. Calling the setup.exe file with the /help switch will bring up the available arguments and their respective functions for future reference (Figure E).
Figure E
5. For now, enter the command as follows, referencing the configuration.xml file in order to execute the deployment tool, allowing it to connect to the CDN and download the most updated versions of Office 365's installation files (Figure F).
serversharesetup.exe /download /configuration.xml
Figure F
This process will take some time depending on your internet speed. Once it's complete, the installation source will be set up and ready to deploy Office 365 (Figure G).
Figure G
III. Deploying Office 365
1. With the latest Office installation files downloaded to the root of the directory, you are ready to deploy Office 365 across the LAN/WAN. The command to launch the deployment and install the Office suite is as follows (Figure H).
serversharesetup.exe /configure configuration.xml
Figure H
Office 365 Deployment Tool For Mac Google Drive
2. When launching from the Windows Explorer environment, it is normal for the Office splash screen to display briefly; it will not appear during deployments via Group Policy, scripted as a batch file, or SCCM or a third-party solution (Figure I).
Figure I
3. Depending on the speed of the LAN/WAN, installation may take several minutes to complete per device. For laptops or computers that are connected over narrowband or have intermittent connectivity, the install source may be copied to local or external storage to be deployed at a later time (Figure J).
Figure J
4. Once the installation is complete, a message will display indicating Office is ready for use; this will only occur while logged onto a machine — silent deployments will not display any dialog screen when the display level is set to None (Figure K).
Figure K
With Office 365 installed, end users will be required to enter their username and password upon launching any Office suite application for the first time. Once the license is verified, the suite will activate automatically. By default, Microsoft requires that Office 365 installations 'check in' online every 30 days to verify activation.
If you choose to deploy Office in a virtualized container as a Remote Desktop Service by utilizing Microsoft's App-V application streaming solution, the /packager mode switch performs a similar function to the /configure argument, except that the contents of the installation source are packaged in a format that works with App-V.
Lastly, applying security updates for Office 365 are handled through Windows Update via the internet, or managed locally via Group Policy or SCCM.
Have you deployed Office 365?
If you deployed Office 365 in your organization, how was the experience? Any horror stories, pain points, or helpful tips? Let us know.
Also see
- Get an early look at the new Office 365 admin center (TechRepublic)
- Yammer is on the way to Office 365: Are you ready? (TechRepublic)
- 10+ things you should know before buying Office 365 (TechRepublic)
- Control collaboration chaos with admin tools for Office 365 Groups (TechRepublic)
- Microsoft updates Office 365 with six new Excel functions (TechRepublic)
- Microsoft starts rolling out Office 365 Connectors as part of Groups (ZDNet)
Applies to:Office for Mac, Office 2019 for Mac, Office 2016 for Mac
There are two basic ways that you, as an admin, can deploy Office for Mac to users in your organization:
Provide your users with the installer package file, and have them install Office for Mac for themselves
Download the installer package file to your local network, and then use your software distribution tools to deploy Office for Mac to your users
If you have an Office 365 plan, you can provide your users with instructions on how to download and install Office for Mac for themselves. To install Office for Mac, a user has to be administrator on the Mac or know an administrator account name and password.
But, if you deploy Office for Mac for your users, you have more control over the deployment, including which users get Office for Mac and when. To plan your deployment, review the following information.
Download Office for Mac to your local network
The easiest way to download Office for Mac, and ensure you're always getting the most current version and build, is to download directly from the Office Content Delivery Network (CDN) on the internet. Here are the links to the installer packages for the Office suite, which contains all the applications:
Office 365 Deployment Tool For Mac Google Search
- Office for Mac (for Office 365 plans)
- Office 2019 for Mac (for retail or volume licensed versions)
- Office 2016 for Mac (for retail or volume licensed versions)
Note
- Installer and update packages for individual applications are also available on the Office CDN. For links to those, see Most current packages for Office for Mac.
- The same installer package is used for Office for Mac and Office 2019 for Mac. How you activate the product determines whether you get the features for Office for Mac or the features for Office 2019 for Mac.
- Unlike Office 2016 for Mac, the installer package for Office 2019 for Mac isn't available on the Volume Licensing Service Center (VLSC).
Deploy Office for Mac to users in your organization
Office 365 Deployment Guide
Office for Mac uses the Apple Installer technology for installation. That means you can use the software distribution tools that you normally use to deploy software to Mac users. Some of the most common tools are Jamf Pro, Munki, and AutoPkg. You can also use Apple Remote Desktop and AppleScript.
Important
There are changes in Office for Mac to improve security, including implementing Apple app sandboxing guidelines. These changes mean that you can't customize the app bundle before or after you deploy Office. Don't add, change, or remove files in an app bundle. For example, even if you don't need the French language resource files for Excel, don't delete them. This change prevents Excel from starting. Even though you can't customize app bundles, you can configure preferences for each app.
Additional deployment information for Office for Mac
Whichever deployment method you decide to use, the following information can help you plan your Office for Mac deployment.
What's new: Before you deploy, review the information about what's new for admins in Office for Mac. This includes information about system requirements, language support, and new features.
Side-by-side installation: You can't have Office 2016 for Mac and Office 2019 for Mac installed on the same computer. Also, you can't have Office for Mac (from an Office 365 plan) along with either Office 2016 for Mac or Office 2019 for Mac (both of which are one-time purchase versions) installed on the same computer.
Deploying individual apps: Installer package files for individual applications are available on the Office Content Delivery Network (CDN). For links to those, see Most current packages for Office for Mac.
Activation: To use Office for Mac, it needs to be activated. Before you deploy, review the information about how activation works in Office for Mac.
Uninstalling: If you need to uninstall Office for Mac, you can follow these steps to completely remove Office for Mac. Unfortunately, there is no program to uninstall Office for Mac automatically.
Office for Mac 2011: Support for Office for Mac 2011 ended on October 10, 2017. All of your Office for Mac 2011 apps will continue to function. But, you could expose yourself to serious and potentially harmful security risks. To completely remove Office for Mac 2011, follow these steps.
Upgrading to Office 2019 for Mac: If you're a volume licensed customer, you can upgrade to Office 2019 for Mac without uninstalling Office 2016 for Mac. You just need to download the 2019 version of the Volume License (VL) Serializer from the Volume Licensing Service Center (VLSC) and deploy it to each computer running Office 2016 for Mac. If you need to go back to Office 2016 for Mac after you've upgraded, follow these steps.
Version numbers Version numbers of 16.17 or higher for retail or volume licensed installs indicate you have Office 2019 for Mac. Office 2016 for Mac has version numbers of 16.16 or lower. Since the 'major' version (16) hasn't changed between Office 2016 for Mac and Office 2019 for Mac, application settings, including policies, preferences, and preference domains are similar between the two versions. Also, add-ins and other extensibility solutions that are compatible with Office 2016 for Mac will most likely be compatible with Office 2019 for Mac or will require minimal testing.