Office 2003 - Local Installation Source Feature

D

Darren

Hi All

Is there any way to get the Local Installation Source feature to work when
you install Office Professional using the PRO11.MSI instead of using the
SETUPPRO.EXE.

I am trying to deploy office 2003 using Group Policy software distrubition.
The local installation source feature only seems to work if you use the
setuppro.exe. When I use the .MSI to run the install it does not create the
MSOCache hidden folder.

I have also tried using the custom installation wizard to create an MST
transform file that enables this feature. I have also modified the CDCACHE=2
entry in the setuppro.ini file. None of these changes seem to have any
effect when using the pro11.msi file to run the installation.

I can understand why from the information I found on the Office Resource Kit
Website http://www.microsoft.com/office/ork/2003/two/ch3/DepA03.htm#sub_4
but I'm wandering if there are any other settings\modifications I can try.

Thanks in advance for any suggestions

Darren
 
I

Ian Baird [MS]

Hi Darren,

01. The MSOCache can only be created from utilizing Setup.exe.

02. Active Directory is way to manage all of the applications in one
central area
-- admin install points, patch them and redeploy. You can only patch
either admin install point OR client side patching
(http//office.microsoft.com).

03. The generation of a local installation source is not provided by
Windows
Installer functionality. This functionality is provided by an
Office-specific
installation engine, the Office Source Engine (OSE.EXE).

Unfortunately, the limitation is with Intellimirror which is currently
unable to
automatically call Application-specific EXE’s such as Setup.exe and,
therefore,
relies completely on the Windows Installer ( Msiexec.exe) to perform
software
deployments.

The design of the Local Install Source is to take source management away
from
Windows Installer. During the initial setup process, a custom action
written
specifically for Office 2003, and called by Setup.exe, detects that the
installation is being performed from a compressed source and that the Local
Installation Source option has not been disabled. The following actions
are called
when the CDCACHE=1 or CDCACHE=2 property is set:

UpdateCacheSrcList and ProcessCacheSrcList

These actions create the following registry entries to ensure the local
installation source, \MSOCache, and any additional resiliency sources, are
appropriately registered; however, the Windows Installer SourceList is NOT
updated
with any information other than the path to the local source location.

HKEY_CLASSES_ROOT\Installer\Products\9040110900063D11C8EF10054038389C\Source
List
Value Name: LastUsedSource
Value Type: Reg_Expand_SZ
Value Data: n;1;C:\MSOCache\All Users\90000409-6000-11D3-8CFE-0150048383C9
Only the Office Source Engine (OSE.EXE) is aware of the following registry
entry
and queries for source(s) in this location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads
\9000040
9-6000-11D3-8CFE-0150048383C9\Sources

830168 Frequently Asked Questions About the Local Install Source Feature
http://support.microsoft.com/?id=830168

provides additional information regarding the MSOCache and supported
methods for removing or restoring the cache.

Hope this answers your question raised.

Regards,
Ian Baird
Microsoft PSS

This posting is provided 'AS IS' with no warranties and confers no rights.
 
I

Ian Baird [MS]

Hi Darren,

01. The MSOCache can only be created from utilizing Setup.exe.

02. Active Directory is way to manage all of the applications in one
central area
-- admin install points, patch them and redeploy. You can only patch
either admin install point OR client side patching
(http//office.microsoft.com).

03. The generation of a local installation source is not provided by
Windows
Installer functionality. This functionality is provided by an
Office-specific
installation engine, the Office Source Engine (OSE.EXE).

Unfortunately, the limitation is with Intellimirror which is currently
unable to
automatically call Application-specific EXE’s such as Setup.exe and,
therefore,
relies completely on the Windows Installer ( Msiexec.exe) to perform
software
deployments.

The design of the Local Install Source is to take source management away
from
Windows Installer. During the initial setup process, a custom action
written
specifically for Office 2003, and called by Setup.exe, detects that the
installation is being performed from a compressed source and that the Local
Installation Source option has not been disabled. The following actions
are called
when the CDCACHE=1 or CDCACHE=2 property is set:

UpdateCacheSrcList and ProcessCacheSrcList

These actions create the following registry entries to ensure the local
installation source, \MSOCache, and any additional resiliency sources, are
appropriately registered; however, the Windows Installer SourceList is NOT
updated
with any information other than the path to the local source location.

HKEY_CLASSES_ROOT\Installer\Products\9040110900063D11C8EF10054038389C\Source
List
Value Name: LastUsedSource
Value Type: Reg_Expand_SZ
Value Data: n;1;C:\MSOCache\All Users\90000409-6000-11D3-8CFE-0150048383C9
Only the Office Source Engine (OSE.EXE) is aware of the following registry
entry
and queries for source(s) in this location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads
\9000040
9-6000-11D3-8CFE-0150048383C9\Sources

830168 Frequently Asked Questions About the Local Install Source Feature
http://support.microsoft.com/?id=830168

provides additional information regarding the MSOCache and supported
methods for removing or restoring the cache.

Hope this answers your question raised.

Regards,
Ian Baird
Microsoft PSS

This posting is provided 'AS IS' with no warranties and confers no rights.
 
I

Ian Baird [MS]

Hi Darren,

01. The MSOCache can only be created from utilizing Setup.exe.

02. Active Directory is way to manage all of the applications in one
central area
-- admin install points, patch them and redeploy. You can only patch
either admin install point OR client side patching
(http//office.microsoft.com).

03. The generation of a local installation source is not provided by
Windows
Installer functionality. This functionality is provided by an
Office-specific
installation engine, the Office Source Engine (OSE.EXE).

Unfortunately, the limitation is with Intellimirror which is currently
unable to
automatically call Application-specific EXE’s such as Setup.exe and,
therefore,
relies completely on the Windows Installer ( Msiexec.exe) to perform
software
deployments.

The design of the Local Install Source is to take source management away
from
Windows Installer. During the initial setup process, a custom action
written
specifically for Office 2003, and called by Setup.exe, detects that the
installation is being performed from a compressed source and that the Local
Installation Source option has not been disabled. The following actions
are called
when the CDCACHE=1 or CDCACHE=2 property is set:

UpdateCacheSrcList and ProcessCacheSrcList

These actions create the following registry entries to ensure the local
installation source, \MSOCache, and any additional resiliency sources, are
appropriately registered; however, the Windows Installer SourceList is NOT
updated
with any information other than the path to the local source location.

HKEY_CLASSES_ROOT\Installer\Products\9040110900063D11C8EF10054038389C\Source
List
Value Name: LastUsedSource
Value Type: Reg_Expand_SZ
Value Data: n;1;C:\MSOCache\All Users\90000409-6000-11D3-8CFE-0150048383C9
Only the Office Source Engine (OSE.EXE) is aware of the following registry
entry
and queries for source(s) in this location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads
\9000040
9-6000-11D3-8CFE-0150048383C9\Sources

830168 Frequently Asked Questions About the Local Install Source Feature
http://support.microsoft.com/?id=830168

provides additional information regarding the MSOCache and supported
methods for removing or restoring the cache.

Hope this answers your question raised.

Regards,
Ian Baird
Microsoft PSS

This posting is provided 'AS IS' with no warranties and confers no rights.
 
I

Ian Baird [MS]

Hi Darren,

01. The MSOCache can only be created from utilizing Setup.exe.

02. Active Directory is way to manage all of the applications in one
central area
-- admin install points, patch them and redeploy. You can only patch
either admin install point OR client side patching
(http//office.microsoft.com).

03. The generation of a local installation source is not provided by
Windows
Installer functionality. This functionality is provided by an
Office-specific
installation engine, the Office Source Engine (OSE.EXE).

Unfortunately, the limitation is with Intellimirror which is currently
unable to
automatically call Application-specific EXE’s such as Setup.exe and,
therefore,
relies completely on the Windows Installer ( Msiexec.exe) to perform
software
deployments.

The design of the Local Install Source is to take source management away
from
Windows Installer. During the initial setup process, a custom action
written
specifically for Office 2003, and called by Setup.exe, detects that the
installation is being performed from a compressed source and that the Local
Installation Source option has not been disabled. The following actions
are called
when the CDCACHE=1 or CDCACHE=2 property is set:

UpdateCacheSrcList and ProcessCacheSrcList

These actions create the following registry entries to ensure the local
installation source, \MSOCache, and any additional resiliency sources, are
appropriately registered; however, the Windows Installer SourceList is NOT
updated
with any information other than the path to the local source location.

HKEY_CLASSES_ROOT\Installer\Products\9040110900063D11C8EF10054038389C\Source
List
Value Name: LastUsedSource
Value Type: Reg_Expand_SZ
Value Data: n;1;C:\MSOCache\All Users\90000409-6000-11D3-8CFE-0150048383C9
Only the Office Source Engine (OSE.EXE) is aware of the following registry
entry
and queries for source(s) in this location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads
\9000040
9-6000-11D3-8CFE-0150048383C9\Sources

830168 Frequently Asked Questions About the Local Install Source Feature
http://support.microsoft.com/?id=830168

provides additional information regarding the MSOCache and supported
methods for removing or restoring the cache.

Hope this answers your question raised.

Regards,
Ian Baird
Microsoft PSS

This posting is provided 'AS IS' with no warranties and confers no rights.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

office 2003 0
Office2007 Downgrade 2
Help! Using an MST file to modify installation with group policy 2
Microsoft Office Profession Edit. 2003 installation (repair) probl 3
my pro11.msi file isMissing,no cd,cant reinstall,HowICanGetANewOne 5
Question about Office/Access 2003 installation 0
Updates for Office 2003...no install disks and error pop ups... 4
Deploying Office 2003 Silent Install - Problem with Outlook 18

Top