R
RayT
Trying to upgrade our Office XP to 2003, 200 nodes, and make life a little
easier by creating Local Installtaion Source on all client machines so when
the next Service Pack comes out the CD will not be required. Wonderful
documentation on how to do this but the Local Installation Caching will not
work. I created a network share, Compressed CD image, and created a
transform, modified the setup.ini file as well. The office 2003 installs
fine applying my setup.ini settings as well as my transform settings except
where is my Local Installation Source? From my log file i see the following:
Failed to download file: DW20.ADM_1033.
Error 0x8007000f
Failed to download file.
Retrying error for resource: DW20.ADM_1033
Download retry 0 failed: 0x8007000f
Download retry 1 failed: 0x8007000f
Download retry 2 failed: 0x8007000f
Error 0x8007000f
failed to wait for file
LocalCache has failed. Exiting...
Shutting down chained setup processing.
So is there a reason that the local installation source caching fails, what
is Microsofts stance on this issue? It's obviously some sort of bug, what is
the fix?
easier by creating Local Installtaion Source on all client machines so when
the next Service Pack comes out the CD will not be required. Wonderful
documentation on how to do this but the Local Installation Caching will not
work. I created a network share, Compressed CD image, and created a
transform, modified the setup.ini file as well. The office 2003 installs
fine applying my setup.ini settings as well as my transform settings except
where is my Local Installation Source? From my log file i see the following:
Failed to download file: DW20.ADM_1033.
Error 0x8007000f
Failed to download file.
Retrying error for resource: DW20.ADM_1033
Download retry 0 failed: 0x8007000f
Download retry 1 failed: 0x8007000f
Download retry 2 failed: 0x8007000f
Error 0x8007000f
failed to wait for file
LocalCache has failed. Exiting...
Shutting down chained setup processing.
So is there a reason that the local installation source caching fails, what
is Microsofts stance on this issue? It's obviously some sort of bug, what is
the fix?