Moving an Office 2003 Admin Install Point - what will break?

[neo [mvp outlook]]

I haven't forgot about you. My brain is getting stuck about the GPO where
once it is removed or revised that it could trigger an uninstall/reinstall
of Office.

Neo,

My AIP is more like your example number 2. We installed from a plan old
share using the .msi file. We're doing all our updates to client machines
by
refreshing the installation from that AIP also.

My question at this point is how to make the clients think the 'original'
AIP is really the new one I'm moving things to. I've thought I could just
edit the Install registry key on each client - that may fix it. Or I could
simply re-install the whole install from the new server.

I'm interested in your thoughts.

 

[neo [mvp outlook]]

I haven't forgot about you. My brain is getting stuck about the GPO where
once it is removed or revised that it could trigger an uninstall/reinstall
of Office.

Neo,

My AIP is more like your example number 2. We installed from a plan old
share using the .msi file. We're doing all our updates to client machines
by
refreshing the installation from that AIP also.

My question at this point is how to make the clients think the 'original'
AIP is really the new one I'm moving things to. I've thought I could just
edit the Install registry key on each client - that may fix it. Or I could
simply re-install the whole install from the new server.

I'm interested in your thoughts.

 

[neo [mvp outlook]]

I haven't forgot about you. My brain is getting stuck about the GPO where
once it is removed or revised that it could trigger an uninstall/reinstall
of Office.

Neo,

My AIP is more like your example number 2. We installed from a plan old
share using the .msi file. We're doing all our updates to client machines
by
refreshing the installation from that AIP also.

My question at this point is how to make the clients think the 'original'
AIP is really the new one I'm moving things to. I've thought I could just
edit the Install registry key on each client - that may fix it. Or I could
simply re-install the whole install from the new server.

I'm interested in your thoughts.

 

[neo [mvp outlook]]

I haven't forgot about you. My brain is getting stuck about the GPO where
once it is removed or revised that it could trigger an uninstall/reinstall
of Office.

Neo,

My AIP is more like your example number 2. We installed from a plan old
share using the .msi file. We're doing all our updates to client machines
by
refreshing the installation from that AIP also.

My question at this point is how to make the clients think the 'original'
AIP is really the new one I'm moving things to. I've thought I could just
edit the Install registry key on each client - that may fix it. Or I could
simply re-install the whole install from the new server.

I'm interested in your thoughts.

 

[neo [mvp outlook]]

I haven't forgot about you. My brain is getting stuck about the GPO where
once it is removed or revised that it could trigger an uninstall/reinstall
of Office.

Neo,

My AIP is more like your example number 2. We installed from a plan old
share using the .msi file. We're doing all our updates to client machines
by
refreshing the installation from that AIP also.

My question at this point is how to make the clients think the 'original'
AIP is really the new one I'm moving things to. I've thought I could just
edit the Install registry key on each client - that may fix it. Or I could
simply re-install the whole install from the new server.

I'm interested in your thoughts.

 

[neo [mvp outlook]]

I haven't forgot about you. My brain is getting stuck about the GPO where
once it is removed or revised that it could trigger an uninstall/reinstall
of Office.

Neo,

My AIP is more like your example number 2. We installed from a plan old
share using the .msi file. We're doing all our updates to client machines
by
refreshing the installation from that AIP also.

My question at this point is how to make the clients think the 'original'
AIP is really the new one I'm moving things to. I've thought I could just
edit the Install registry key on each client - that may fix it. Or I could
simply re-install the whole install from the new server.

I'm interested in your thoughts.

 

[neo [mvp outlook]]

I haven't forgot about you. My brain is getting stuck about the GPO where
once it is removed or revised that it could trigger an uninstall/reinstall
of Office.

Neo,

My AIP is more like your example number 2. We installed from a plan old
share using the .msi file. We're doing all our updates to client machines
by
refreshing the installation from that AIP also.

My question at this point is how to make the clients think the 'original'
AIP is really the new one I'm moving things to. I've thought I could just
edit the Install registry key on each client - that may fix it. Or I could
simply re-install the whole install from the new server.

I'm interested in your thoughts.

 

[neo [mvp outlook]]

I haven't forgot about you. My brain is getting stuck about the GPO where
once it is removed or revised that it could trigger an uninstall/reinstall
of Office.

Neo,

My AIP is more like your example number 2. We installed from a plan old
share using the .msi file. We're doing all our updates to client machines
by
refreshing the installation from that AIP also.

My question at this point is how to make the clients think the 'original'
AIP is really the new one I'm moving things to. I've thought I could just
edit the Install registry key on each client - that may fix it. Or I could
simply re-install the whole install from the new server.

I'm interested in your thoughts.

 

[Sandy Wood]

I believe I've found a workable solution for my dilemma. If I simple
reinstall Office 2003 from the new server, over the existing Office 2003
installation, it populates the SourceList on the client with the new source.
Not elegant, but it will do the trick.

 

[Sandy Wood]

I believe I've found a workable solution for my dilemma. If I simple
reinstall Office 2003 from the new server, over the existing Office 2003
installation, it populates the SourceList on the client with the new source.
Not elegant, but it will do the trick.

 

[Sandy Wood]

I believe I've found a workable solution for my dilemma. If I simple
reinstall Office 2003 from the new server, over the existing Office 2003
installation, it populates the SourceList on the client with the new source.
Not elegant, but it will do the trick.

 

[Sandy Wood]

I believe I've found a workable solution for my dilemma. If I simple
reinstall Office 2003 from the new server, over the existing Office 2003
installation, it populates the SourceList on the client with the new source.
Not elegant, but it will do the trick.

 

[Sandy Wood]

I believe I've found a workable solution for my dilemma. If I simple
reinstall Office 2003 from the new server, over the existing Office 2003
installation, it populates the SourceList on the client with the new source.
Not elegant, but it will do the trick.

 

[Sandy Wood]

I believe I've found a workable solution for my dilemma. If I simple
reinstall Office 2003 from the new server, over the existing Office 2003
installation, it populates the SourceList on the client with the new source.
Not elegant, but it will do the trick.

 

[Sandy Wood]

I believe I've found a workable solution for my dilemma. If I simple
reinstall Office 2003 from the new server, over the existing Office 2003
installation, it populates the SourceList on the client with the new source.
Not elegant, but it will do the trick.

 

[Sandy Wood]

I believe I've found a workable solution for my dilemma. If I simple
reinstall Office 2003 from the new server, over the existing Office 2003
installation, it populates the SourceList on the client with the new source.
Not elegant, but it will do the trick.

 

[Sandy Wood]

I believe I've found a workable solution for my dilemma. If I simple
reinstall Office 2003 from the new server, over the existing Office 2003
installation, it populates the SourceList on the client with the new source.
Not elegant, but it will do the trick.