Installing Office 2003 Professional with all current patches prompts for media

[GMAN Slater]

Trying to create a custom install of Office 2003 Pro from select media. Since I need to have the Local Installation Source created I am NOT using an admin install, but I am using the "compressed CD image" mentioned here:

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

I'm using the latest setup.exe and using the new ENFORCECACHE in the setup.ini file.as I need to abort the install if a Local Installation Source can not be created, and I need to reduce the chance of the user removing it. The latest setup is here:
http://www.microsoft.com/office/ork/2003/journ/NewSetupEXE.htm

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, directly or indirectly via ENFORCECACHE (which I verified from looking at the setup logs is getting parsed correctly), the install should abort if it can not cache the source.

For the chaining I am following these:
http://support.microsoft.com/?id=828947
http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

I would be glad to post all or part of my setup.ini, changing I am making in my transform, and the command line I am running to launch the install if needed.

My goal here is to create an install that can be ran from a network share or CD that will do a full unattended (but with basic!- display of progress) of Office with all updates chained in the setup.ini file. All appears to work but the chaining of updates. Which always requests the installation media despite the local installation source being present AND even if I use full patches that aren't supposed to require the source anyway!! I have turned up the logging via /lv* and I can see it is using my setup.ini specified via the /settings switch and that my transform is getting applied ( I do notice that Outlook 2003 Junk Filter is not set to High as I specified in the transform, but other than that everything from it is getting applied).

If anyone has made such a setup work please let me know. I am willing to pay good money for it!

GMAN

 

[GMAN Slater]

Well it looks like I'm the only one here with this problem, but I will post my findings anyway just in case someone tries to do a customized install of Office 2003 from CD, or even run patches off a CD.

After much testing, it comes down to the patches being on the CD itself. Move them to the hard drive or a network share and all is well. There are many documentations errors on the microsoft site for ORK. Here is one that effects chaining patches:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm
"To use Windows Installer to chain client patches
1.. Extract each binary patch (MSP file) from the corresponding client update (EXE file).
2.. In the Setup.ini file, chain Msiexec.exe to the core Office installation.
You must create a separate [ChainedInstall_n] section for each patch.

For example:

[ChainedInstall_1]
TASKTYPE=exe
PATH=C:\Windows\System32\MSIExec.exe
CmdLine=\\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo [path\name of log file]"This is incorrect as msiexec will cry with an invalid command line unless you prepend a /p like this:CmdLine=/p \\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo [path\name of log file]"Making that correction allows the setup to chain the patches if ran from a network share or hard drive, but it still doesn't work off a CD as you are prompted to "Please insert the disk: Microsoft Office Professional Edition 2003". when the first patch runs (in my case it was KB828041). Aborting this patch causes an even bigger problem. As the KB828041 install was aborted it removed a dozen or so files from the LIS. One of those was the SKU011.CAB file. After that any patching attempt prompts for media until you do a repair to get the LIS rebuilt.

So I changed my install and did not chain patches. Even then, if you try to run the patches from the CD (d: in this example) like so you will still run into the problem:
start /wait msiexec /p d:\mso-FullFile-GLB.msp /qb

Only solution I have found is to copy them to the HD during my install and then run the patches from there. My eample uses the "Full" patch file, but the same problem exists with the binary ones.

 

[GMAN Slater]

Well it looks like I'm the only one here with this problem, but I will post my findings anyway just in case someone tries to do a customized install of Office 2003 from CD, or even run patches off a CD.

After much testing, it comes down to the patches being on the CD itself. Move them to the hard drive or a network share and all is well. There are many documentations errors on the microsoft site for ORK. Here is one that effects chaining patches:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm
"To use Windows Installer to chain client patches
1.. Extract each binary patch (MSP file) from the corresponding client update (EXE file).
2.. In the Setup.ini file, chain Msiexec.exe to the core Office installation.
You must create a separate [ChainedInstall_n] section for each patch.

For example:

[ChainedInstall_1]
TASKTYPE=exe
PATH=C:\Windows\System32\MSIExec.exe
CmdLine=\\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo [path\name of log file]"This is incorrect as msiexec will cry with an invalid command line unless you prepend a /p like this:CmdLine=/p \\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo [path\name of log file]"Making that correction allows the setup to chain the patches if ran from a network share or hard drive, but it still doesn't work off a CD as you are prompted to "Please insert the disk: Microsoft Office Professional Edition 2003". when the first patch runs (in my case it was KB828041). Aborting this patch causes an even bigger problem. As the KB828041 install was aborted it removed a dozen or so files from the LIS. One of those was the SKU011.CAB file. After that any patching attempt prompts for media until you do a repair to get the LIS rebuilt.

So I changed my install and did not chain patches. Even then, if you try to run the patches from the CD (d: in this example) like so you will still run into the problem:
start /wait msiexec /p d:\mso-FullFile-GLB.msp /qb

Only solution I have found is to copy them to the HD during my install and then run the patches from there. My eample uses the "Full" patch file, but the same problem exists with the binary ones.

 

[GMAN Slater]

Well it looks like I'm the only one here with this problem, but I will post my findings anyway just in case someone tries to do a customized install of Office 2003 from CD, or even run patches off a CD.

After much testing, it comes down to the patches being on the CD itself. Move them to the hard drive or a network share and all is well. There are many documentations errors on the microsoft site for ORK. Here is one that effects chaining patches:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm
"To use Windows Installer to chain client patches
1.. Extract each binary patch (MSP file) from the corresponding client update (EXE file).
2.. In the Setup.ini file, chain Msiexec.exe to the core Office installation.
You must create a separate [ChainedInstall_n] section for each patch.

For example:

[ChainedInstall_1]
TASKTYPE=exe
PATH=C:\Windows\System32\MSIExec.exe
CmdLine=\\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo [path\name of log file]"This is incorrect as msiexec will cry with an invalid command line unless you prepend a /p like this:CmdLine=/p \\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo [path\name of log file]"Making that correction allows the setup to chain the patches if ran from a network share or hard drive, but it still doesn't work off a CD as you are prompted to "Please insert the disk: Microsoft Office Professional Edition 2003". when the first patch runs (in my case it was KB828041). Aborting this patch causes an even bigger problem. As the KB828041 install was aborted it removed a dozen or so files from the LIS. One of those was the SKU011.CAB file. After that any patching attempt prompts for media until you do a repair to get the LIS rebuilt.

So I changed my install and did not chain patches. Even then, if you try to run the patches from the CD (d: in this example) like so you will still run into the problem:
start /wait msiexec /p d:\mso-FullFile-GLB.msp /qb

Only solution I have found is to copy them to the HD during my install and then run the patches from there. My eample uses the "Full" patch file, but the same problem exists with the binary ones.

 

[GMAN Slater]

Well it looks like I'm the only one here with this problem, but I will post my findings anyway just in case someone tries to do a customized install of Office 2003 from CD, or even run patches off a CD.

After much testing, it comes down to the patches being on the CD itself. Move them to the hard drive or a network share and all is well. There are many documentations errors on the microsoft site for ORK. Here is one that effects chaining patches:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm
"To use Windows Installer to chain client patches
1.. Extract each binary patch (MSP file) from the corresponding client update (EXE file).
2.. In the Setup.ini file, chain Msiexec.exe to the core Office installation.
You must create a separate [ChainedInstall_n] section for each patch.

For example:

[ChainedInstall_1]
TASKTYPE=exe
PATH=C:\Windows\System32\MSIExec.exe
CmdLine=\\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo [path\name of log file]"This is incorrect as msiexec will cry with an invalid command line unless you prepend a /p like this:CmdLine=/p \\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo [path\name of log file]"Making that correction allows the setup to chain the patches if ran from a network share or hard drive, but it still doesn't work off a CD as you are prompted to "Please insert the disk: Microsoft Office Professional Edition 2003". when the first patch runs (in my case it was KB828041). Aborting this patch causes an even bigger problem. As the KB828041 install was aborted it removed a dozen or so files from the LIS. One of those was the SKU011.CAB file. After that any patching attempt prompts for media until you do a repair to get the LIS rebuilt.

So I changed my install and did not chain patches. Even then, if you try to run the patches from the CD (d: in this example) like so you will still run into the problem:
start /wait msiexec /p d:\mso-FullFile-GLB.msp /qb

Only solution I have found is to copy them to the HD during my install and then run the patches from there. My eample uses the "Full" patch file, but the same problem exists with the binary ones.

 

[GMAN Slater]

Well it looks like I'm the only one here with this problem, but I will post my findings anyway just in case someone tries to do a customized install of Office 2003 from CD, or even run patches off a CD.

After much testing, it comes down to the patches being on the CD itself. Move them to the hard drive or a network share and all is well. There are many documentations errors on the microsoft site for ORK. Here is one that effects chaining patches:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm
"To use Windows Installer to chain client patches
1.. Extract each binary patch (MSP file) from the corresponding client update (EXE file).
2.. In the Setup.ini file, chain Msiexec.exe to the core Office installation.
You must create a separate [ChainedInstall_n] section for each patch.

For example:

[ChainedInstall_1]
TASKTYPE=exe
PATH=C:\Windows\System32\MSIExec.exe
CmdLine=\\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo [path\name of log file]"This is incorrect as msiexec will cry with an invalid command line unless you prepend a /p like this:CmdLine=/p \\server\share\admin_install_point\1234\[MSP file] /qb /lpiwaeo [path\name of log file]"Making that correction allows the setup to chain the patches if ran from a network share or hard drive, but it still doesn't work off a CD as you are prompted to "Please insert the disk: Microsoft Office Professional Edition 2003". when the first patch runs (in my case it was KB828041). Aborting this patch causes an even bigger problem. As the KB828041 install was aborted it removed a dozen or so files from the LIS. One of those was the SKU011.CAB file. After that any patching attempt prompts for media until you do a repair to get the LIS rebuilt.

So I changed my install and did not chain patches. Even then, if you try to run the patches from the CD (d: in this example) like so you will still run into the problem:
start /wait msiexec /p d:\mso-FullFile-GLB.msp /qb

Only solution I have found is to copy them to the HD during my install and then run the patches from there. My eample uses the "Full" patch file, but the same problem exists with the binary ones.