How to Deploy Microsoft Project 2013 using SCCM

This post shows the steps to deploy Microsoft Project 2013 using SCCM. Microsoft Project 2013 application helps you plan and manage complex projects efficiently.

Project is released in two versions – Project online professional and project 2013. Project online professional offers more advantages over Project 2013. You can view the comparison table here.

In my previous posts we have seen deploying office 2010, 2013, Lync 2010, 2013 using SCCM. In this post we will look at the steps to deploy Microsoft Project 2013 using SCCM.

Most of all the deployment method shown in this post should work for both professional and standard editions of Project 2013. While I have got 32 bit copy of project professional 2013, you could use 64 bit copy with similar deployment steps.

In addition to the above point, Project Professional edition provides more features than Project Standard edition. If you are looking to understand about the licensing part, here is the link for that.

• How to Deploy Office 2010 using SCCM
• Deploying Office 2013 using SCCM
• Deploy Office 2016 using SCCM

How to Deploy Microsoft Project 2013 using SCCM

To deploy Microsoft Project 2013 using SCCM perform the following steps.

• Launch the configuration manager console.
• Navigate to Software Library > Overview > Application Management > Applications.
• Create a new application and select Manually specify the application information.

General Information – Provide the application name and some more details. Click Next.

Specify the configuration manager application catalog entry info. Click Next.

On the next screen Click on Add button to add new deployment type. Select Manually specify the deployment type information and click Next.

Content location – Specify path where the content is stored. Specify install and uninstall commands and click Next :-

Installation program – “setup” /config prjpro.ww\config.xml

Uninstall program – msiexec /q /x {90150000-002A-0000-1000-0000000FF1CE}

So basically my config.xml looks like this. This configuration file is stored in the prjpro.ww folder insider the project setup files.

<Configuration Product="PrjPro">

	<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
	
	<Logging Type="standard" Path="%temp%" Template="Microsoft Office Project Professional Setup(*).txt" />

	<USERNAME Value="sccmadmin" />
	
	<COMPANYNAME Value="tecdeploy" />
	
	<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->
	
	<!-- <LIS CACHEACTION="CacheOnly" /> -->
	
	<!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> -->
	
	<!-- <DistributionPoint Location="\\server\share\Office" /> -->
	
	<!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->
	
	<Setting Id="SETUP_REBOOT" Value="Never" />
	
	<!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->

</Configuration>

 

In the next step define the detection rule. Click Add Clause and enter the information in order.

Setting Type – Windows Installer

Product Code – {90150000-002A-0000-1000-0000000FF1CE}

Select this MSI product code must exist on target system and following condition must be met to detect the presence of application.

MSI Property – Version

Operator – Greater than or equal to

Value – 15.0.4569.1506

Click OK and click Next.

Specify the user experience settings for this application. Setting the program visibility to Hidden. Click Next.

Complete the remaining steps in wizard and finally on the completion page click Close.

Test the Project 2013 Deployment

First of all distribute the content to all the distribution points in your setup.

On the client machine, I could see the application in the software center. Click on application and click Install. Furthermore open the AppEnforce.log file to see the installation progress. We see that MS project 2013 has been installed successfully.

Testing the application uninstall and it worked well.