help w / office msi / GPO

[Rory]

Hello

Has anyone had any luck using 2003 server GPOs to inst
office on 2000 pro clients?

We have been using GPO / msi to install Office and to put
out SPs to 2000 clients from 2000 servers for a while.

This week we tried testing from 2003 Server to 2000
clients and had this problem:

First we put out office through user settings in the same
way as always in 2000 server and we get this
error -

"Ms office 2000 has been advertised on your computer by
the system administrator. To install MS office 2000, run
setup with the /q or /qb command-line option. Contact
your sys admin for more info."

Then we found the KB article 227813 that deals with this
problem. However, our setup does not meet the criteria
for the listed casues and the listed solutions did not
resolve the problem.

The causes listed on 227813 say this:

you are running 2k, AND you are logged in as non-admin,
AND you also either ran the command setup / jm, or you
applied the "AlwaysInstallElelvated Policy"

Yes we are running 2k and yes we are using non-admin
accounts (why would you be applying office only to admin
accounts)

However we did NOT run a /jm command and we did not set
the "AlwaysInstallElelvated Policy" In fact I never heard
of it.

So the casues listed on KB 227813 do not really apply to
our setup.

Next the solutions on KB 227813 also did not help.

It says to run setup with the /q, or /qb swithes to
resolve this, but that does not work either. (tried /qb)

Does anyone have an idea why our sftw GPOs
are working in 2003 to inst office to 2k clients


HERE IS MORE SETUP AND BACKGROUND INFO FOR ABOVE PROBLEM

- Server is 2003.
- client is 2000
- Administrative install of Office was installed to a
share with the setup.exe /a command (like it has always
been done w / 2k servers)
- Office Share point is on a 2k pro box
- IN GPO, we used the UNC path to data1 msi (not browse)
- Office share point admin inst was updated to SR1/a
- Would have then been updated with SP 3 if it had worked
- Tried over and over, deleted everything , reinstalled,
re-performed admin install, re installed SR1 update,
share point, deleted and created new GPO etc

ANY FOLKS OUT THERE HAVE ANY INFO / FIXS, GUESSES OR BEST
WISHES ?

Thank you to anyone who tries to help.

Rory

 

[Rory]

Hi Cary,

I will try it on a server as you suggested. I never did
it w/ the share on a pro box either but I thought it
should work as this is only our test lab network of 1
server and 2 clients. Since there was only one client
logged in, I did not think the 10 connetion limit would
matter.

I am not familiar with the GPOTOOL and/or GPResult tools,
but if putting the share on a server does not work, I will
look into them.

THANK YOU!

Rory

 

[Cary Shultz]

-----Original Message-----
Hi Cary,

I will try it on a server as you suggested. I never did
it w/ the share on a pro box either but I thought it
should work as this is only our test lab network of 1
server and 2 clients. Since there was only one client
logged in, I did not think the 10 connetion limit would
matter.

I am not familiar with the GPOTOOL and/or GPResult tools,
but if putting the share on a server does not work, I will
look into them.

THANK YOU!

Rory
.

You are welcome...

 

[Rory]

To Carry or anyone else who read this post. The error
indicated in the original thread was resolved by selecting
the basic instead of maximized option in the advanced
deployment options in the GPO. Interestingly, the default
in 2003 comes up as maximized which DOES NOT work for
office /data1.msi (thats how it comes up in my 2003
installation if you just choose assigned instead of going
into advanced)

Also, once GPO is set as maximized you must delete it a re-
create is as basic. Just changing it back did not help.

Thanks again for your help Carry