Patch beta2 with TR

[Innocent Devil]

is it possible to do the msi patching to patch beta2 by TR

by /extract switch to extract both and

instead of putting the patches in update directory of beta 2 ???

[fizban2]

you could chain method to patch the files, but why would you want to? it would be doing the same thing as adding them to the updates folder.

note,

just checking the TR2 files, there is no MSI files, only MSP. so truly the only way to do the update is through the setup file or by adding the files to the update folder

[Innocent Devil]

I did it.

But then i had to waste 1.5GB of my HDD

all the backup "MSOCache" => 459 MB (original beta2)

and the patches backup in C:\windows\Installer => 1.02GB (msp files and configs)

So if the patches were applied before install

then it would cost abt 500+ or something for MSOCache folder only,

isn't it ??

[fizban2]

those files can be deleted once your installation has finished, i have not found a way to do it from an automated install yet though

[Innocent Devil]

Okay, if i can delete all those files safely then no probz

[fizban2]

shouldn't be an issue but be warned***

Changes in the 2007 Office system

Administrative installation images

Description: Administrative installation images have been replaced by a required local installation source.

Reason for change: Administrative installation images were difficult to sustain. Requiring a local installation source prevents source resiliency problems when updating.

http://technet2.microsoft.com/Office/en-us...3.mspx?mfr=true

more info here

[fizban2]

More Info (:-D i can find stuff if i ever have any freaking free time)

Precache the local installation source for the 2007 Office system

When you deploy the 2007 Microsoft Office system, Setup creates a local installation source on the user's computer — a copy of the compressed source files for the Office product you are installing. Once the files have been copied to the user's computer, Setup completes the installation from the local installation source. You can minimize the load on your network by deploying the local installation source separately, before you deploy Office.

To deploy the local installation source by itself

1. On the network installation point, open the Config.xml file in a text editor such as Notepad.

By default, Config.xml is located in the core product folder for the Office product you are installing. For example, if you are installing Microsoft Office Professional 2007, open the Config.xml file in the Pro.WW folder.

2. Find the <LIS> element; uncomment the line by deleting the opening <!-- and closing --> tags.

3. Set the <CacheAction> attribute to "CacheOnly".

The line in Config.xml should look like this:

<LIS CacheAction="CacheOnly" />

4. Save the Config.xml file.

5. Run Setup.exe on users' computers; on the Setup command line, specify the path to your modified Config.xml file.

Note that you must use a full qualified path. For example: \\server\share\Office12\setup.exe /config \\server\share\Office12\Pro.WW\Config.xml

where Office12 is the root of the network installation point.

Note:

If you precache the local installation source on users' computers and subsequently need to remove it, you can set the <CacheAction> attribute to "RemoveCacheOnly" and rerun Setup. This setting works only if users have not yet installed Office.

When users with a precached local installation source on their computers run Setup from the network installation point, most of the activity takes place on the local computer instead of over the network. Precaching also allows you to coordinate the upgrade to the new version. You can distribute the local installation source to groups of users over time and then schedule a simultaneous installation throughout the organization without over-taxing the network.

Setup handles the creation and maintenance of the local installation source automatically. The default location is \MSOCache\All Users at the root of the drive on which Office is installed. In addition to installing Office from the local installation source, Setup also uses it to repair, reinstall, or update Office later on. If the local installation source is corrupted or deleted, Setup uses the original source on the network to repair or recreate it.

[Innocent Devil]

but is it really a disk space wasting ???

It okay to cache in local system an can reduce network traffice during install

after install why it is kept ??

does it make repair frequent ??

[fizban2]

but is it really a disk space wasting ???

It okay to cache in local system an can reduce network traffice during install

after install why it is kept ??

does it make repair frequent ??

for the most part it is to deal with the issues companies have had with trying to fix office setups when patches would look out to a network share files the install files to configure office,

besides disk space is cheap these days,