Office 2003 Deployment, Compressed CD Image or Administrative Installation Point

[ckunselman]

Looking at the advantages and disadvantages of using a local
installation source (compressed CD image) or an administrative
installation point to deploy Office 2003. I read in the Office 2003
Resource Kit that for roaming users (roaming profiles) an
administrative installation point was recommended vs. a compressed CD
image. Any idea as to why this is the preferred installation method
for roaming users?

Also, if MS Office 2003 is installed from a networked copy of the
compressed CD image, the local cached copy is deleted and the program
needs to install something on first use, what will occur? Will the
software failover to the network compressed CD image, or will it prompt
for a CD?

Chris

 

[neo [mvp outlook]]

My site went with a CD copied to network location. All installs are done by
calling the setup executable in order to generate the local installation
source. We have found that this allows for detect/repairs, add/remove of
components when there is no network connection, and/or patching by WSUS.

 

[neo [mvp outlook]]

My site went with a CD copied to network location. All installs are done by
calling the setup executable in order to generate the local installation
source. We have found that this allows for detect/repairs, add/remove of
components when there is no network connection, and/or patching by WSUS.

 

[neo [mvp outlook]]

My site went with a CD copied to network location. All installs are done by
calling the setup executable in order to generate the local installation
source. We have found that this allows for detect/repairs, add/remove of
components when there is no network connection, and/or patching by WSUS.

 

[neo [mvp outlook]]

My site went with a CD copied to network location. All installs are done by
calling the setup executable in order to generate the local installation
source. We have found that this allows for detect/repairs, add/remove of
components when there is no network connection, and/or patching by WSUS.

 

[neo [mvp outlook]]

My site went with a CD copied to network location. All installs are done by
calling the setup executable in order to generate the local installation
source. We have found that this allows for detect/repairs, add/remove of
components when there is no network connection, and/or patching by WSUS.

 

[neo [mvp outlook]]

My site went with a CD copied to network location. All installs are done by
calling the setup executable in order to generate the local installation
source. We have found that this allows for detect/repairs, add/remove of
components when there is no network connection, and/or patching by WSUS.

 

[neo [mvp outlook]]

My site went with a CD copied to network location. All installs are done by
calling the setup executable in order to generate the local installation
source. We have found that this allows for detect/repairs, add/remove of
components when there is no network connection, and/or patching by WSUS.

 

[neo [mvp outlook]]

My site went with a CD copied to network location. All installs are done by
calling the setup executable in order to generate the local installation
source. We have found that this allows for detect/repairs, add/remove of
components when there is no network connection, and/or patching by WSUS.

 

[Bob Buckland ?:-\)]

Hi Chris,

For Roaming Profile deployments the Local Installation Source (LIS/MSOCache) doesn't 'watch' things on a per user basis. The
\MSOCache is shared, when it's damaged it's damaged for any user connected to it, so roaming profiles don't play well against that
limitation, so using the Office Admin point is recommended.

For fail over, if the client PC is connected to the network with the original source the installer will look to that source to
repair a damaged installation/LIS. If there isn't a connection to the original install source the user should be prompted for the
source point/CD to complete a repair.

Note that a compressed CD image and a Local Installation Source (MSOCache) are not the same thing.
http://microsoft.com/office/ork/2003

==============
Looking at the advantages and disadvantages of using a local
installation source (compressed CD image) or an administrative
installation point to deploy Office 2003. I read in the Office 2003
Resource Kit that for roaming users (roaming profiles) an
administrative installation point was recommended vs. a compressed CD
image. Any idea as to why this is the preferred installation method
for roaming users?

Also, if MS Office 2003 is installed from a networked copy of the
compressed CD image, the local cached copy is deleted and the program
needs to install something on first use, what will occur? Will the
software failover to the network compressed CD image, or will it prompt
for a CD?

Chris>>

--
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

 

[Bob Buckland ?:-\)]

Hi Chris,

For Roaming Profile deployments the Local Installation Source (LIS/MSOCache) doesn't 'watch' things on a per user basis. The
\MSOCache is shared, when it's damaged it's damaged for any user connected to it, so roaming profiles don't play well against that
limitation, so using the Office Admin point is recommended.

For fail over, if the client PC is connected to the network with the original source the installer will look to that source to
repair a damaged installation/LIS. If there isn't a connection to the original install source the user should be prompted for the
source point/CD to complete a repair.

Note that a compressed CD image and a Local Installation Source (MSOCache) are not the same thing.
http://microsoft.com/office/ork/2003

==============
Looking at the advantages and disadvantages of using a local
installation source (compressed CD image) or an administrative
installation point to deploy Office 2003. I read in the Office 2003
Resource Kit that for roaming users (roaming profiles) an
administrative installation point was recommended vs. a compressed CD
image. Any idea as to why this is the preferred installation method
for roaming users?

Also, if MS Office 2003 is installed from a networked copy of the
compressed CD image, the local cached copy is deleted and the program
needs to install something on first use, what will occur? Will the
software failover to the network compressed CD image, or will it prompt
for a CD?

Chris>>

--
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

 

[Bob Buckland ?:-\)]

Hi Chris,

For Roaming Profile deployments the Local Installation Source (LIS/MSOCache) doesn't 'watch' things on a per user basis. The
\MSOCache is shared, when it's damaged it's damaged for any user connected to it, so roaming profiles don't play well against that
limitation, so using the Office Admin point is recommended.

For fail over, if the client PC is connected to the network with the original source the installer will look to that source to
repair a damaged installation/LIS. If there isn't a connection to the original install source the user should be prompted for the
source point/CD to complete a repair.

Note that a compressed CD image and a Local Installation Source (MSOCache) are not the same thing.
http://microsoft.com/office/ork/2003

==============
Looking at the advantages and disadvantages of using a local
installation source (compressed CD image) or an administrative
installation point to deploy Office 2003. I read in the Office 2003
Resource Kit that for roaming users (roaming profiles) an
administrative installation point was recommended vs. a compressed CD
image. Any idea as to why this is the preferred installation method
for roaming users?

Also, if MS Office 2003 is installed from a networked copy of the
compressed CD image, the local cached copy is deleted and the program
needs to install something on first use, what will occur? Will the
software failover to the network compressed CD image, or will it prompt
for a CD?

Chris>>

--
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

 

[Bob Buckland ?:-\)]

Hi Chris,

For Roaming Profile deployments the Local Installation Source (LIS/MSOCache) doesn't 'watch' things on a per user basis. The
\MSOCache is shared, when it's damaged it's damaged for any user connected to it, so roaming profiles don't play well against that
limitation, so using the Office Admin point is recommended.

For fail over, if the client PC is connected to the network with the original source the installer will look to that source to
repair a damaged installation/LIS. If there isn't a connection to the original install source the user should be prompted for the
source point/CD to complete a repair.

Note that a compressed CD image and a Local Installation Source (MSOCache) are not the same thing.
http://microsoft.com/office/ork/2003

==============
Looking at the advantages and disadvantages of using a local
installation source (compressed CD image) or an administrative
installation point to deploy Office 2003. I read in the Office 2003
Resource Kit that for roaming users (roaming profiles) an
administrative installation point was recommended vs. a compressed CD
image. Any idea as to why this is the preferred installation method
for roaming users?

Also, if MS Office 2003 is installed from a networked copy of the
compressed CD image, the local cached copy is deleted and the program
needs to install something on first use, what will occur? Will the
software failover to the network compressed CD image, or will it prompt
for a CD?

Chris>>

--
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

 

[Bob Buckland ?:-\)]

Hi Chris,

For Roaming Profile deployments the Local Installation Source (LIS/MSOCache) doesn't 'watch' things on a per user basis. The
\MSOCache is shared, when it's damaged it's damaged for any user connected to it, so roaming profiles don't play well against that
limitation, so using the Office Admin point is recommended.

For fail over, if the client PC is connected to the network with the original source the installer will look to that source to
repair a damaged installation/LIS. If there isn't a connection to the original install source the user should be prompted for the
source point/CD to complete a repair.

Note that a compressed CD image and a Local Installation Source (MSOCache) are not the same thing.
http://microsoft.com/office/ork/2003

==============
Looking at the advantages and disadvantages of using a local
installation source (compressed CD image) or an administrative
installation point to deploy Office 2003. I read in the Office 2003
Resource Kit that for roaming users (roaming profiles) an
administrative installation point was recommended vs. a compressed CD
image. Any idea as to why this is the preferred installation method
for roaming users?

Also, if MS Office 2003 is installed from a networked copy of the
compressed CD image, the local cached copy is deleted and the program
needs to install something on first use, what will occur? Will the
software failover to the network compressed CD image, or will it prompt
for a CD?

Chris>>

--
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

 

[Bob Buckland ?:-\)]

Hi Chris,

For Roaming Profile deployments the Local Installation Source (LIS/MSOCache) doesn't 'watch' things on a per user basis. The
\MSOCache is shared, when it's damaged it's damaged for any user connected to it, so roaming profiles don't play well against that
limitation, so using the Office Admin point is recommended.

For fail over, if the client PC is connected to the network with the original source the installer will look to that source to
repair a damaged installation/LIS. If there isn't a connection to the original install source the user should be prompted for the
source point/CD to complete a repair.

Note that a compressed CD image and a Local Installation Source (MSOCache) are not the same thing.
http://microsoft.com/office/ork/2003

==============
Looking at the advantages and disadvantages of using a local
installation source (compressed CD image) or an administrative
installation point to deploy Office 2003. I read in the Office 2003
Resource Kit that for roaming users (roaming profiles) an
administrative installation point was recommended vs. a compressed CD
image. Any idea as to why this is the preferred installation method
for roaming users?

Also, if MS Office 2003 is installed from a networked copy of the
compressed CD image, the local cached copy is deleted and the program
needs to install something on first use, what will occur? Will the
software failover to the network compressed CD image, or will it prompt
for a CD?

Chris>>

--
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

 

[Bob Buckland ?:-\)]

Hi Chris,

For Roaming Profile deployments the Local Installation Source (LIS/MSOCache) doesn't 'watch' things on a per user basis. The
\MSOCache is shared, when it's damaged it's damaged for any user connected to it, so roaming profiles don't play well against that
limitation, so using the Office Admin point is recommended.

For fail over, if the client PC is connected to the network with the original source the installer will look to that source to
repair a damaged installation/LIS. If there isn't a connection to the original install source the user should be prompted for the
source point/CD to complete a repair.

Note that a compressed CD image and a Local Installation Source (MSOCache) are not the same thing.
http://microsoft.com/office/ork/2003

==============
Looking at the advantages and disadvantages of using a local
installation source (compressed CD image) or an administrative
installation point to deploy Office 2003. I read in the Office 2003
Resource Kit that for roaming users (roaming profiles) an
administrative installation point was recommended vs. a compressed CD
image. Any idea as to why this is the preferred installation method
for roaming users?

Also, if MS Office 2003 is installed from a networked copy of the
compressed CD image, the local cached copy is deleted and the program
needs to install something on first use, what will occur? Will the
software failover to the network compressed CD image, or will it prompt
for a CD?

Chris>>

--
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

 

[Bob Buckland ?:-\)]

Hi Chris,

For Roaming Profile deployments the Local Installation Source (LIS/MSOCache) doesn't 'watch' things on a per user basis. The
\MSOCache is shared, when it's damaged it's damaged for any user connected to it, so roaming profiles don't play well against that
limitation, so using the Office Admin point is recommended.

For fail over, if the client PC is connected to the network with the original source the installer will look to that source to
repair a damaged installation/LIS. If there isn't a connection to the original install source the user should be prompted for the
source point/CD to complete a repair.

Note that a compressed CD image and a Local Installation Source (MSOCache) are not the same thing.
http://microsoft.com/office/ork/2003

==============
Looking at the advantages and disadvantages of using a local
installation source (compressed CD image) or an administrative
installation point to deploy Office 2003. I read in the Office 2003
Resource Kit that for roaming users (roaming profiles) an
administrative installation point was recommended vs. a compressed CD
image. Any idea as to why this is the preferred installation method
for roaming users?

Also, if MS Office 2003 is installed from a networked copy of the
compressed CD image, the local cached copy is deleted and the program
needs to install something on first use, what will occur? Will the
software failover to the network compressed CD image, or will it prompt
for a CD?

Chris>>

--
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