Office 2003 Install

[Peter Ellis]

Is running the Office 2003 install program the same as a network install?

I want to copy the files from a CD Rom to the server to install a full
version of Office 2003. I do not want to do a network install becuase if the
server ever comes down, I still want the users to be able to run office fully.

Is running setup from the server share the same as a network install and if
so, how do I get around it. I have the licenses required for each
workstation and simply want to avoid running the setup program from our few
Cds on each of the several dozed workstations.

 

[neo [mvp outlook]]

* Running setup.exe /a from the CD is where you are setting up an
Administrative Install Point (network install)

* Copying the CD to network unc/local drive is creating a compressed CD
image (When installing to desktop from this location by using setup, you
still get the local installation source [MSOCache] folder so clients can do
repairs, add/remove features, patch, .etc when the server is unavailable.)

IMHO, I always recommend the compressed CD method because it offers the most
flexibility.

 

[neo [mvp outlook]]

* Running setup.exe /a from the CD is where you are setting up an
Administrative Install Point (network install)

* Copying the CD to network unc/local drive is creating a compressed CD
image (When installing to desktop from this location by using setup, you
still get the local installation source [MSOCache] folder so clients can do
repairs, add/remove features, patch, .etc when the server is unavailable.)

IMHO, I always recommend the compressed CD method because it offers the most
flexibility.

 

[neo [mvp outlook]]

* Running setup.exe /a from the CD is where you are setting up an
Administrative Install Point (network install)

* Copying the CD to network unc/local drive is creating a compressed CD
image (When installing to desktop from this location by using setup, you
still get the local installation source [MSOCache] folder so clients can do
repairs, add/remove features, patch, .etc when the server is unavailable.)

IMHO, I always recommend the compressed CD method because it offers the most
flexibility.

 

[neo [mvp outlook]]

* Running setup.exe /a from the CD is where you are setting up an
Administrative Install Point (network install)

* Copying the CD to network unc/local drive is creating a compressed CD
image (When installing to desktop from this location by using setup, you
still get the local installation source [MSOCache] folder so clients can do
repairs, add/remove features, patch, .etc when the server is unavailable.)

IMHO, I always recommend the compressed CD method because it offers the most
flexibility.

 

[neo [mvp outlook]]

* Running setup.exe /a from the CD is where you are setting up an
Administrative Install Point (network install)

* Copying the CD to network unc/local drive is creating a compressed CD
image (When installing to desktop from this location by using setup, you
still get the local installation source [MSOCache] folder so clients can do
repairs, add/remove features, patch, .etc when the server is unavailable.)

IMHO, I always recommend the compressed CD method because it offers the most
flexibility.

 

[neo [mvp outlook]]

* Running setup.exe /a from the CD is where you are setting up an
Administrative Install Point (network install)

* Copying the CD to network unc/local drive is creating a compressed CD
image (When installing to desktop from this location by using setup, you
still get the local installation source [MSOCache] folder so clients can do
repairs, add/remove features, patch, .etc when the server is unavailable.)

IMHO, I always recommend the compressed CD method because it offers the most
flexibility.

 

[neo [mvp outlook]]

* Running setup.exe /a from the CD is where you are setting up an
Administrative Install Point (network install)

* Copying the CD to network unc/local drive is creating a compressed CD
image (When installing to desktop from this location by using setup, you
still get the local installation source [MSOCache] folder so clients can do
repairs, add/remove features, patch, .etc when the server is unavailable.)

IMHO, I always recommend the compressed CD method because it offers the most
flexibility.