RE: Administrative Install OXP
From: Mark Plantenberg (markpl_at_online.microsoft.com)
Date: 05/18/04
- Previous message: Peter: "office 2003 on dvd?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 May 2004 21:06:19 GMT
<EMAILSUBJECT>Newsgroup Message Response to IssueID:
<ISSUEID></EMAILSUBJECT>
Hi Barry,
I wanted to inform you that I have replied to your thread in the Office
Setup Newsgroup titled: <NEWSGROUPSUBJECT> with IssueID: <ISSUEID>.
<a href="http://wwww.microsoft.com>
This issue may not be as easy as a simple registry hack or reinstall. There
are a few things to concider before 'Forcing' your updates.
There are three basic ways to handle Office deployments
1. SneakerNet: Running around with a CD of Office and applying client
updates as you get time. Hard to manage and know what is what
2. Create an Admin Point and deploy using GPO, SMS or other tool. Leave
Admin Piont at RTM level and apply client updates.
3. Create an Admin Point and deploy using GPO, SMS or other tool. Apply
updates to the Admin Point and Reinstall to clients. (Only updates newer
files)
Options 2 and 3 are very good options and can be easy to maintain. Option
three is less fexible as it will prevent client (non-SP) updates from being
applied as source files will not be at the expected level.
Rules of thumb for MSI/Office Deployments:
DO NOT MIX CLIENT AND ADMIN PATCHING!!!
1. If you install Office from an Admin Point that has been updated by small
updates past RTM or Baseline level (All Office XP SP's are baselines) you
CANNOT to apply ANY CLIENT Patches.
2. The Adverse is also ture: If you apply some client patches to a system
that has been installed from a baseline Admin Point and then update the
Admin point with Newer updates, the install will go well, but the Client
updates will be re-applied at the end of the install, effectively
downleveling the files updated by the client patch.
NOTE: Applying a new Service Pack obsoletes all client patches.
3. For the most part, you need to plan on having source files available
when applying Client updates. Many SP2 and newer FULL FILE(Admin) patches
do not require source files but client patches do.
4. When you create an Administrative Installation Point in Office XP, a
property is passed to disable CD media. (DISABLEMEDIA=1) This can be
neggated running DISABLEMEDIA-"" in the commandline while creatng wither
the AP or the client.
Other things to concider:
1. Was Office deployed via GPO at some point?
2. Do you want Office to stay in a 'Managed State'? (Managed by Group
Policy) If so, you need to apply the updates to the Admin point (304953)
and then perform a Redeploy of Office from the Users and Computers MMC.
3. Do you want to have all computers using the same deployment and patching
method? 307803
4. Do you have other methods that would make more sence in your
organization?
Related Articles:
====
Q307803 HOW TO: Bring an Unmanaged Installation of Office XP into a Managed
State
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q307803
Q312972 HOW TO: Use IntelliMirror in Windows 2000 to Deploy Office XP
Programs
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q312972
Setup Properties for Office XP
http://www.microsoft.com/office/ork/xp/appndx/setprop.htm
Q283686 OFFXP: Setup Command-Line Switches
http://support.microsoft.com/support/kb/articles/q283/6/86.asp
I hope this gives some insight. I'm sure it will bring up more questions.
To make you future Office updates and upgrades easier, take some time now
to think of what wouold be the best option in your environment
Please reply directly to the thread with any updates. You may receive this
email notification before you are able to view my reply in the newsgroup.
If you are unable to view the reply to your thread, please send me an email
with a description of the problem and what newsreader you are using.
Regards,
Mark Plantenberg
Microsoft Customer Support Services
- Previous message: Peter: "office 2003 on dvd?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
