Office 2000 - Install window keeps poping up

[TM]

I have a windows 2000 machine with service pack 4 and I
just installed office 2000, I performed a full
installation (run all from the hard drive) and then
rebooted the PC, under the administrator login everything
works fine, word starts up, I can open files...no
problem. However a new user on the domain logged into it
(this person is a domain admin) but for some reason she
keeps getting the window that states (ready to install
office 2000 components....) this happens every time, does
anyone know how I can stop this from happening its really
annoying...

Thanks

 

[mpm]

HI
did you get any answer? could you pass it to me please?

 

[mpm]

HI
did you get any answer? could you pass it to me please?

 

[mpm]

HI
did you get any answer? could you pass it to me please?

 

[mpm]

HI
did you get any answer? could you pass it to me please?

 

[mpm]

HI
did you get any answer? could you pass it to me please?

 

[mpm]

HI
did you get any answer? could you pass it to me please?

 

[Carlos]

I would try installing office logged in as the user with
the install problem. Let me know.

 

[Carlos]

I would try installing office logged in as the user with
the install problem. Let me know.

 

[Carlos]

I would try installing office logged in as the user with
the install problem. Let me know.

 

[Carlos]

I would try installing office logged in as the user with
the install problem. Let me know.

 

[Carlos]

I would try installing office logged in as the user with
the install problem. Let me know.

 

[Carlos]

I would try installing office logged in as the user with
the install problem. Let me know.

 

[RickV]

I have the same problem. The only solution that has
worked for me so far is to elevate the user to local
administrator, log in as that user and run an Office
application (Word). When prompted, insert the cd and let
it do its thing. When done, reduce the user back to
normal status (restricted or power user) and log back in.

This works for me for people with dedicated computers, but
it's not practical in all situations since I have a lot of
machines on my network that are shared among many users.
Each time a user migrates to a different computer the
problem re-appears on that new machine.

I'm still waiting to find that more practical solution.

 

[RickV]

I have the same problem. The only solution that has
worked for me so far is to elevate the user to local
administrator, log in as that user and run an Office
application (Word). When prompted, insert the cd and let
it do its thing. When done, reduce the user back to
normal status (restricted or power user) and log back in.

This works for me for people with dedicated computers, but
it's not practical in all situations since I have a lot of
machines on my network that are shared among many users.
Each time a user migrates to a different computer the
problem re-appears on that new machine.

I'm still waiting to find that more practical solution.

 

[RickV]

I have the same problem. The only solution that has
worked for me so far is to elevate the user to local
administrator, log in as that user and run an Office
application (Word). When prompted, insert the cd and let
it do its thing. When done, reduce the user back to
normal status (restricted or power user) and log back in.

This works for me for people with dedicated computers, but
it's not practical in all situations since I have a lot of
machines on my network that are shared among many users.
Each time a user migrates to a different computer the
problem re-appears on that new machine.

I'm still waiting to find that more practical solution.

 

[RickV]

I have the same problem. The only solution that has
worked for me so far is to elevate the user to local
administrator, log in as that user and run an Office
application (Word). When prompted, insert the cd and let
it do its thing. When done, reduce the user back to
normal status (restricted or power user) and log back in.

This works for me for people with dedicated computers, but
it's not practical in all situations since I have a lot of
machines on my network that are shared among many users.
Each time a user migrates to a different computer the
problem re-appears on that new machine.

I'm still waiting to find that more practical solution.

 

[RickV]

I have the same problem. The only solution that has
worked for me so far is to elevate the user to local
administrator, log in as that user and run an Office
application (Word). When prompted, insert the cd and let
it do its thing. When done, reduce the user back to
normal status (restricted or power user) and log back in.

This works for me for people with dedicated computers, but
it's not practical in all situations since I have a lot of
machines on my network that are shared among many users.
Each time a user migrates to a different computer the
problem re-appears on that new machine.

I'm still waiting to find that more practical solution.

 

[RickV]

I have the same problem. The only solution that has
worked for me so far is to elevate the user to local
administrator, log in as that user and run an Office
application (Word). When prompted, insert the cd and let
it do its thing. When done, reduce the user back to
normal status (restricted or power user) and log back in.

This works for me for people with dedicated computers, but
it's not practical in all situations since I have a lot of
machines on my network that are shared among many users.
Each time a user migrates to a different computer the
problem re-appears on that new machine.

I'm still waiting to find that more practical solution.

 

[RickV]

I have the same problem. The only solution that has
worked for me so far is to elevate the user to local
administrator, log in as that user and run an Office
application (Word). When prompted, insert the cd and let
it do its thing. When done, reduce the user back to
normal status (restricted or power user) and log back in.

This works for me for people with dedicated computers, but
it's not practical in all situations since I have a lot of
machines on my network that are shared among many users.
Each time a user migrates to a different computer the
problem re-appears on that new machine.

I'm still waiting to find that more practical solution.