Help Center

Follow

Install Office 365 2016 Skype for Business/Lync (and probably other Office 365 applications)

This article has been superseded by this document, linked here: Install and Uninstall Skype for Business: Office Customization Tool and Click-to-Run

It is strongly recommended you follow the article linked above to complete your installation of Skype for Business. While it is possible the instructions included in this document may work, the contents have not been tested with newer versions of PDQ.com products or with regard to changes made to Office 365 deployment scenarios.

Purpose:
This article is no longer current or maintained. For the most current version of this article, please see Install and Uninstall Skype for Business: Office Customization Tool and Click-to-Run

This article provides guidance on deploying Office 365 Skype for Business 2016 throughout your organization on machines that have Office 365 2016 installed and on machines that do not have any version of Office 365 installed. The same instructions may work for deploying other Office 365 products (e.g. Outlook, OneNote), but such instructions are beyond the scope of this document. For the full Office 365 installation and more, see Silently Install Office 365.

Important Notes/prerequisites:

  • You must be using PDQ Deploy in Pro Mode or higher to deploy in accordance with the provided instructions.
  • If Office 365 2013 is installed, the package will fail, typically with an error code 17002, indicating an incorrect target version. You can either modify the steps in this document to install Skype for Business 2013 or you can uninstall the current Office 365 2013 product before deploying the Skype for Business Office 365 2016 product.
  • You cannot mix 32-bit Office installations and 64-bit Office installations of the same version. If Office 365 64-bit is installed, 64-bit Skype for Business must also be installed. Likewise with 32-bit versions of Office 365 and Skype for Business.
  • If other Office products are installed that are not Office 365 (e.g. Office Pro Plus 2013, Office Standard 2010, etc.), Skype for Business will install normally; other version(s) will not be uninstalled or otherwise molested by the installation regardless of whether they are 32-bit or 64-bit.

Resolution:
1. Download the Office 2016 Deployment Tool for Click-to-Run from Microsoft’s site: https://www.microsoft.com/en-us/download/details.aspx?id=49117

2. Create the necessary shared folders to serve the Office 365 deployment: \\server\share\

3. Install the Office 2016 Deployment Tool for Click-to-Run, choose the extraction location to the previously created \\server\share\

4. Copy the configuration.xml (installed with the deployment tool) to 2016config.xml or another name of your choosing, in the same directory

5. Create another directory inside \\server\share called 2016 (i.e. \\server\share\2016)

6. Edit 2016config.xml from Step 3 (change OfficeClientEdition to 64 if you're deploying the 64-bit rather than 32-bit version of Skype). Change the UNC of SourcePath to match your environment (in this example, the location where the Office files will be downloaded: \\server\share\2016)

<Configuration>
<Add SourcePath="\\server\share\2016" OfficeClientEdition="32">
<Product ID="O365ProPlusRetail" >
<Language ID="en-us" />
</Product>
</Add>
</Configuration>

7. Open a command prompt: modify then run the following command (use quotes if your paths contain spaces):

\\server\share\setup.exe /download \\server\share\2016config.xml

8. Wait for the download to complete, which may take some time. Once the command above has completed and you return to a prompt, you should now have the downloaded Office 365 files in \\server\share\2016

9. Make another copy of the configuration.xml and name it something meaningful, like skypeconfig.xml

10. Edit skypeconfig.xml and change SourcePath to the location of the Office install files from step 6 (change OfficeClientEdition to 64 if you're deploying x64 Skype rather than x86 -see notes in step 6 above):

<Configuration>
<Add SourcePath="\\server\share\2016\" OfficeClientEdition="32" Branch="Current">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
<ExcludeApp ID="Access" />
<ExcludeApp ID="Excel" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="InfoPath" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
<ExcludeApp ID="PowerPoint" />
<ExcludeApp ID="Project" />
<ExcludeApp ID="Publisher" />
<ExcludeApp ID="SharePointDesigner" />
<ExcludeApp ID="Visio" />
<ExcludeApp ID="Word" />
</Product>
</Add>
<Updates Enabled="TRUE" Branch="Current" />
<Display Level="None" AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="0" />
</Configuration>

Notes:

  • The XML elements in the above are excluding every Office application except “Lync” (Microsoft is calling Skype for Business “Lync” for use in this element). For a complete list of the ExcludeApp elements and the appropriate syntax, please see https://technet.microsoft.com/en-us/library/jj219426.aspx
  • You should change the Updates, Display, and Property elements to match your specific needs.

11. In PDQ Deploy, create a new deployment and name it something meaningful.

12. Create a Command step (delete the install step), modify to match your choices from above: "\\server\share\setup.exe" /configure "\\server\share\skypeconfig.xml"

13. Set the deployment Run As as "Deploy User (interactive)."

14. Test the deployment (Right-click and Deploy Once)

As with any custom deployment, it is strongly encouraged the deployment, and each/all steps therein, be thoroughly tested in a lab environment prior to releasing into production. While we do as much testing on as many machines with as many variables as possible, such testing is insufficient to cover all possible variables.

Special thanks to Jordan M. who provided valuable feedback and testing for this article.

See Also:
Install and Uninstall Skype for Business: Office Customization Tool and Click-to-Run
Deploy Office 365 2013 or Office 365 2016: A (more or less) Definitive Guide
Silently Installing Office 365
Silently Uninstall Office 2010
Deploy Office 2013 Using the Office Customization Tool (OCT) and PDQ Deploy

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk