- Deploy Office for Mac to users in your organization. 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.
- Hi, I have a user with a mac that is unable to see the install files with in the portal.office.com page. When I go to install status there is nothing listed on the page.
- Deploy Office 2016 for Mac using your preferred deployment tool or manually install it by double-clicking the installer package. Note: The Outlook Exchange Setup 5.5.0.scpt AppleScript assumes you’re using a volume license edition of Office and not Office 365. Office 365 not only requires activation but also supports Autodiscover.
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.
The problem is that the configuration.xml example provided with the Office 2016 Deployment Tool mentioned the product ID as 'O365ProPlusRetail', which is incorrect. The correct product id for Office 2016 is 'ProPlusRetail'.
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).
Adding images, video, hyperlinks and attachments is simple, and the project planning tools make it straightforward to turn ideas into action. MindManager from Mindjet is a powerful mind mapping tool that lets you organize your ideas in a single view, where you can easily drag and drop to gather and prioritize your ideas. Price: Free 16.
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).
Software Deployment Tools
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).
Principle Mirror for iOS lets others view your designs on their device. While designing, you can interact instantly by plugging your device into the computer. You can also export a standalone Mac. Itool for mac.
serversharesetup.exe /download /configuration.xml
Figure F
Office 2016 Deployment Tool For Mac
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
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)
Microsoft has released new deployment tools for Office 2013/2016 and Office 365. With these tools we can create offline installers for a range of Microsoft Office products. This article features step-by-step instructions how to create your customized installer.
Do I need the Deployment Tool?
A lot of Office 2013 and 2016 downloads are availabe as direct downloads, either with or without product key. Please check out or articles on Office 2013 and Office 2016 direct download links. If you don't find your required download there, you can proceed with the steps here in this article.
Step 1: Download and Run the Office Deployment Tool
First of all, you need the Microsoft Office Depolyment Tool. The tool exists in two versions for Office 2013 and Office 2016. Both tools are also suitable to create Office 365 installers, based on Office 2013 and Office 2016 respectively. Chip foose mac tool box. The installation media that the deployment tool downloads are all based on the click & run technology.
The download is a self-extracting application that contains two files, setup.exe and configuration.xml. Extract those files into a folder of your choice.
Step 2: Configure the Office Deployment Tool
Before you start downloading the installation files, you need to modify the configuration file. Instead of the file that ships with the download, you can use our version of configuration.xml, that is preconfigured for Office Professional Plus 32 bit (suitable for both 2013 and 2016 version). Simply download the configuration file from us, and replace the original one.
If you don't need to modify the configuration file, you can skip straight to step 3. However, you can further modify the configuration to create a tailor made Office installer, either by changing the existing values, or by adding new ones.
Changing the command
OfficeClientEdition='32'
to 64
creates an installer for the 64 bit edition. Changing the command
Product
to something else creates an installer for a different edition. For possible values, please refer to the following table. Edition | Value |
---|---|
Office 2013/2016 Home and Student | HomeStudentRetail |
Office 2013/2016 Personal | PersonalRetail |
Office 2013/2016 Home and Business | HomeBusinessRetail |
Office 2013/2016 Professional | ProfessionalRetail |
Office 2013/2016 Professional Plus | ProPlusRetail |
Office 365 Home Premium | O365HomePremRetail |
Office 365 Small Business Premium | O365SmallBusPremRetail |
Office 365 Business | O365BusinessRetail |
Office 365 Professional Plus | O365ProPlusRetail |
Access 2013/2016 | AccessRetail |
Excel 2013/2016 | ExcelRetail |
InfoPath 2013/2016 | InfoPathRetail |
OneNote 2013/2016 | OneNoteRetail |
Outlook 2013/2016 | OutlookRetail |
PowerPoint 2013/2016 | PowerPointRetail |
Publisher 2013/2016 | PublisherRetail |
Word 2013/2016 | WordRetail |
SharePoint Designer 2013 | SPDRetail |
Project 2013/2016 Standard | ProjectStdRetail |
Project 2013/2016 Professional | ProjectProRetail |
Project 2013/2016 Standard volume license | ProjectStdXVolume |
Project 2013/2016 Professional volume license | ProjectProXVolume |
Visio 2013/2016 Standard | VisioStdRetail |
Visio 2013/2016 Professional | VisioProRetail |
Visio 2013/2016 Standard volume license | VisioStdXVolume |
Visio 2013/2016 Professional volume license | VisioProXVolume |
Skype for Business Basic 2015 (Office 2013) | LyncEntryRetail |
Skype for Business 2015 (Office 2013) | LyncRetail |
Skype for Business Basic 2016 (Office 2016) | SkypeforBusinessEntryRetail |
Skype for Business 2016 (Office 2016) | SkypeforBusinessRetail |
Similarly, you can change the language edition by modifying the command
Language
. If you require multiple language packs for Office, you can add additional lines and provide one requred language ID per line. Please refer to the following table for a list of values. Language | Value |
---|---|
Arabic (Saudi-Arabia) | ar-sa |
Bulgarian (Bulgaria) | bg-bg |
Chinese, simplified (PR China) | zh-cn |
Chinese, traditional (Taiwan) | zh-tw |
Croatian (Croatia) | hr-hr |
Czech (Chech Replublic) | cs-cz |
Danish (Denmakr) | da-dk |
Dutch (Netherlands) | nl-nl |
English (USA) | en-us |
Estonian (Estonia) | et-ee |
Finnish (Finland) | fi-fi |
French (France) | fr-fr |
German (Germany) | de-de |
Greek (Greece) | el-gr |
Hebrew (Israel) | he-il |
Hindi (India) | hi-in |
Hungarian (Hungary) | hu-hu |
Indonesian (Indonesia) | id-id |
Italian (Italy) | it-it |
Japanese (Japan) | ja-jp |
Kazakh (Kazakhstan) | kk-kz |
Korean (Republic of Korea) | ko-kr |
Latvian (Latvia) | lv-lv |
Lithuanian (Lithuania) | lt-lt |
Malay (Malaysia) | ms-my |
Norwegian, Bokmål (Norway) | nb-no |
Polish (Poland) | pl-pl |
Portuguese (Brazil) | pt-br |
Portuguese (Portugal) | pt-pt |
Romanian (Romania) | ro-ro |
Russian (Russian Federation) | ru-ru |
Serbian, Latin (Serbia / Montenegro) | sr-latn-cs |
Slovakian (Slovakia) | sk-sk |
Slovenian (Slovenia) | sl-si |
Spanish (Spain) | es-es |
Swedish (Sweden) | sv-se |
Thai (Thailand) | th-th |
Turkish (Turkey) | tr-tr |
Ukrainian (Ukraine) | uk-ua |
Vietnamese (Vietnam) | vi-vn |
The command
Updates Enabled='TRUE'
enables automatic updates for Microsoft Office. If you want to disable updates, you can set the value to FALSE
. The line
AcceptEULA='TRUE'
suppresses the dialogue that requires the user to accept the Office license agreement. If you want to enable that dialogue, you can set the value to FALSE
. The line
Display Level='Full'
enables the UI during installation (progress bar etc.) If you want to install Office without user interface, please set the value to None
. You can supply a product key in your configuration file and enable automatic activaltion of the product. They key can be added with the command
Product PIDKEY='XXXXX-XXXXX-XXXXX-XXXXX-XXXXX'
. Of course you need to replace the XXX with a real product key. For automatic product activation, please insert the following line right after the line that contains the
Display Level
command: Finally, you can insert commands to exclude Office applications from the installation. Usually, the Click-to-Run installer adds all applications of the Office suite to your computer. Modifying the configuration provides a workaround here and gives you full control over the applications that are installed. Afther the line that contains the
Language ID
command, you can insert one or more lines of the following type: For a list of possible values, please refer to the following table.
Application | Value |
---|---|
Access | Access |
Excel | Excel |
InfoPath | InfoPath |
OneDrive | OneDrive |
OneDrive for Business | Groove |
OneNote | OneNote |
Outlook | Outlook |
PowerPoint | PowerPoint |
Project | Project |
Publisher | Publisher |
SharePoint Designer | SharePointDesigner |
Skype for Business | Lync |
Visio | Visio |
Word | Word |
We've covered only the most useful configuration option here. If you need to go more advanced, have a look at the official documentation.
To double check that the configuration file is valid, you can open it in Internet Explorer and verify that the xml has no errors.
Step 3: Download the Office installation files
To download the installation files, you open a command box and navigate to the download folder that contains the setup.exe and the configuration file. Now execute the following command.
There is no progress indicator. Once all files are downloaded, the process will simply stop. The installation files are all contained in a subfolder called
Office
. After the download is complete, the folder structure should roughly look as follows. Step 4: Create a Self-Extracting Installer
We now have all required files, and could go ahead install Microsoft Office with the setup.exe from the deployment tool and the modified configuration file.
However, let's create a self-extracting installer first, which can be used for easy storage and backup, as well as deploying the same software to multiple computers. The following steps are all based on WinRAR, but can be done with any archiving software that support self-extracting archives.
The archive needs to contain the files setup.exe, configuration.xml, and the Office folder including all subfolders and files. On the WinRAR configuration screen, you need to tick the box
Create SFX archive
, and provide an archive name for the installer. Office 2016 Deployment Tool For Mac
On the
Advanced
tab, you click the button to go to the SFX options. On the SFX options dialogue, you go to the
Setup
tab, and enter the following line into the textbox Run after extraction
. That was already everything. You can WinRAR let do its job, and create an SFX installer of your download. Starting the SFX installer will install your Office product either with or without user interface, according to your configuration.