Installed on First Use: network installation point vs. LIS

[Vadikan]

Hi, All!

While configuring Office 2007 with OCT I ran across two statements in the
OCT's help that seem to contradict to each other.

On the "Additional network sources" page it says:
"Setup looks for servers in this list, in the order specified, if it is
installing a feature on demand or repairing Office and the original network
installation point is unavailable."

however on the "Set feature installation states" it says:

"Installed on First Use Setup leaves components for the feature and all its
child features in the local installation source until the user attempts to
use the feature for the first time, at which time the components are
installed."

I'm aware that LIS is created during the setup, and according to the ORK
"the local installation source is a required part of the design."
http://technet2.microsoft.com/Office/f/?en-us/library/8295626a-4570-4b7f-91e3-717fe6b81f961033.mspx

Questions:
When does setup actually use additional installation sources for installing
features on first use or repairing Office applications? Does this happen only
when LIS is missing?

How does setup search for the installation source whenever it needs to
install a feature on first use or repair an application? Is it using the
sequence LIS -> Original network installation point -> Additonal network
sources?

I'd like to get definite answers, because I can do guessing myself Thanks
for your time and attention to my questions.

 

[Bob Buckland ?:-\)]

Hi Vadim,

For 2007 Office System products the Local Installation Source (LIS) can be precached to client machines.

Setup is run from the Local Installation Source as are feature changes. If the LIS is missing, damaged or ???, then the MS
Installer looks first to repair the LIS then installs from that point. The where do I look for the source is similar to adding a
driver or device to Windows, where you have the choice to look in additional places if the 'default' (original) installation point
isn't available.

The LIS isn't checked by Office when apps are run to see if it's intact. It's only checked when updating, repairing or installing,
so there will be cases (mainly individual users) where updates will come along and folks will need their CDs (or Network Points)
available again to repair the LIS (\MSOCache) folder that they may have deleted to 'save space'.

It's still a bit short of being complete, but you may find the MS Office 2007 Resource Kit to be helpful.
http://microsoft.com/office/ork

==============
Hi, All!

While configuring Office 2007 with OCT I ran across two statements in the
OCT's help that seem to contradict to each other.

On the "Additional network sources" page it says:
"Setup looks for servers in this list, in the order specified, if it is
installing a feature on demand or repairing Office and the original network
installation point is unavailable."

however on the "Set feature installation states" it says:

"Installed on First Use Setup leaves components for the feature and all its
child features in the local installation source until the user attempts to
use the feature for the first time, at which time the components are
installed."

I'm aware that LIS is created during the setup, and according to the ORK
"the local installation source is a required part of the design."
http://technet2.microsoft.com/Office/f/?en-us/library/8295626a-4570-4b7f-91e3-717fe6b81f961033.mspx

Questions:
When does setup actually use additional installation sources for installing
features on first use or repairing Office applications? Does this happen only
when LIS is missing?

How does setup search for the installation source whenever it needs to
install a feature on first use or repair an application? Is it using the
sequence LIS -> Original network installation point -> Additonal network
sources?

I'd like to get definite answers, because I can do guessing myself Thanks
for your time and attention to my questions.

--
Vadim Sterkin aka Vadikan
MVP Windows/Shell >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Vadim,

For 2007 Office System products the Local Installation Source (LIS) can be precached to client machines.

Setup is run from the Local Installation Source as are feature changes. If the LIS is missing, damaged or ???, then the MS
Installer looks first to repair the LIS then installs from that point. The where do I look for the source is similar to adding a
driver or device to Windows, where you have the choice to look in additional places if the 'default' (original) installation point
isn't available.

The LIS isn't checked by Office when apps are run to see if it's intact. It's only checked when updating, repairing or installing,
so there will be cases (mainly individual users) where updates will come along and folks will need their CDs (or Network Points)
available again to repair the LIS (\MSOCache) folder that they may have deleted to 'save space'.

It's still a bit short of being complete, but you may find the MS Office 2007 Resource Kit to be helpful.
http://microsoft.com/office/ork

==============
Hi, All!

While configuring Office 2007 with OCT I ran across two statements in the
OCT's help that seem to contradict to each other.

On the "Additional network sources" page it says:
"Setup looks for servers in this list, in the order specified, if it is
installing a feature on demand or repairing Office and the original network
installation point is unavailable."

however on the "Set feature installation states" it says:

"Installed on First Use Setup leaves components for the feature and all its
child features in the local installation source until the user attempts to
use the feature for the first time, at which time the components are
installed."

I'm aware that LIS is created during the setup, and according to the ORK
"the local installation source is a required part of the design."
http://technet2.microsoft.com/Office/f/?en-us/library/8295626a-4570-4b7f-91e3-717fe6b81f961033.mspx

Questions:
When does setup actually use additional installation sources for installing
features on first use or repairing Office applications? Does this happen only
when LIS is missing?

How does setup search for the installation source whenever it needs to
install a feature on first use or repair an application? Is it using the
sequence LIS -> Original network installation point -> Additonal network
sources?

I'd like to get definite answers, because I can do guessing myself Thanks
for your time and attention to my questions.

--
Vadim Sterkin aka Vadikan
MVP Windows/Shell >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Vadim,

For 2007 Office System products the Local Installation Source (LIS) can be precached to client machines.

Setup is run from the Local Installation Source as are feature changes. If the LIS is missing, damaged or ???, then the MS
Installer looks first to repair the LIS then installs from that point. The where do I look for the source is similar to adding a
driver or device to Windows, where you have the choice to look in additional places if the 'default' (original) installation point
isn't available.

The LIS isn't checked by Office when apps are run to see if it's intact. It's only checked when updating, repairing or installing,
so there will be cases (mainly individual users) where updates will come along and folks will need their CDs (or Network Points)
available again to repair the LIS (\MSOCache) folder that they may have deleted to 'save space'.

It's still a bit short of being complete, but you may find the MS Office 2007 Resource Kit to be helpful.
http://microsoft.com/office/ork

==============
Hi, All!

While configuring Office 2007 with OCT I ran across two statements in the
OCT's help that seem to contradict to each other.

On the "Additional network sources" page it says:
"Setup looks for servers in this list, in the order specified, if it is
installing a feature on demand or repairing Office and the original network
installation point is unavailable."

however on the "Set feature installation states" it says:

"Installed on First Use Setup leaves components for the feature and all its
child features in the local installation source until the user attempts to
use the feature for the first time, at which time the components are
installed."

I'm aware that LIS is created during the setup, and according to the ORK
"the local installation source is a required part of the design."
http://technet2.microsoft.com/Office/f/?en-us/library/8295626a-4570-4b7f-91e3-717fe6b81f961033.mspx

Questions:
When does setup actually use additional installation sources for installing
features on first use or repairing Office applications? Does this happen only
when LIS is missing?

How does setup search for the installation source whenever it needs to
install a feature on first use or repair an application? Is it using the
sequence LIS -> Original network installation point -> Additonal network
sources?

I'd like to get definite answers, because I can do guessing myself Thanks
for your time and attention to my questions.

--
Vadim Sterkin aka Vadikan
MVP Windows/Shell >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Bob Buckland ?:-\)]

Hi Vadim,

For 2007 Office System products the Local Installation Source (LIS) can be precached to client machines.

Setup is run from the Local Installation Source as are feature changes. If the LIS is missing, damaged or ???, then the MS
Installer looks first to repair the LIS then installs from that point. The where do I look for the source is similar to adding a
driver or device to Windows, where you have the choice to look in additional places if the 'default' (original) installation point
isn't available.

The LIS isn't checked by Office when apps are run to see if it's intact. It's only checked when updating, repairing or installing,
so there will be cases (mainly individual users) where updates will come along and folks will need their CDs (or Network Points)
available again to repair the LIS (\MSOCache) folder that they may have deleted to 'save space'.

It's still a bit short of being complete, but you may find the MS Office 2007 Resource Kit to be helpful.
http://microsoft.com/office/ork

==============
Hi, All!

While configuring Office 2007 with OCT I ran across two statements in the
OCT's help that seem to contradict to each other.

On the "Additional network sources" page it says:
"Setup looks for servers in this list, in the order specified, if it is
installing a feature on demand or repairing Office and the original network
installation point is unavailable."

however on the "Set feature installation states" it says:

"Installed on First Use Setup leaves components for the feature and all its
child features in the local installation source until the user attempts to
use the feature for the first time, at which time the components are
installed."

I'm aware that LIS is created during the setup, and according to the ORK
"the local installation source is a required part of the design."
http://technet2.microsoft.com/Office/f/?en-us/library/8295626a-4570-4b7f-91e3-717fe6b81f961033.mspx

Questions:
When does setup actually use additional installation sources for installing
features on first use or repairing Office applications? Does this happen only
when LIS is missing?

How does setup search for the installation source whenever it needs to
install a feature on first use or repair an application? Is it using the
sequence LIS -> Original network installation point -> Additonal network
sources?

I'd like to get definite answers, because I can do guessing myself Thanks
for your time and attention to my questions.

--
Vadim Sterkin aka Vadikan
MVP Windows/Shell >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Vadikan]

Hi Bob,

Thanks for your prompt answer!

If the LIS is missing, damaged or ???, then the MS
Installer looks first to repair the LIS then installs from that point. The where do I look for the source is similar to adding a
driver or device to Windows, where you have the choice to look in additional places if the 'default' (original) installation point
isn't available.

This is the missing piece of the puzzle I was looking for. I did check the
2007 resource kit, but couldn't find this particular information. In fact,
the OCT's help and 2007 resource kit share a lot of entries.

Thanks again for your input.

 

[Vadikan]

Hi Bob,

Thanks for your prompt answer!

If the LIS is missing, damaged or ???, then the MS
Installer looks first to repair the LIS then installs from that point. The where do I look for the source is similar to adding a
driver or device to Windows, where you have the choice to look in additional places if the 'default' (original) installation point
isn't available.

This is the missing piece of the puzzle I was looking for. I did check the
2007 resource kit, but couldn't find this particular information. In fact,
the OCT's help and 2007 resource kit share a lot of entries.

Thanks again for your input.

 

[Vadikan]

Hi Bob,

Thanks for your prompt answer!

If the LIS is missing, damaged or ???, then the MS
Installer looks first to repair the LIS then installs from that point. The where do I look for the source is similar to adding a
driver or device to Windows, where you have the choice to look in additional places if the 'default' (original) installation point
isn't available.

This is the missing piece of the puzzle I was looking for. I did check the
2007 resource kit, but couldn't find this particular information. In fact,
the OCT's help and 2007 resource kit share a lot of entries.

Thanks again for your input.

 

[Vadikan]

Hi Bob,

Thanks for your prompt answer!

If the LIS is missing, damaged or ???, then the MS
Installer looks first to repair the LIS then installs from that point. The where do I look for the source is similar to adding a
driver or device to Windows, where you have the choice to look in additional places if the 'default' (original) installation point
isn't available.

This is the missing piece of the puzzle I was looking for. I did check the
2007 resource kit, but couldn't find this particular information. In fact,
the OCT's help and 2007 resource kit share a lot of entries.

Thanks again for your input.