IT Pro Tips for Microsoft Project Professional 2007 12

Deployment Tips (14)

Most Common Setup Type

Not Determined

Average Package Difficulty Rating

Rated 2 / 5 (Somewhat Easy) based on 1 ratings

Most Commonly Reported Deployment Method

Vendor Provided Command Line (switch driven)

124

Note

MSI Cannot be edited
--------------------

Hi, the MSI (ProjectMUI.msi) cannot be edited using any other packaging tool. There is a checksum in the MSI, and if the MSI is changed, an error is prompted while installing the application.

Hence, all the changes need to be made using the Customization Toolkit.

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

matrixtushar
01/05/2007
Show Comments ( 0 )

121

Note

The MS Project 2007 can be customized by using the /admin switch in conjunction with the Setup.exe.

Hence, if you want to customize the installation and behaviour of the application, use "setup.exe /admin" switch to customize.

By using this switch, a file is created that contains the customizations. This file is applied at the time of installation and acts as a transform.

There is no separate application or resource kit to customize MSProject 2007. It can be done using the /admin option.

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

matrixtushar
12/20/2006
Show Comments ( 0 )

121

Note

Deploying via Active Directory
------------------------------

Step 1.
Create an MSP file using setup.exe /admin with your required settings and save to the "Updates" folder where your setup.exe is located.

Step 2.
Create an MSI wrapper with your chosen Packaging tool. I have used Wise for Windows Installer.
In the wrapper you will need to create a couple of custom actions.

These are as follows:

-In Execute Immediate
After Register Product
if NOT REMOVE~="ALL"
Set Property InstalProcess to [SOURCEDIR](SetLocation)
---------------------------
Custom Action Name: SetLocation
Property: InstallProcess
Property Value: [SOURCEDIR]
---------------------------
end if

-In Execute Deferred
Before Install Finalize
if NOT REMOVE~="ALL"
Call VBScript From Embedded Code (InstallProcess)
---------------------------
InstallProcess Code
---------------------------
strSourceDir = session.property("CustomActionData")
Set WshShell = CreateObject("WScript.Shell")

strCommand = strSourceDir & "setup.exe"
WshShell.Run strCommand, 1, 0

---------------------------
end if

if REMOVE~="ALL"
Call VBScript From Embedded Code (UnInstallProcess)
---------------------------
UnInstallProcess Code
---------------------------
Set WshShell = CreateObject("WScript.Shell")
strCommand = "msiexec.exe /x _ {90120000-003B-0000-0000-0000000FF1CE}"

WshShell.Run strCommand, 1, 0
---------------------------
end if

NOTE: Both of the above custom actions need to be set to run under Deferred Execution - System Context and Processing set to Async, No Wait.

Step 3.
Compile MSI. Copy MSI and Microsoft Project 2007 Professional to your Admin Install Point.

Step 4.
Publish your application to users via AD pointing to the MSI that you have created.

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

Psyrax
02/28/2008
Show Comments ( 0 )

39

Command Line

To repair the Project Professional 2007:

msiexec.exe /fa {90120000-003B-0000-0000-0000000FF1CE} /qn /norestart

Note: After repair restart is necessary otherwise application wonât work properly.

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

jay2010
10/27/2010
Show Comments ( 0 )

39

Command Line

To repair the Project Professional 2007:

msiexec.exe /fa {90120000-003B-0000-0000-0000000FF1CE} /qn /norestart

Note: After repair restart is necessary otherwise application wonÃ¢Â€Â™t work properly.

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

jay2010
10/27/2010
Show Comments ( 0 )

10

Command Line

Command line description:

setup.exe /?

Create MSP file in Office Customization Tool:

setup.exe /admin

Install:

setup.exe /adminfile "project.MSP" /config "PrjPro.WW\config.xml"

note: "project.msp" should be the file name you created and saved in the Office Customization Tool. If you have copied all your Office 2007 products to the same folder structure, use the config file option to specify the specific app you are installing, in this case project which is "PrjPro.WW\config.xml".

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

jcauthorn
02/18/2009
Show Comments ( 0 )

4

Note

Notes on suppressing the planning wizard and security notice after an UPGRADE:

The Global.mtp (global Template) file from the previous Project 200x install is what causes the pop-up.

If the Global.MPT file for the previously installed Project 200x is deleted during the Project Professional 2007 installation procedure, "Planning Wizard" and "Security Notice" dialog box will not pop-up when starting Project Professional 2007 on the client machine.

Removing the file will suppress the pop-up.

On my machine its here- C:\Documents and Settings\user_name\Application Data\Microsoft\MS Project\11\1033.

Note: If you need to keep the user customization settings in the Global.MPT file for the previously installed Project 2003, do not apply the above method to delete the Global.MPT file.

Script something similar to: del global.mpt /s
BEFORE you run the install.

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

jtow
06/16/2010
Show Comments ( 0 )

3

Command Line

uninstall:
setup.exe /uninstall PrjPror /config \\servername\share\officedir\PrjPror.WW\SilentUninstallConfig.xml

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

ribasnet
12/23/2008
Show Comments ( 0 )

2

Note

I used the /admin command switch and entered basic information: my company name, serial number, and removed two shortcuts. I saved it into the Updates folder and tried to install. It errored out stating that it couldn't install the language. I re-opened the patch file I just created, Select Feature Installation States, Expand Office Tools, and then set Language Settings tool to Not Available. Save and exit. Install succeeded on my next attempt. Hope this helps.

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

hfystff
11/14/2008
Show Comments ( 0 )

2

Note

[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\General]
"ShownFirstRunOptin"=dword:00000001

Use this reg setting to suppress the startup screen from Microsoft

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

an33th
06/02/2011
Show Comments ( 0 )

1

Note

Customizing Project Professional 2007
-------------------------------------

When finished with the customizations, we can save it as an MSP file (Patch). This patch can be added to the Update folder.

When you run Setup.exe to install the application, the patch gets applied.

Limitations
-----------
Creating an MSP has the following limitations:
1. No additional custom actions can be added in the MSP.
2. Properties such as ALLUSERS etc cant be changed.
3. Properties such as [WindowsVolume], [ProductName], [ProductVersion] etc cannot be resolved into their appropriate values.

Solution to the limitations
---------------------------
The solution to make the changes is that the MSI, which is a part of the installation can be edited using Orca or any other installer tool.

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

matrixtushar
12/21/2006
Show Comments ( 0 )

1

Virtualization

<POLICIES>
<LOCAL_INTERACTION_ALLOWED>TRUE</LOCAL_INTERACTION_ALLOWED>
</POLICIES>

the above entry needs to be added to the osd file when sequencing with microsoft appv

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

d4rkcell
10/29/2010
Show Comments ( 0 )

0

Note

Zenworks 11 Verify (repair) Notes: The verify action step will automatically populate with the repair switch. You'll need to add the product name pulled from the config file (this goes for all the office 2007 products). In this case the switches would be: /repair prjpro /config \\[path to the install media]\PrjPro.WW\config.xml In addition to the command line, we customized the config.xml so that it's silent, and called it during the various steps (install, uninstall, and repair) to prevent reboots and windows specific dialogues. Set the following lines in the config.xml ------------------ <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> ------------------ <Setting Id="SETUP_REBOOT" Value="never" /> ------------------ Note the lines need to be 'uncommented' out first, and that the default reboot syntax is incorrect.

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

Moedius
04/02/2012
Show Comments ( 0 )

0

Note

To "uncheck" the Advice from planning wizard I had to implement the following registry keys in my MSP:

HKCU\Software\Microsoft\Office\12.0\MS Project\Options\PlanningWizard
REG_DWORD
Name: Display PlanningWizard
Value:0
REG_SZ
Name: PlanningWizard Cases
Value: 11111111111111111111111111111111111111111111111111111

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

nucko
02/06/2009
Show Comments ( 0 )

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

12

Project Professional 2007

Version

12

Questions & Answers (6)

Questions & Answers related to Microsoft Project Professional 2007

1

ANSWERED

How to Deploy MS Project 2007 in Kace1000

By: khanman74 11 years ago 3.5k views

2

ANSWERS

Project 2007 SP2 APPCRASH, while closing first launch

By: talonsprem87 11 years ago 5.2k views

1

ANSWERS

Help reqiured in Pause command

By: krischaitu 14 years ago 3.4k views

27

ANSWERS

ms project 2007 - app-v

By: lady.d 14 years ago 20k views

5

ANSWERS

Project 2007/Office 2007 via GPO

By: mrflash 15 years ago 11k views

11

ANSWERS

Project 2007

By: linstead 17 years ago 10.5k views

Blogs (0)

Blog posts related to Microsoft Project Professional 2007

Links (2)

Links related to Microsoft Project Professional 2007

link

Office Customization Tool in Office 2010

By: Teitan 14 years ago 2.9k views

link

Online resource kit for Office 2007

By: Rhys 18 years ago 2.2k views

Reviews (0)

Reviews related to Microsoft Project Professional 2007

Microsoft Project Professional 2007

Don't be a Stranger!

Deployment Tips (14)

Inventory Records (1)

Project Professional 2007

Version

Questions & Answers (6)

Blogs (0)

Links (2)

Reviews (0)