Change Administrative Install Path

[Gerry Hickman]

Hi,

To answer the other question about product GUID mismatches - YES, this
is important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Gerry Hickman]

Hi,

To answer the other question about product GUID mismatches - YES, this
is important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Gerry Hickman]

Hi,

To answer the other question about product GUID mismatches - YES, this
is important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Gerry Hickman]

Hi,

To answer the other question about product GUID mismatches - YES, this
is important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Gerry Hickman]

Hi,

To answer the other question about product GUID mismatches - YES, this
is important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Gerry Hickman]

Hi,

To answer the other question about product GUID mismatches - YES, this
is important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Philippe Desmarais]

How can I find the versions related to the produit GUID?

Any website, documentation??

Hi,

To answer the other question about product GUID mismatches - YES, this is
important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Philippe Desmarais]

How can I find the versions related to the produit GUID?

Any website, documentation??

Hi,

To answer the other question about product GUID mismatches - YES, this is
important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Philippe Desmarais]

How can I find the versions related to the produit GUID?

Any website, documentation??

Hi,

To answer the other question about product GUID mismatches - YES, this is
important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Philippe Desmarais]

How can I find the versions related to the produit GUID?

Any website, documentation??

Hi,

To answer the other question about product GUID mismatches - YES, this is
important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Philippe Desmarais]

How can I find the versions related to the produit GUID?

Any website, documentation??

Hi,

To answer the other question about product GUID mismatches - YES, this is
important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Philippe Desmarais]

How can I find the versions related to the produit GUID?

Any website, documentation??

Hi,

To answer the other question about product GUID mismatches - YES, this is
important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Philippe Desmarais]

How can I find the versions related to the produit GUID?

Any website, documentation??

Hi,

To answer the other question about product GUID mismatches - YES, this is
important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Philippe Desmarais]

How can I find the versions related to the produit GUID?

Any website, documentation??

Hi,

To answer the other question about product GUID mismatches - YES, this is
important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Philippe Desmarais]

How can I find the versions related to the produit GUID?

Any website, documentation??

Hi,

To answer the other question about product GUID mismatches - YES, this is
important! It's essential that all AIPs match the installations being
patched/upgraded/SPd etc.

In other words, if you've installed Office Pro with SP1 on 500 machines,
then installed Office Premium SP3 on 100 machines, you cannot just
suddenly set all their install paths to Office Pro SP3. Everything must
match.

 

[Gerry Hickman]

Hi Philippe,

How can I find the versions related to the produit GUID?

Is this the only problem now, did you solve everything else?

I'm not sure of the proper way to check product GUIDs, but I have done
it in the past using a combination of MSI log files and the registry.
e.g. here's my home computer registry:

HKEY_CLASSES_ROOT\Installer\Products\904000001E872D116BF00006799C897E

Under this key it says:

PackageCode:
E7E5BD6FEA6EC0847A5FA062C0E4CF8D

PruductName:
Microsoft Office 2000 SR-1 Premium

Now let's look at HKLM:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{00000409-78E1-11D2-B60F-006097C998E7}

InstallSource:
D:\Office\o2kadm\

UninstallString:
MsiExec.exe /I{00000409-78E1-11D2-B60F-006097C998E7}

So with this information we can quickly check each machine to see which
product is installed.

All you need to do is make sure there's a valid installation source for
each incarnation that exists on the clients.

If it gets too complicated, just create a brand new AIP with all latest
patches and start blasting it out overnight 50 machines at a time.

 

[Gerry Hickman]

Hi Philippe,

How can I find the versions related to the produit GUID?

Is this the only problem now, did you solve everything else?

I'm not sure of the proper way to check product GUIDs, but I have done
it in the past using a combination of MSI log files and the registry.
e.g. here's my home computer registry:

HKEY_CLASSES_ROOT\Installer\Products\904000001E872D116BF00006799C897E

Under this key it says:

PackageCode:
E7E5BD6FEA6EC0847A5FA062C0E4CF8D

PruductName:
Microsoft Office 2000 SR-1 Premium

Now let's look at HKLM:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{00000409-78E1-11D2-B60F-006097C998E7}

InstallSource:
D:\Office\o2kadm\

UninstallString:
MsiExec.exe /I{00000409-78E1-11D2-B60F-006097C998E7}

So with this information we can quickly check each machine to see which
product is installed.

All you need to do is make sure there's a valid installation source for
each incarnation that exists on the clients.

If it gets too complicated, just create a brand new AIP with all latest
patches and start blasting it out overnight 50 machines at a time.

 

[Gerry Hickman]

Hi Philippe,

How can I find the versions related to the produit GUID?

Is this the only problem now, did you solve everything else?

I'm not sure of the proper way to check product GUIDs, but I have done
it in the past using a combination of MSI log files and the registry.
e.g. here's my home computer registry:

HKEY_CLASSES_ROOT\Installer\Products\904000001E872D116BF00006799C897E

Under this key it says:

PackageCode:
E7E5BD6FEA6EC0847A5FA062C0E4CF8D

PruductName:
Microsoft Office 2000 SR-1 Premium

Now let's look at HKLM:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{00000409-78E1-11D2-B60F-006097C998E7}

InstallSource:
D:\Office\o2kadm\

UninstallString:
MsiExec.exe /I{00000409-78E1-11D2-B60F-006097C998E7}

So with this information we can quickly check each machine to see which
product is installed.

All you need to do is make sure there's a valid installation source for
each incarnation that exists on the clients.

If it gets too complicated, just create a brand new AIP with all latest
patches and start blasting it out overnight 50 machines at a time.

 

[Gerry Hickman]

Hi Philippe,

How can I find the versions related to the produit GUID?

Is this the only problem now, did you solve everything else?

I'm not sure of the proper way to check product GUIDs, but I have done
it in the past using a combination of MSI log files and the registry.
e.g. here's my home computer registry:

HKEY_CLASSES_ROOT\Installer\Products\904000001E872D116BF00006799C897E

Under this key it says:

PackageCode:
E7E5BD6FEA6EC0847A5FA062C0E4CF8D

PruductName:
Microsoft Office 2000 SR-1 Premium

Now let's look at HKLM:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{00000409-78E1-11D2-B60F-006097C998E7}

InstallSource:
D:\Office\o2kadm\

UninstallString:
MsiExec.exe /I{00000409-78E1-11D2-B60F-006097C998E7}

So with this information we can quickly check each machine to see which
product is installed.

All you need to do is make sure there's a valid installation source for
each incarnation that exists on the clients.

If it gets too complicated, just create a brand new AIP with all latest
patches and start blasting it out overnight 50 machines at a time.

 

[Gerry Hickman]

Hi Philippe,

How can I find the versions related to the produit GUID?

Is this the only problem now, did you solve everything else?

I'm not sure of the proper way to check product GUIDs, but I have done
it in the past using a combination of MSI log files and the registry.
e.g. here's my home computer registry:

HKEY_CLASSES_ROOT\Installer\Products\904000001E872D116BF00006799C897E

Under this key it says:

PackageCode:
E7E5BD6FEA6EC0847A5FA062C0E4CF8D

PruductName:
Microsoft Office 2000 SR-1 Premium

Now let's look at HKLM:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{00000409-78E1-11D2-B60F-006097C998E7}

InstallSource:
D:\Office\o2kadm\

UninstallString:
MsiExec.exe /I{00000409-78E1-11D2-B60F-006097C998E7}

So with this information we can quickly check each machine to see which
product is installed.

All you need to do is make sure there's a valid installation source for
each incarnation that exists on the clients.

If it gets too complicated, just create a brand new AIP with all latest
patches and start blasting it out overnight 50 machines at a time.