Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 899361 - Last Review: August 29, 2006 - Revision: 3.5
White papers for the Microsoft Office 2003 service packs are available
INTRODUCTION
Microsoft has released white papers that contain documentation about the installation of the Microsoft Office 2003 service packs. To obtain the Microsoft Office 2003 Service Pack 2 (SP2) white paper, visit the following Microsoft Web site:
To obtain the Microsoft Office 2003 Service Pack 1 (SP1) white paper, visit the following Microsoft Web site:
Note The white papers for the Office 2003 service packs are available in the English language only.
MORE INFORMATION
The following is the table of contents for the Microsoft Office 2003 Service Pack 2 (SP2) white paper:
- INTRODUCTION
- Included in this service pack
- Minimum requirements to Install the Office 2003 SP2 Update
- PRODUCTS UPDATED BY THE MAIN OFFICE 2003 SP2 UPDATE
- Languages supported for Office 2003
- Microsoft products updated by separate Office 2003 SP2 stand-alone updates
- Critical public updates included in the main Office 2003 SP2 Update
- ENGLISH-LANGUAGE CLIENT AND FULL-FILE UPDATES ON OFFICE ONLINE
- OFFICE 2003 SP2 UPDATES AND ENHANCEMENTS FOR INFOPATH, ONENOTE, AND OUTLOOK
- InfoPath (previously available in Office 2003 Service Pack 1)
- OneNote (previously available in Office 2003 Service Pack 1)
- Outlook
- FULL USER INTERFACE INSTALLATION
- OVERVIEW OF RECOMMENDED DEPLOYMENT METHODS
- Deploying software by using the local installation source
- Administrative installation point
- Deploying software packages by using Group Policy object
- Installing Office Updates by using Windows Server Update Services
- Useful Windows Server Update Services and Office Update articles
- TAKING ADVANTAGE OF THE LOCAL INSTALLATION SOURCE
- Setup Settings file (Setup.ini)
- Scenario 1
- Scenario 2
- Scenario 3
- USING LISTOOL.EXE TO ENABLE, MOVE, OR DELETE THE LOCAL INSTALLATION SOURCE
- Enabling the local installation source
- Deleting and disabling the local installation source
- Moving the local installation source to a different drive
- Sample command lines
- RELYING ON THE LOCAL INSTALLATION SOURCE WHEN DISTRIBUTING CLIENT UPDATES
- Command lines for silent Office 2003 SP2 Update installations
- Why Microsoft recommends that you have a minimum of 500 MB of free space on the system partition when you install a full-file service pack update
- USING OHOTFIX.EXE FOR CLIENT UPDATES
- CUSTOMIZING OHOTFIX.INI FOR SILENT UPDATES
- OHotfix.ini default settings
- OHotfix.ini quiet installation settings
- Scenario
- OHotfix known issues
- CUSTOMIZING SETUP.INI TO CHAIN OFFICE 2003 SP2 WITH OFFICE 2003
- To chain the Office 2003 SP2 installation with the initial Office 2003 installation /settings file
- INSTALLING FUTURE SERVICE PACKS AND SECURITY UPDATES
- TROUBLESHOOTING OFFICE 2003 SP2 UPDATE INSTALLATION ISSUES
- Original Setup logs
- Windows Installer verbose logs
- Using an Office 2003 Setup log file to troubleshoot Setup problems
- Understanding OHotfix verbose logs
- Updating or replacing protected files
- ADVANTAGES OF WINDOWS INSTALLER 3.1
- Office 2003 Service Pack 2 known issues
- ADDITIONAL RESOURCES FOR UPDATING AND DEPLOYMENT
- Office 2003 Service Pack 2 Knowledge Base article resources
- Application issues fixed in Office 2003 SP2
- Post–Office 2003 SP2 Updates for Office 2003
- Troubleshooting Setup or updating problems
APPLIES TO
- Microsoft Office Professional Edition 2003
- Microsoft Office Standard Edition 2003
- Microsoft Office Small Business Edition 2003
- Microsoft Office Basic Edition 2003
- Microsoft Office Access 2003
- Microsoft Office OneNote 2003
- Microsoft Office PowerPoint 2003
- Microsoft Office Publisher 2003
| kbwhitepaper kbsetup atdownload kbinfo KB899361 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please