Install Project 2016 Alongside Office 2016
Question details
The user wants to add Project 2016 to an existing Office 2016 installation.

- Product
- Microsoft Project 2016 and Microsoft Office 2016
- Device & OS
- not provided
- Scenario
- Deploy Project 2016 with the Office Deployment Tool while keeping it compatible with the installed Office edition.
- Observed behavior
- Project 2016 should install alongside Office 2016 with a compatible architecture and deployment configuration.
In an Office app, open File > Account > About to check the installed version and whether it is 32-bit or 64-bit. Check the installation technology and update channel, confirm your Project license, and obtain the Office Deployment Tool from Microsoft.
Deploy Project 2016 with a matching configuration XML
Use the Office Deployment Tool to install a licensed Project edition that matches the existing Office installation.
The Project edition, installation technology, architecture, and update channel must be compatible with the existing Office installation. If Office uses an MSI installation rather than Click-to-Run, check Microsoft's coexistence guidance before proceeding.
A product ID alone does not guarantee a 2016 release. Use a compatible 2016 build and installation source available for your deployment, and verify the version settings before running the tool.
Open Word or another installed Office app and select File > Account > About. Record the version and 32-bit or 64-bit architecture; also check the update channel and installation technology shown in the account information.
Use Microsoft's Office Customization Tool at config.office.com or an XML editor to create a configuration XML. Select the Project edition covered by your license, match the Office architecture and channel, and specify the appropriate 2016 build and source. For Project Professional Retail, verify that the product ID is ProjectProRetail.
Open the saved XML in an editor and review its product ID, OfficeClientEdition, channel, version, language, and source settings against your existing installation and license. If using a third-party XML editor, review the site and any downloads carefully.
Extract the Microsoft Office Deployment Tool, open Command Prompt in its folder, and run setup.exe /configure followed by the path to your XML file, such as setup.exe /configure configuration.xml.
Open Project and select File > Account to check its activation and version. Test update behavior in a controlled environment; compatible Click-to-Run Office products generally share update settings, so do not assume Project updates independently.

Track project tasks with WPS Spreadsheets
WPS Office is a free, lightweight, easy-to-use alternative for everyday documents and spreadsheets. Its familiar interface and Microsoft Office format compatibility make it easier to move existing files into WPS. For simple project tracking, use a spreadsheet; WPS does not install or replace Microsoft Project.

Frequently Asked Questions
How do I check whether Office 2016 is 32-bit or 64-bit?
In an installed Office app, go to File > Account > About. The About window identifies the Office architecture.
Which product ID should I use for Project Professional Retail?
Use ProjectProRetail for Project Professional Retail, provided that it matches your license. Review the XML product ID before running the Office Deployment Tool.
Will the Office Deployment Tool automatically install the 2016 release?
Not necessarily. Check the configuration's version and source settings to ensure they refer to an available, compatible 2016 build rather than assuming the product ID alone selects that release.
Can Project and Office update independently?
Compatible Click-to-Run Office products generally share update settings. Check File > Account for update information and test the behavior in a controlled environment rather than assuming independent updates.
What if my existing Office 2016 installation uses MSI?
Check Microsoft's coexistence guidance for your exact Office and Project editions before deploying. The Click-to-Run configuration must be compatible with the existing MSI installation.




