Office 2003 Administrative Install

Frank Muk · May 18, 2004

Greetings!

One of the great changes Microsoft made with Office 2003 was saving the
install files to the hard drive so patches can be applied without having to
have the CD. Unfortunately, when installing from an administrative
installation using transforms, the setup files aren't copied over. It seems
like I've seen where there's a new setup.exe you can download from
Microsoft that'll go ahead and copy them over. Alas, other than the nagging
suspicion that it should be fairly straightforward, I don't have a clue.
Can you help me out?

Thanks in advance -

FM

Milly Staples [MVP - Outlook] · May 18, 2004

Have you tried the Office Resource Kit for Office 2003? Most items such as
this are included in the ORK.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, Frank Muk asked:

| Greetings!
|
| One of the great changes Microsoft made with Office 2003 was saving
| the install files to the hard drive so patches can be applied without
| having to have the CD. Unfortunately, when installing from an
| administrative installation using transforms, the setup files aren't
| copied over. It seems like I've seen where there's a new setup.exe
| you can download from Microsoft that'll go ahead and copy them over.
| Alas, other than the nagging suspicion that it should be fairly
| straightforward, I don't have a clue. Can you help me out?
|
| Thanks in advance -
|
| FM

Bill Bradley · May 18, 2004

Read the ORK, as she says, but, basically, providing you have the Select or
Enterprise license version (not the "off the shelf" version), you copy the
whole CD to the network, rather than doing an Administrative Installation
Point (AIP), as in previous versions, then, use the newer setup.exe (which
gives you more options over the caching process).

Bill Bradley · May 18, 2004

Read the ORK, as she says, but, basically, providing you have the Select or
Enterprise license version (not the "off the shelf" version), you copy the
whole CD to the network, rather than doing an Administrative Installation
Point (AIP), as in previous versions, then, use the newer setup.exe (which
gives you more options over the caching process).

Bill Bradley · May 18, 2004

Read the ORK, as she says, but, basically, providing you have the Select or
Enterprise license version (not the "off the shelf" version), you copy the
whole CD to the network, rather than doing an Administrative Installation
Point (AIP), as in previous versions, then, use the newer setup.exe (which
gives you more options over the caching process).

Bill Bradley · May 18, 2004

Read the ORK, as she says, but, basically, providing you have the Select or
Enterprise license version (not the "off the shelf" version), you copy the
whole CD to the network, rather than doing an Administrative Installation
Point (AIP), as in previous versions, then, use the newer setup.exe (which
gives you more options over the caching process).

Bill Bradley · May 18, 2004

Read the ORK, as she says, but, basically, providing you have the Select or
Enterprise license version (not the "off the shelf" version), you copy the
whole CD to the network, rather than doing an Administrative Installation
Point (AIP), as in previous versions, then, use the newer setup.exe (which
gives you more options over the caching process).

GMAN Slater · May 18, 2004

No the latest setup won't help you here...

Even though as you step through the CIW it would appear that it allows this, it doesn't. Microsoft has stated that to create a Local Installation Source requires that the installation source be in compressed form (i.e. from the CD), not uncompressed form of admin install point.

Like you I wanted the best of both worlds so to speak. I settled on copying the CD to disk and running CIW against the MSI there to create my custom transform. See:
http://www.microsoft.com/office/ork/2003/two/ch3/DepC06.htm

I'm using the latest setup.exe from:
http://www.microsoft.com/office/ork/2003/journ/NewSetupEXE.htm

and using the new ENFORCECACHE in the setup.ini file. In addition to setting:
CDCACHE=2
DELETEABLECACHE=0

this "Sets the local installation source to NoCleanUp in the Windows registry, so that even when users run the Disk Cleanup Wizard, the local installation source is not removed. "

This all works fine for the install, but the problem I am having with this setup is that if I try to chain updates to office in the setup.ini file I get prompted for the installation media!!! At this point nothing satisfies that request and I have to abort the patch install. Even if I try to apply the "full" patch (which isn't supposed to require the install files) not the "binary" patch I get prompted for the media. I have way over the 2.5GB required to get the complete source cached local. I have verified it is there with the files present (although after the first failed patch a few files like sku011.cab are removed and later prompted for when you try to run that same patch again or another one) and that the permissions are correct for access to it. Also since I have CDCACHE=2 in the setup.ini (which I verified from looking at the setup logs is getting parsed correctly), the install should abort if it can not cache the source.

Anyway sorry for stating my current problems in your thread, just wanted you to see some of the issues that might be in your future!

I will start another thread for this "chained updates" issue, but if anyone has successfully chained updates please let me know. I am following this:
http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

GMAN

GMAN Slater · May 18, 2004

No the latest setup won't help you here...

Even though as you step through the CIW it would appear that it allows this, it doesn't. Microsoft has stated that to create a Local Installation Source requires that the installation source be in compressed form (i.e. from the CD), not uncompressed form of admin install point.

Like you I wanted the best of both worlds so to speak. I settled on copying the CD to disk and running CIW against the MSI there to create my custom transform. See:
http://www.microsoft.com/office/ork/2003/two/ch3/DepC06.htm

I'm using the latest setup.exe from:
http://www.microsoft.com/office/ork/2003/journ/NewSetupEXE.htm

and using the new ENFORCECACHE in the setup.ini file. In addition to setting:
CDCACHE=2
DELETEABLECACHE=0

this "Sets the local installation source to NoCleanUp in the Windows registry, so that even when users run the Disk Cleanup Wizard, the local installation source is not removed. "

This all works fine for the install, but the problem I am having with this setup is that if I try to chain updates to office in the setup.ini file I get prompted for the installation media!!! At this point nothing satisfies that request and I have to abort the patch install. Even if I try to apply the "full" patch (which isn't supposed to require the install files) not the "binary" patch I get prompted for the media. I have way over the 2.5GB required to get the complete source cached local. I have verified it is there with the files present (although after the first failed patch a few files like sku011.cab are removed and later prompted for when you try to run that same patch again or another one) and that the permissions are correct for access to it. Also since I have CDCACHE=2 in the setup.ini (which I verified from looking at the setup logs is getting parsed correctly), the install should abort if it can not cache the source.

Anyway sorry for stating my current problems in your thread, just wanted you to see some of the issues that might be in your future!

I will start another thread for this "chained updates" issue, but if anyone has successfully chained updates please let me know. I am following this:
http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

GMAN

GMAN Slater · May 18, 2004

No the latest setup won't help you here...

Even though as you step through the CIW it would appear that it allows this, it doesn't. Microsoft has stated that to create a Local Installation Source requires that the installation source be in compressed form (i.e. from the CD), not uncompressed form of admin install point.

Like you I wanted the best of both worlds so to speak. I settled on copying the CD to disk and running CIW against the MSI there to create my custom transform. See:
http://www.microsoft.com/office/ork/2003/two/ch3/DepC06.htm

I'm using the latest setup.exe from:
http://www.microsoft.com/office/ork/2003/journ/NewSetupEXE.htm

and using the new ENFORCECACHE in the setup.ini file. In addition to setting:
CDCACHE=2
DELETEABLECACHE=0

this "Sets the local installation source to NoCleanUp in the Windows registry, so that even when users run the Disk Cleanup Wizard, the local installation source is not removed. "

This all works fine for the install, but the problem I am having with this setup is that if I try to chain updates to office in the setup.ini file I get prompted for the installation media!!! At this point nothing satisfies that request and I have to abort the patch install. Even if I try to apply the "full" patch (which isn't supposed to require the install files) not the "binary" patch I get prompted for the media. I have way over the 2.5GB required to get the complete source cached local. I have verified it is there with the files present (although after the first failed patch a few files like sku011.cab are removed and later prompted for when you try to run that same patch again or another one) and that the permissions are correct for access to it. Also since I have CDCACHE=2 in the setup.ini (which I verified from looking at the setup logs is getting parsed correctly), the install should abort if it can not cache the source.

Anyway sorry for stating my current problems in your thread, just wanted you to see some of the issues that might be in your future!

I will start another thread for this "chained updates" issue, but if anyone has successfully chained updates please let me know. I am following this:
http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

GMAN

GMAN Slater · May 18, 2004

No the latest setup won't help you here...

Even though as you step through the CIW it would appear that it allows this, it doesn't. Microsoft has stated that to create a Local Installation Source requires that the installation source be in compressed form (i.e. from the CD), not uncompressed form of admin install point.

Like you I wanted the best of both worlds so to speak. I settled on copying the CD to disk and running CIW against the MSI there to create my custom transform. See:
http://www.microsoft.com/office/ork/2003/two/ch3/DepC06.htm

I'm using the latest setup.exe from:
http://www.microsoft.com/office/ork/2003/journ/NewSetupEXE.htm

and using the new ENFORCECACHE in the setup.ini file. In addition to setting:
CDCACHE=2
DELETEABLECACHE=0

this "Sets the local installation source to NoCleanUp in the Windows registry, so that even when users run the Disk Cleanup Wizard, the local installation source is not removed. "

This all works fine for the install, but the problem I am having with this setup is that if I try to chain updates to office in the setup.ini file I get prompted for the installation media!!! At this point nothing satisfies that request and I have to abort the patch install. Even if I try to apply the "full" patch (which isn't supposed to require the install files) not the "binary" patch I get prompted for the media. I have way over the 2.5GB required to get the complete source cached local. I have verified it is there with the files present (although after the first failed patch a few files like sku011.cab are removed and later prompted for when you try to run that same patch again or another one) and that the permissions are correct for access to it. Also since I have CDCACHE=2 in the setup.ini (which I verified from looking at the setup logs is getting parsed correctly), the install should abort if it can not cache the source.

Anyway sorry for stating my current problems in your thread, just wanted you to see some of the issues that might be in your future!

I will start another thread for this "chained updates" issue, but if anyone has successfully chained updates please let me know. I am following this:
http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

GMAN

GMAN Slater · May 18, 2004

No the latest setup won't help you here...

Even though as you step through the CIW it would appear that it allows this, it doesn't. Microsoft has stated that to create a Local Installation Source requires that the installation source be in compressed form (i.e. from the CD), not uncompressed form of admin install point.

Like you I wanted the best of both worlds so to speak. I settled on copying the CD to disk and running CIW against the MSI there to create my custom transform. See:
http://www.microsoft.com/office/ork/2003/two/ch3/DepC06.htm

I'm using the latest setup.exe from:
http://www.microsoft.com/office/ork/2003/journ/NewSetupEXE.htm

and using the new ENFORCECACHE in the setup.ini file. In addition to setting:
CDCACHE=2
DELETEABLECACHE=0

this "Sets the local installation source to NoCleanUp in the Windows registry, so that even when users run the Disk Cleanup Wizard, the local installation source is not removed. "

This all works fine for the install, but the problem I am having with this setup is that if I try to chain updates to office in the setup.ini file I get prompted for the installation media!!! At this point nothing satisfies that request and I have to abort the patch install. Even if I try to apply the "full" patch (which isn't supposed to require the install files) not the "binary" patch I get prompted for the media. I have way over the 2.5GB required to get the complete source cached local. I have verified it is there with the files present (although after the first failed patch a few files like sku011.cab are removed and later prompted for when you try to run that same patch again or another one) and that the permissions are correct for access to it. Also since I have CDCACHE=2 in the setup.ini (which I verified from looking at the setup logs is getting parsed correctly), the install should abort if it can not cache the source.

Anyway sorry for stating my current problems in your thread, just wanted you to see some of the issues that might be in your future!

I will start another thread for this "chained updates" issue, but if anyone has successfully chained updates please let me know. I am following this:
http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

GMAN

Bjoern Schaefer · May 26, 2004