I did not have any specific changes required apart from also installing Project SP1 with the install and so just extracted the Service Pack to the same directory as Project and created a vbscript with the following content for a silent install
-----------------------------------------------------------
Set WshShell = CreateObject("wscript.shell")
Set objFSO = Wscript.CreateObject("Scripting.FileSystemObject")
'Install Project 2003 Professional with Service Pack 1
WshShell.run "msiexec.exe /I PRJPROE.MSI PIDKEY=XXXXXXXXXXXXXXXXXXX ALLUSERS=1 /qb!", 1, true
WshShell.run "msiexec.exe /p Project2003-KB837240-SP1.msp ALLUSERS=1 /qb!", 1, true
Batch file script for Project 2003 with MST file...
1) Download "ork.exe" (Office Resource Kit) from M$ website for Office 2003.
2) Run the Custom Installation Wizard that's part of the Toolkit to create your MST file.
3) Download Service Pack 2 for Project 2003, KB914455 and KB917151.
4) Create a batch file as follows...
REM -----------------------
REM Installing Project 2003
REM -----------------------
@echo off
\Project_2003\setup.exe TRANSFORMS=<YOUR MST FILE NAME>.MST /qb-
CLS
@echo on
REM Installing Project 2003 Service Pack 2
@echo off
\Project_2003\SP2\ohotfix.exe
CLS
@echo on
REM Installing Post Service Pack 2 Updates
@echo off
\Project_2003\SP2\KB914455\ohotfix.exe
\Project_2003\SP2\KB917151\ohotfix.exe
COPY "C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft Office\Microsoft Office Project 2003.lnk" "C:\Documents and Settings\%USERNAME%\Desktop"
Take the CD \Files\Setup\Setup.ini and copy it to your AIP or root folder where the SETUP.EXE is located.
Modify this INI file with correct MSI= and MST=
If the MST is loacted in the same folder as the Setup, you can set MST=@NameOfMst.mst
In the [Oprions] section add/change
COMPANYNAME=
ALLUSERS=1
In the [Display ] section set
Display=Quit or Basic
CompletionNotice=No
In the [Logging] section set
Path=\\Server\Share\Logging\Project2003
Template=Project2003_%computernane%:%username%(*).txt
At the end of the file add the following sections
[ChainedInstall_1]
Path=\\Server\Share\<path to KB>\ohotfix.exe
TaskType=exe
IgnoreReturnValue=0
Reboot=0
If more hotfixes, add a new section
[ChainedInstall_2]
Path=\\Server\Share\<path to KB>\ohotfix.exe
TaskType=exe
IgnoreReturnValue=0
Reboot=0
If more hotfixes, add a new section, and so on
[ChainedInstall_3]
If you prefare to rename the Setup.exe to Project2003.exe, then also remember to rename the INI to the same name.
When you start the EXE, the installation will run silent without any scripting at all.
Created an OPS file using the Microsoft Office 2003 Resource Kit Profile Wizard. The OPS can then be imported into an MST, which should be created using the Resource Kit Custom Installation Wizard.
The OPS file is optional, but was primarily used in this case, because we still have some legacy versions existing in our environment. So, via Group Policy, set the default Save As format to Project 98 compatibility. This setting will be removed once the rollout of Project 2003 is completed.
Until then, however, need to suppress the warning prompt that appears by default when saving in Project 98 format. Was able to accomplish this within the OPS file.
Also added the PIDKEY and REBOOT properties to the MST. Set REBOOT to ReallySuppress.
If you encounter an error which starts with:
The command is attempting to use a webpage from the site gbui://blank.htm/. You have not identified this site as a trusted site in Internet Explorer.
.....
after you try to launch Project 2003 then the following RegKey should help:
[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\MS Project\Options\Interface]
"GBUIDisplayToggle"=dword:00000000
Reviews related to Microsoft Microsoft Project 2003
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ
