Office installs over and over

[pctom]

I got same problem on win2k pro machine with office xp sbe. deleting the
user doesn't fix the problem for the user now does it! how about a real fix
so the user can be able use office on the machine? amazing how every other
product works fine!

 

[pctom]

I got same problem on win2k pro machine with office xp sbe. deleting the
user doesn't fix the problem for the user now does it! how about a real fix
so the user can be able use office on the machine? amazing how every other
product works fine!

 

[pctom]

I got same problem on win2k pro machine with office xp sbe. deleting the
user doesn't fix the problem for the user now does it! how about a real fix
so the user can be able use office on the machine? amazing how every other
product works fine!

 

[pctom]

I got same problem on win2k pro machine with office xp sbe. deleting the
user doesn't fix the problem for the user now does it! how about a real fix
so the user can be able use office on the machine? amazing how every other
product works fine!

 

[pctom]

I got same problem on win2k pro machine with office xp sbe. deleting the
user doesn't fix the problem for the user now does it! how about a real fix
so the user can be able use office on the machine? amazing how every other
product works fine!

 

[neo [mvp outlook]]

Unfortunately I cannot duplicate the problem and when it does surface it is
because a registry key is not being created successfully. So w/out really
knowing how Office was deployed to these machines and what type of extra
setup was done, it is nearly impossible to say how to fix.

Outside of that, because you guys say blowing the user profile away doesn't
work. It sounds like the key that it needs to work with is in the HKLM
section. The Users group only has read rights to this section. So
escalating the user to Admin (or possibly turning on the always install with
elevated rights for windows installer in gp) would permit this to happen.

 

[neo [mvp outlook]]

Unfortunately I cannot duplicate the problem and when it does surface it is
because a registry key is not being created successfully. So w/out really
knowing how Office was deployed to these machines and what type of extra
setup was done, it is nearly impossible to say how to fix.

Outside of that, because you guys say blowing the user profile away doesn't
work. It sounds like the key that it needs to work with is in the HKLM
section. The Users group only has read rights to this section. So
escalating the user to Admin (or possibly turning on the always install with
elevated rights for windows installer in gp) would permit this to happen.

 

[neo [mvp outlook]]

Unfortunately I cannot duplicate the problem and when it does surface it is
because a registry key is not being created successfully. So w/out really
knowing how Office was deployed to these machines and what type of extra
setup was done, it is nearly impossible to say how to fix.

Outside of that, because you guys say blowing the user profile away doesn't
work. It sounds like the key that it needs to work with is in the HKLM
section. The Users group only has read rights to this section. So
escalating the user to Admin (or possibly turning on the always install with
elevated rights for windows installer in gp) would permit this to happen.

 

[neo [mvp outlook]]

Unfortunately I cannot duplicate the problem and when it does surface it is
because a registry key is not being created successfully. So w/out really
knowing how Office was deployed to these machines and what type of extra
setup was done, it is nearly impossible to say how to fix.

Outside of that, because you guys say blowing the user profile away doesn't
work. It sounds like the key that it needs to work with is in the HKLM
section. The Users group only has read rights to this section. So
escalating the user to Admin (or possibly turning on the always install with
elevated rights for windows installer in gp) would permit this to happen.

 

[neo [mvp outlook]]

Unfortunately I cannot duplicate the problem and when it does surface it is
because a registry key is not being created successfully. So w/out really
knowing how Office was deployed to these machines and what type of extra
setup was done, it is nearly impossible to say how to fix.

Outside of that, because you guys say blowing the user profile away doesn't
work. It sounds like the key that it needs to work with is in the HKLM
section. The Users group only has read rights to this section. So
escalating the user to Admin (or possibly turning on the always install with
elevated rights for windows installer in gp) would permit this to happen.

 

[neo [mvp outlook]]

Unfortunately I cannot duplicate the problem and when it does surface it is
because a registry key is not being created successfully. So w/out really
knowing how Office was deployed to these machines and what type of extra
setup was done, it is nearly impossible to say how to fix.

Outside of that, because you guys say blowing the user profile away doesn't
work. It sounds like the key that it needs to work with is in the HKLM
section. The Users group only has read rights to this section. So
escalating the user to Admin (or possibly turning on the always install with
elevated rights for windows installer in gp) would permit this to happen.

 

[neo [mvp outlook]]

Unfortunately I cannot duplicate the problem and when it does surface it is
because a registry key is not being created successfully. So w/out really
knowing how Office was deployed to these machines and what type of extra
setup was done, it is nearly impossible to say how to fix.

Outside of that, because you guys say blowing the user profile away doesn't
work. It sounds like the key that it needs to work with is in the HKLM
section. The Users group only has read rights to this section. So
escalating the user to Admin (or possibly turning on the always install with
elevated rights for windows installer in gp) would permit this to happen.

 

[neo [mvp outlook]]

Unfortunately I cannot duplicate the problem and when it does surface it is
because a registry key is not being created successfully. So w/out really
knowing how Office was deployed to these machines and what type of extra
setup was done, it is nearly impossible to say how to fix.

Outside of that, because you guys say blowing the user profile away doesn't
work. It sounds like the key that it needs to work with is in the HKLM
section. The Users group only has read rights to this section. So
escalating the user to Admin (or possibly turning on the always install with
elevated rights for windows installer in gp) would permit this to happen.