Office 2003 administrative Install vs. CDCache with CAB

[eapy]

The following URL explain the benefits of deploying CABs with CDCache:

http://www.microsoft.com/office/ork/2003/two/ch3/DepC06.htm

Microsoft finally come up with the long-waited solution to avoid "Insert CD Media" issue and lots-of-small-file issues.

It explains how you can make a network sharepoint effectively but didn't say anything for the Enterprise Software Distribution Tool (Marimba, Novadigm, Tivoli, SMS, etc.) Packaging Best Practice and how we (as a system administrators) would deal with the Patch.

Q1. My best guess would be use the same practice (Deploy Cab files) but what's Microsoft's answer for this? do we still have to perform /a (administrative install) first and then publish them up?

Q2. When Microsoft releases new patches (either SR level or SP level), do we have to simply queue up the patches in sequence on ESD? or follow the exisitng practice (/p /a to apply the patch to the sharepoint and publish new files)?

Q3. If we choose Cab file deploy (instead of /a deploy) and Microsoft officially release SR1 or 2, do we simply replace the whole Cabs with new version and 1) uninstall and reinstall the whole thing since I know that the install will complain that there is anothor product is already installed.

Please answer these questions if you know the answers:

TIA

 

[Bob Buckland ?:-\)]

Hi Eapy,

Except for its own SMS product MS hasn't provided
'how to' practices for 3rd party deployment tools
in the Office Resource Kits Generally documenting
the methods for working with those tools is left to the
manufacturers of those tools although in the link
below they do mention Tivoli <g>

The methods you can use for deploying updates do,
as you mentioned, depend on the initial deployment
approach you select. This section of the Office 2003
Resource Kit discusses the update approaches:
http://microsoft.com/office/ork/2003/five/ch18/MntA01.htm
You would not cneed to reate an Office Admin Installation
Point (OAIP) for updating if you had not deployed from one
but can use the OHotfix utility.

While it's not ideal some product patch updates may require
the use of the product and it's often a good idea to
test each updated product after a patch rather than applying
a 'catchup' string of updates at once.

MS has generally gotten away from Office Service Release
updates (where a matching, updated, full product CD is
also available).

As a side note, the cached CAB files can cut down the
need for the CD, but may not totally eliminate it and
you can still install from a CD image. One thing that
can happen, for example, with the cached CAB files is
that folks may use the Windows Disk Cleanup tool
from Start=>Programs=>Accessories=>System Tools and
check the box that removes those files (there is a
new choice for that tool that cleans up left over
Office temp files and folks may tend to assume they
should click on both choices).

========
The following URL explain the benefits of deploying CABs with CDCache:

http://www.microsoft.com/office/ork/2003/two/ch3/DepC06.htm

Microsoft finally come up with the long-waited solution to avoid "Insert CD Media" issue and lots-of-small-file issues.

It explains how you can make a network sharepoint effectively but didn't say anything for the Enterprise Software Distribution Tool
(Marimba, Novadigm, Tivoli, SMS, etc.) Packaging Best Practice and how we (as a system administrators) would deal with the Patch.

Q1. My best guess would be use the same practice (Deploy Cab files) but what's Microsoft's answer for this? do we still have to
perform /a (administrative install) first and then publish them up?

Q2. When Microsoft releases new patches (either SR level or SP level), do we have to simply queue up the patches in sequence on ESD?
or follow the exisitng practice (/p /a to apply the patch to the sharepoint and publish new files)?

Q3. If we choose Cab file deploy (instead of /a deploy) and Microsoft officially release SR1 or 2, do we simply replace the whole
Cabs with new version and 1) uninstall and reinstall the whole thing since I know that the install will complain that there is
anothor product is already installed.

Please answer these questions if you know the answers:

TIA>>
--
I hope this helps you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

The Office 2003 System parts explained
http://microsoft.com/uk/office/preview/system.asp

MS on 'Why Office System 2003'
http://microsoft.com/mscorp/execmail/2003/10-13productivity.asp