ms office

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

What is the easiest way to roll out office 2003? I know from going to
previous sites that sometimes there is an issue if it is installed from the
network, becuase if that server is then gone and a feature needs to be added
or something happens to office it causes an issue.
How can you avoid that? I know office 2003 has the cached install but even
if it is just office xp, why does that happen and how would that be rolled
out via gpo or from a network share just manually installing it and then
avoiding that issue?
 
Office 2003 Resource Kit
http://office.microsoft.com/en-us/FX011511471033.aspx

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

-------------------------------------------------------------------------------------------

:

| What is the easiest way to roll out office 2003? I know from going to
| previous sites that sometimes there is an issue if it is installed from the
| network, becuase if that server is then gone and a feature needs to be added
| or something happens to office it causes an issue.
| How can you avoid that? I know office 2003 has the cached install but even
| if it is just office xp, why does that happen and how would that be rolled
| out via gpo or from a network share just manually installing it and then
| avoiding that issue?
 
I realize that, I guess the big question is what is the issue when someone
has installed it from the network and then if you need to repair or if office
feels like it, then the installer kicks up and wants to point to the server
it was installed from.

How do you avoid that?
 
Frequently asked questions about the Local Install Source feature in Office 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;830168

Local Install Source (Msocache)
http://support.microsoft.com/kb/825933/

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

-------------------------------------------------------------------------------------------

:

| I realize that, I guess the big question is what is the issue when someone
| has installed it from the network and then if you need to repair or if office
| feels like it, then the installer kicks up and wants to point to the server
| it was installed from.
|
| How do you avoid that?
 
If and when you change the network share install location on your network,
you change the "installed from" location in the users registry via an AD
Group Policy change.

--

Star Fleet Admiral Q @ your Service!

http://www.google.com
Google is your "Friend"
 
THx, how do you fix this if the office version is like xp or something and
the server is already gone?

Now this is the issue even when you just sit at a desktop and run the
install for office from a shared folder?
 
One soulotion at least to new installs is to create a dfs share and install
from this share. Then you can change or add servers as you like and the
client will still belive that it is installing from the original server. We
are using this for all our MSI packages on about 17000 workstations
 
Thanks, that is a good idea. So basically if this issue occurs already, you
have no choice but to do a reinstall?
 
I dont think so.

Have you tried to put up a dns alias pointing the old servername to an
existing server with the officefiles in the right place?
 
Back
Top