Curtis,
Thanks so much! I have been trying to get this working
and asking questions for a week. You were correct in that
the error was casued by the "maximized" setting vs. the
basic. It is interesting that the default comes up as
maximized and that does not work. However - for you info
too, I had to actually delete the GPO, and re-create it to
get it to work. Once it was set as maximized, just
changing it back did not work either as I tried that
ealier. Also, I could not figure out how to find the
launch conditions table in the msi as you said but I did
not need to.
Once again, thanks for your help.
PEACE
Rory
>-----Original Message-----
>Check out the "LaunchConditions" table in the Office 2000
>MSI. It lists the error you're seeing, and the condition
>that must be met in order to prevent this error.
>
>If you're assinging Office 2000 to users, make sure to
>create the software package object using a "basic"
>interface. Selecting "Maximized" (on the "Deployment"
>tab) will cause this Launch Condition to fail, resulting
>in the message you're seeing.
>
>Hope this helps!
>
>Curtis Sawin
>>-----Original Message-----
>>Hello
>>
>>Has anyone had any luck using 2003 Server GPOs to inst
>>office 2000 (2000-pro clients)?
>>
>>We have been using GPO / msi to install Office 2000 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 (assign) office through user settings
>in
>>exactly the same way as always in 2000 server. We then
>>get this error when attempting to load from the client -
>>
>>"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 KB 227813 that deals with this error. Our
>>setup does not meet the listed casues, and the listed
>>solutions did not help as they dont apply to GPO / MSI
>>installs. I can not find another mention of this error
>>anywhere on any MS sites.
>>
>>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 was on a 2k pro box for first
>> test, and then placed on a server but same result.
>> - 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 and reinstalled
>everything
>>over and over but same problem, re-performed admin
>>install, re installed SR1 update, deleted and
reinstalled
>>share point, deleted and re-created new GPO, etc
>>
>>Any suggestions at all would be appreciated.
>>
>>Thank you to anyone who tries to help.
>>
>>Rory
>>
>>.
>>
>.
>
|
Similar Threads
