How do I install MS Office 2003 Pro using SMS 2003?
How do I install MS Office 2003 Pro using SMS 2003?
I've created a New Custom Setup File.MST using the Custom Installation Wizard in Microsoft Office 2003 Resource Kit.
The New Custom Setup File.MST is now sitting on a network share with all the MS Office 2003 Pro files.
I have recieved a message after creating the New Custom Setup File.MST -
You have completed the Custom Installation Wizard.
- Your custom Windows Installer transform file is:
\\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003\New Custom Setup File.MST"
- To use your transform file, include it in the Office Setup command line. For example, the following will run setup quietly using your transform file:
setup.exe TRANSFORMS="\\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003\New Custom Setup File.MST" /qb-
There is no setup.exe file in \\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003.
What command line now do I run in SMS 2003 to install???
msiexec.exe /i PRO11.MSI \\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003\New Custom Setup File.MST" /qb-
msiexec.exe /i PRO11.MSI TRANSFORMS="\\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003\New Custom Setup File.MST" /qb-
msiexec.exe /i PRO11.MSI TRANSFORMS=New Custom Setup File.MST /qb!
msiexec.exe /iPRO11.MSI SETUPPRO.EXE TRANSFORMS=New Custom Setup File.MST /qb!
???
Please help!!!
I've created a New Custom Setup File.MST using the Custom Installation Wizard in Microsoft Office 2003 Resource Kit.
The New Custom Setup File.MST is now sitting on a network share with all the MS Office 2003 Pro files.
I have recieved a message after creating the New Custom Setup File.MST -
You have completed the Custom Installation Wizard.
- Your custom Windows Installer transform file is:
\\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003\New Custom Setup File.MST"
- To use your transform file, include it in the Office Setup command line. For example, the following will run setup quietly using your transform file:
setup.exe TRANSFORMS="\\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003\New Custom Setup File.MST" /qb-
There is no setup.exe file in \\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003.
What command line now do I run in SMS 2003 to install???
msiexec.exe /i PRO11.MSI \\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003\New Custom Setup File.MST" /qb-
msiexec.exe /i PRO11.MSI TRANSFORMS="\\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003\New Custom Setup File.MST" /qb-
msiexec.exe /i PRO11.MSI TRANSFORMS=New Custom Setup File.MST /qb!
msiexec.exe /iPRO11.MSI SETUPPRO.EXE TRANSFORMS=New Custom Setup File.MST /qb!
???
Please help!!!
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
dunnpy
15 years ago
nkobas,
I personally would add a "new package from definition" in SMS and point it to the Office MSI file.
This will create programs for all of the installation options (per-machine unattented etc.) including MIF configuration.
You will then just need to modify the command line on your perferred program to include your transforms file and any log file you wish to create.
I would suggest you get a copy of the Administrators's Companion for Microsoft Systems Management Server 2003 (ISBN 0-7356-1888-7) and maybe get some SMS training - MS course 2596 covers all aspects of using SMS.
I found I was managing to get by in SMS until I did the courses/read the book, then realised there are better ways to manage things.
There is a sub-forum under Distribution for SMS, which is where this question probably should have been posted.
Hope this helps,
Dunnpy
I personally would add a "new package from definition" in SMS and point it to the Office MSI file.
This will create programs for all of the installation options (per-machine unattented etc.) including MIF configuration.
You will then just need to modify the command line on your perferred program to include your transforms file and any log file you wish to create.
I would suggest you get a copy of the Administrators's Companion for Microsoft Systems Management Server 2003 (ISBN 0-7356-1888-7) and maybe get some SMS training - MS course 2596 covers all aspects of using SMS.
I found I was managing to get by in SMS until I did the courses/read the book, then realised there are better ways to manage things.
There is a sub-forum under Distribution for SMS, which is where this question probably should have been posted.
Hope this helps,
Dunnpy
Posted by:
nkobas
15 years ago
Finally worked 
msiexec.exe /i PRO11.MSI TRANSFORMS=Custom.MST /qb-
Thanks all
msiexec.exe /i PRO11.MSI TRANSFORMS=Custom.MST /qb-
Thanks all
Posted by:
jmcfadyen
15 years ago
this is not an SMS forum its a windows installer forum as indicated on your other post www.myitforum.com is an sms based forum.
Posted by:
anonymous_9363
15 years ago
Bit harsh, John? His question doesn't in fact seem to be SMS-slanted. This particular forum still isn't *quite* the right place to ask, since there's no Package Development involved as such, but even so...I thought *I* was the hard man here! :)
This looks OK. Personally, I'd a log file:
......msiexec.exe /i PRO11.MSI TRANSFORMS="\\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003\New Custom Setup File.MST" /qb- /l*v %temp%\OfficePro11.log
msiexec.exe /i PRO11.MSI TRANSFORMS="\\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003\New Custom Setup File.MST" /qb-
This looks OK. Personally, I'd a log file:
......msiexec.exe /i PRO11.MSI TRANSFORMS="\\SERVER\MasterDisks\Server & Workstation\Microsoft\Office Packages\Office\Office 2003\New Custom Setup File.MST" /qb- /l*v %temp%\OfficePro11.log
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.