This document shows the steps to deploy Microsoft Project 2013 using SCCM. Microsoft Project 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 this document we will look at the steps to deploy Microsoft Project 2013 using SCCM.

Most of all the deployment method shown in this document 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 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 SCCMDeploying Office 2013 using SCCMDeploy 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 andselect 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 typeinformation 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 setupfiles.

MS Project 2013 Configuration File

<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 ofapplication.

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. I prefer to deploy it for system whether or not user is logged on.Setting the program visibility to Hidden. Click Next.

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

Deploy Microsoft Project 2013 using SCCM

First of all let’s distribute the content to all the distribution points. Once you see the application is distributed, deploy it to adevice collection.

On the client machine, I could see the application in the software center. Click on application and click Install. Furthermoreopen 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.

Applications } .Appl1ication Detaills

Microsoft Project .2013 Professiona I

Published by Microsoft

IL r� �·-·1 II- �Install .. _, -·-

Configuration Manager Trace Log Tool - [C:\Windows\CCM\Logs\AppEnforce. log] Tools Window Help

Log Text Component

Prepared command line: "C:\Windows\sys.tem32\msiexec.exe" /q /x {90150000 ... AppEnforce• • ••

Working directory C:\Windows\ccmcache\1 Post install behavior is BasedOnExitCode Waiting for process 1212 to finish. Timeout= 120 minutes, P mcess 1212 terminated with exitmd e: 0 Looking for exit co,de O in exit codes tahl'e .. ,

. ..

AppEnforce AppEnforce AppEnforce AppEnforce AppEnforce

Matched exit code Oto a Success entry in exit codes ta hie, AppEnforce Performing detection of app deplo,yment type Install Microsoft Project 2013(Sc .. , AppEnforce

+++ Application not discovered, [AppDT Id: Scopeld_BCB118C2.-B950-4904-8F02 .... AppEnforce ++++++ App enforcement comp leted (4 sec

�8f r A�, P,T "Ins.tall re·s·a l�(nQ'fll

Date{Time: 7/31/2017 3,:30:40 PM Com�em:: r � ij Thread: 164 (OxA4) S01.11rce: appexrnlib,cpp:203

Date/Time Threa,d

7/31/2017 3:30:40 PM 164 (OxA4)

7/31/2017 3:30:40 PM 164 (OxA4) 7/31/2017 3:30:40 PM 164 (OxA4) 7/31/2017 3:30:40 PM 164 (OxA4) 7/31/2017 3.:30:45 PM 164 (OxA4) 7/31/2017 3:30:45 PM 164 (OxA4) 7/31/2017 3:30:45 PM 164 (OxA4) 7/31/2017 3:30:45 PM 164 (OxA4) 7/31/2017 3:30:45 PM 164 (OxA4) 7/31/2017 3:30:45 PM 164 (OxA4)

Executing Command line: i:: \Windows �ystem32vnsiexec. exe • /q /x {90150000-00cZA-0000-lOOO-OOOOOOOFF lCE} /qn with user context