Office 2010 rebuild MSOCache fails with SCCM TS Deployment
I'm working on an issue that affects Office 2010 task sequence deployments. First let's make sure I understand what is happening. When Office Setup runs it creates msocache and copies the installation files there. The files in msocache are used for the Office installation and for repairs/updates that require the original installation files. The location of the original installation files are recorded in the registry in case msocache ever needs to be rebuilt. The problem is with a SCCM TS deployment, the original installation files path is C:\_SMSTaskSequence\Packages\.... This directory is deleted when the TS completes. This makes it impossible to rebuild msocache.
I can create a MSP with setup /admin that contains a list of locations where the original installation files can be located. This takes care of new installations but doesn't address installations that have already taken place. I've located the registry keys used to store the original installation files path. I'm not sure if modifying these keys will have the desired or any unexpected results?
Does anyone have any experience with this? I've been unable to locate any references to this issue.
I can create a MSP with setup /admin that contains a list of locations where the original installation files can be located. This takes care of new installations but doesn't address installations that have already taken place. I've located the registry keys used to store the original installation files path. I'm not sure if modifying these keys will have the desired or any unexpected results?
Does anyone have any experience with this? I've been unable to locate any references to this issue.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
dandirk
12 years ago
MSOCACHE is generally copied locally to c:\MSOCACHE has a hidden folder. This circumvents any installation source issues because the installer itself creates its own source in the same place during installation.
Now you may see error 30066 with Office 2010 deployments (upgrades) where this cache has been deleted during a manual install... How updates are affected not sure, haven't run into any update issues so far in our Office 2010 deployment which is over 1000 computers so far.
http://blogs.technet.com/b/office_resource_kit/archive/2010/09/17/office-2010-setup-may-fail-when-upgrading-from-office-2003-if-the-office-2003-local-installation-source-lis-is-corrupt.aspx
Above is a good article on how to rebuild the msocache if needed.
Now you may see error 30066 with Office 2010 deployments (upgrades) where this cache has been deleted during a manual install... How updates are affected not sure, haven't run into any update issues so far in our Office 2010 deployment which is over 1000 computers so far.
http://blogs.technet.com/b/office_resource_kit/archive/2010/09/17/office-2010-setup-may-fail-when-upgrading-from-office-2003-if-the-office-2003-local-installation-source-lis-is-corrupt.aspx
Above is a good article on how to rebuild the msocache if needed.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
