B
Bob Buckland ?:-\)
Hi J.P.
You're correct. Using an Office Installation Point takes you through a different path for deployment options and for
maintenance/upgrading of workstation.
With Office 2003 on deployment you're basically choosing between an Office Administrative Point and using the MS Office Cache
maintained as a Local Installation Source on client computers.
Dan's articles, (like the one you linked to) often based on the Office Resource Kit with explanations and graphics added to make
things clearer have been helpful. This one might make it clearer that with Office 2003 that there is an alternative to the method
that's been used in prior versions of Office as the 'preferred' deploy and update method (patching an Office Admin Point)
Both methods are viable approaches, they're just not real good at being 'mixed and matched' <g> to a single client PC.
For Office 2003 this page from the Office 2003 Resource Kit (ORK2003) may be helpful to you. It has the procedure to use for
updating a Local Installation source. Basically updates are chained as part of a new installation or applied to an existing LIS.
Reference: Distributing Office 2003 Product Updates
http://office.microsoft.com/en-us/assistance/HA011402381033.aspx
I'm not entirely clear from your message if you were deploying to additional computers, in which case you are correct, there would
be no Local Installation Source created when distriuting from an Office Admin Installation Point (OAIP), or if you're trying to
bring up to date previously deployed workstations. In the latter case it's possible that the MSOCache could still be present but
that the links in the registry for it have been removed with the run from the OAIP.
In the latter case,depending on what you find you may be able to 'put things back', if you want to use the but this is just
guesswork at this point, and a bit messy.
If it was just a case of the registry entries gone missing then using the Local Installation Source (LIS) tool from the Office 2003
Resource Kit (http://microsoft.com/office/ork/2003) might be helpful, but with the deployment from an Office Admin Point image you
may need to
1. Remove/delete the Office Admin Point Image in the install location. (backup first for safe keeping).
2. Copy the original Office 2003 CD to that location.
3. Use the MSICuu (MS Installer Cleanup Utility) to remove the MS Office 2003 information from the registry on the client
computers.
4. Redploy with patching as described in the Office 2003 Resource Kit article above.
It's possible that recaching to do a reinstall from your Local Installation Source might work to save some of the steps and you
might want to test that. I'm not sure what residuals would be left in the registry from the 'paint over' installation.
===========
I have deployed 500 PC with Office 2003 SP1 by using LSI.
Worked like a charm.
Now, my goal is to have an integrated SP2 version.
I have follow the instruction on how to slipstream SP2 into Office.
http://www.petri.co.il/office_system_2003_sp_slipstreaming.htm
The problem now is, the LSI does not work anymore. Office 2003 SP2 gets
installed but, there is no MSOCache created on the local c:\ drive?
I think it is because I created a administrative install of Office 2003. (as
within the procedure)
The administrative install has a different stucture than the Office 2003 CD.
Anyone can give me a hint on that?
Regards
JP <<
--
Let us know if this helped you,
Bob Buckland ?
MS Office System Products MVP
Pricing and Packages for '2007 Microsoft Office System'
http://microsoft.com/office/preview
You're correct. Using an Office Installation Point takes you through a different path for deployment options and for
maintenance/upgrading of workstation.
With Office 2003 on deployment you're basically choosing between an Office Administrative Point and using the MS Office Cache
maintained as a Local Installation Source on client computers.
Dan's articles, (like the one you linked to) often based on the Office Resource Kit with explanations and graphics added to make
things clearer have been helpful. This one might make it clearer that with Office 2003 that there is an alternative to the method
that's been used in prior versions of Office as the 'preferred' deploy and update method (patching an Office Admin Point)
Both methods are viable approaches, they're just not real good at being 'mixed and matched' <g> to a single client PC.
For Office 2003 this page from the Office 2003 Resource Kit (ORK2003) may be helpful to you. It has the procedure to use for
updating a Local Installation source. Basically updates are chained as part of a new installation or applied to an existing LIS.
Reference: Distributing Office 2003 Product Updates
http://office.microsoft.com/en-us/assistance/HA011402381033.aspx
I'm not entirely clear from your message if you were deploying to additional computers, in which case you are correct, there would
be no Local Installation Source created when distriuting from an Office Admin Installation Point (OAIP), or if you're trying to
bring up to date previously deployed workstations. In the latter case it's possible that the MSOCache could still be present but
that the links in the registry for it have been removed with the run from the OAIP.
In the latter case,depending on what you find you may be able to 'put things back', if you want to use the but this is just
guesswork at this point, and a bit messy.
If it was just a case of the registry entries gone missing then using the Local Installation Source (LIS) tool from the Office 2003
Resource Kit (http://microsoft.com/office/ork/2003) might be helpful, but with the deployment from an Office Admin Point image you
may need to
1. Remove/delete the Office Admin Point Image in the install location. (backup first for safe keeping).
2. Copy the original Office 2003 CD to that location.
3. Use the MSICuu (MS Installer Cleanup Utility) to remove the MS Office 2003 information from the registry on the client
computers.
4. Redploy with patching as described in the Office 2003 Resource Kit article above.
It's possible that recaching to do a reinstall from your Local Installation Source might work to save some of the steps and you
might want to test that. I'm not sure what residuals would be left in the registry from the 'paint over' installation.
===========
I have deployed 500 PC with Office 2003 SP1 by using LSI.
Worked like a charm.
Now, my goal is to have an integrated SP2 version.
I have follow the instruction on how to slipstream SP2 into Office.
http://www.petri.co.il/office_system_2003_sp_slipstreaming.htm
The problem now is, the LSI does not work anymore. Office 2003 SP2 gets
installed but, there is no MSOCache created on the local c:\ drive?
I think it is because I created a administrative install of Office 2003. (as
within the procedure)
The administrative install has a different stucture than the Office 2003 CD.
Anyone can give me a hint on that?
Regards
JP <<
--
Let us know if this helped you,
Bob Buckland ?
MS Office System Products MVP
Pricing and Packages for '2007 Microsoft Office System'
http://microsoft.com/office/preview