Change Administrative Install Path

P

Phil Desmarais

Also in my Verbose Log file for the installation of

echo Installing Office 2003 Post SP1
msiexec /update "c:\MainSp1op.msp" /qn /l*v c:\wordv4.txt DISABLESRCPROMPT=1
LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS

echo ErrorLevel is %ErrorLevel%


I get this error a lot!
Return error 1603

DEBUG: Error 2746: Transform 15TTo15U invalid for package
C:\WINDOWS\Installer\2e303314.msi. Expected product
{91CA0409-6000-11D3-8CFE-0150048383C9}, found product
{90120409-6000-11D3-8CFE-0150048383C9}.

What is the difference between the 2 product?
 
P

Phil Desmarais

Also in my Verbose Log file for the installation of

echo Installing Office 2003 Post SP1
msiexec /update "c:\MainSp1op.msp" /qn /l*v c:\wordv4.txt DISABLESRCPROMPT=1
LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS

echo ErrorLevel is %ErrorLevel%


I get this error a lot!
Return error 1603

DEBUG: Error 2746: Transform 15TTo15U invalid for package
C:\WINDOWS\Installer\2e303314.msi. Expected product
{91CA0409-6000-11D3-8CFE-0150048383C9}, found product
{90120409-6000-11D3-8CFE-0150048383C9}.

What is the difference between the 2 product?
 
P

Phil Desmarais

Also in my Verbose Log file for the installation of

echo Installing Office 2003 Post SP1
msiexec /update "c:\MainSp1op.msp" /qn /l*v c:\wordv4.txt DISABLESRCPROMPT=1
LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS

echo ErrorLevel is %ErrorLevel%


I get this error a lot!
Return error 1603

DEBUG: Error 2746: Transform 15TTo15U invalid for package
C:\WINDOWS\Installer\2e303314.msi. Expected product
{91CA0409-6000-11D3-8CFE-0150048383C9}, found product
{90120409-6000-11D3-8CFE-0150048383C9}.

What is the difference between the 2 product?
 
P

Phil Desmarais

Also in my Verbose Log file for the installation of

echo Installing Office 2003 Post SP1
msiexec /update "c:\MainSp1op.msp" /qn /l*v c:\wordv4.txt DISABLESRCPROMPT=1
LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS

echo ErrorLevel is %ErrorLevel%


I get this error a lot!
Return error 1603

DEBUG: Error 2746: Transform 15TTo15U invalid for package
C:\WINDOWS\Installer\2e303314.msi. Expected product
{91CA0409-6000-11D3-8CFE-0150048383C9}, found product
{90120409-6000-11D3-8CFE-0150048383C9}.

What is the difference between the 2 product?
 
P

Phil Desmarais

Also in my Verbose Log file for the installation of

echo Installing Office 2003 Post SP1
msiexec /update "c:\MainSp1op.msp" /qn /l*v c:\wordv4.txt DISABLESRCPROMPT=1
LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS

echo ErrorLevel is %ErrorLevel%


I get this error a lot!
Return error 1603

DEBUG: Error 2746: Transform 15TTo15U invalid for package
C:\WINDOWS\Installer\2e303314.msi. Expected product
{91CA0409-6000-11D3-8CFE-0150048383C9}, found product
{90120409-6000-11D3-8CFE-0150048383C9}.

What is the difference between the 2 product?
 
P

Phil Desmarais

Also in my Verbose Log file for the installation of

echo Installing Office 2003 Post SP1
msiexec /update "c:\MainSp1op.msp" /qn /l*v c:\wordv4.txt DISABLESRCPROMPT=1
LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS

echo ErrorLevel is %ErrorLevel%


I get this error a lot!
Return error 1603

DEBUG: Error 2746: Transform 15TTo15U invalid for package
C:\WINDOWS\Installer\2e303314.msi. Expected product
{91CA0409-6000-11D3-8CFE-0150048383C9}, found product
{90120409-6000-11D3-8CFE-0150048383C9}.

What is the difference between the 2 product?
 
P

Phil Desmarais

Also in my Verbose Log file for the installation of

echo Installing Office 2003 Post SP1
msiexec /update "c:\MainSp1op.msp" /qn /l*v c:\wordv4.txt DISABLESRCPROMPT=1
LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS

echo ErrorLevel is %ErrorLevel%


I get this error a lot!
Return error 1603

DEBUG: Error 2746: Transform 15TTo15U invalid for package
C:\WINDOWS\Installer\2e303314.msi. Expected product
{91CA0409-6000-11D3-8CFE-0150048383C9}, found product
{90120409-6000-11D3-8CFE-0150048383C9}.

What is the difference between the 2 product?
 
P

Phil Desmarais

Also in my Verbose Log file for the installation of

echo Installing Office 2003 Post SP1
msiexec /update "c:\MainSp1op.msp" /qn /l*v c:\wordv4.txt DISABLESRCPROMPT=1
LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS

echo ErrorLevel is %ErrorLevel%


I get this error a lot!
Return error 1603

DEBUG: Error 2746: Transform 15TTo15U invalid for package
C:\WINDOWS\Installer\2e303314.msi. Expected product
{91CA0409-6000-11D3-8CFE-0150048383C9}, found product
{90120409-6000-11D3-8CFE-0150048383C9}.

What is the difference between the 2 product?
 
G

Gerry Hickman

Hi Phil,

I gave the keys in the thread, it's up to you if you want to change them
or how you do it. However, there's another option using MSIEXEC. It's a
bit like the CMD used to patch a client box (MSP file). When you patch a
client box from an AIP, it will reset the install source path

(at least this is true under Office 2000, not sure of 2003).

Here's an example of a batch file that patches a client, but BEWARE of
serious line wrap here!! (especially the line begins MSIEXEC.

@echo off
REM Install an office patch to a client PC by reinstalling the feature
from the Admin point
REM Runs on local machine but can be triggered from a remote script
REM /qb means "basic ui", use /qn for no UI at all
echo Installing Office 2000 Post SP3 WINWORDff v3 patch
msiexec /i "\\MyServer\install\o2ksr1adm\data1.msi" /qn /l*
c:\wordv3.txt REINSTALL=WORDFiles UPGRADEWITHRECACHE=TRUE
REINSTALLMODE=vomu REBOOT=REALLYSUPPRESS ALLUSERS=1
echo ErrorLevel is %ErrorLevel%
echo done

You could pick a box and run this as a test to see if it fixes the path.
If it does, you could choose to reapply a tiny "feature" to all
machines, and this should fix the paths, or give the /fvm switch a try
after you've read up on it fully (I've never used it, but it sounds useful).
 
G

Gerry Hickman

Hi Phil,

I gave the keys in the thread, it's up to you if you want to change them
or how you do it. However, there's another option using MSIEXEC. It's a
bit like the CMD used to patch a client box (MSP file). When you patch a
client box from an AIP, it will reset the install source path

(at least this is true under Office 2000, not sure of 2003).

Here's an example of a batch file that patches a client, but BEWARE of
serious line wrap here!! (especially the line begins MSIEXEC.

@echo off
REM Install an office patch to a client PC by reinstalling the feature
from the Admin point
REM Runs on local machine but can be triggered from a remote script
REM /qb means "basic ui", use /qn for no UI at all
echo Installing Office 2000 Post SP3 WINWORDff v3 patch
msiexec /i "\\MyServer\install\o2ksr1adm\data1.msi" /qn /l*
c:\wordv3.txt REINSTALL=WORDFiles UPGRADEWITHRECACHE=TRUE
REINSTALLMODE=vomu REBOOT=REALLYSUPPRESS ALLUSERS=1
echo ErrorLevel is %ErrorLevel%
echo done

You could pick a box and run this as a test to see if it fixes the path.
If it does, you could choose to reapply a tiny "feature" to all
machines, and this should fix the paths, or give the /fvm switch a try
after you've read up on it fully (I've never used it, but it sounds useful).
 
G

Gerry Hickman

Hi Phil,

I gave the keys in the thread, it's up to you if you want to change them
or how you do it. However, there's another option using MSIEXEC. It's a
bit like the CMD used to patch a client box (MSP file). When you patch a
client box from an AIP, it will reset the install source path

(at least this is true under Office 2000, not sure of 2003).

Here's an example of a batch file that patches a client, but BEWARE of
serious line wrap here!! (especially the line begins MSIEXEC.

@echo off
REM Install an office patch to a client PC by reinstalling the feature
from the Admin point
REM Runs on local machine but can be triggered from a remote script
REM /qb means "basic ui", use /qn for no UI at all
echo Installing Office 2000 Post SP3 WINWORDff v3 patch
msiexec /i "\\MyServer\install\o2ksr1adm\data1.msi" /qn /l*
c:\wordv3.txt REINSTALL=WORDFiles UPGRADEWITHRECACHE=TRUE
REINSTALLMODE=vomu REBOOT=REALLYSUPPRESS ALLUSERS=1
echo ErrorLevel is %ErrorLevel%
echo done

You could pick a box and run this as a test to see if it fixes the path.
If it does, you could choose to reapply a tiny "feature" to all
machines, and this should fix the paths, or give the /fvm switch a try
after you've read up on it fully (I've never used it, but it sounds useful).
 
G

Gerry Hickman

Hi Phil,

I gave the keys in the thread, it's up to you if you want to change them
or how you do it. However, there's another option using MSIEXEC. It's a
bit like the CMD used to patch a client box (MSP file). When you patch a
client box from an AIP, it will reset the install source path

(at least this is true under Office 2000, not sure of 2003).

Here's an example of a batch file that patches a client, but BEWARE of
serious line wrap here!! (especially the line begins MSIEXEC.

@echo off
REM Install an office patch to a client PC by reinstalling the feature
from the Admin point
REM Runs on local machine but can be triggered from a remote script
REM /qb means "basic ui", use /qn for no UI at all
echo Installing Office 2000 Post SP3 WINWORDff v3 patch
msiexec /i "\\MyServer\install\o2ksr1adm\data1.msi" /qn /l*
c:\wordv3.txt REINSTALL=WORDFiles UPGRADEWITHRECACHE=TRUE
REINSTALLMODE=vomu REBOOT=REALLYSUPPRESS ALLUSERS=1
echo ErrorLevel is %ErrorLevel%
echo done

You could pick a box and run this as a test to see if it fixes the path.
If it does, you could choose to reapply a tiny "feature" to all
machines, and this should fix the paths, or give the /fvm switch a try
after you've read up on it fully (I've never used it, but it sounds useful).
 
G

Gerry Hickman

Hi Phil,

I gave the keys in the thread, it's up to you if you want to change them
or how you do it. However, there's another option using MSIEXEC. It's a
bit like the CMD used to patch a client box (MSP file). When you patch a
client box from an AIP, it will reset the install source path

(at least this is true under Office 2000, not sure of 2003).

Here's an example of a batch file that patches a client, but BEWARE of
serious line wrap here!! (especially the line begins MSIEXEC.

@echo off
REM Install an office patch to a client PC by reinstalling the feature
from the Admin point
REM Runs on local machine but can be triggered from a remote script
REM /qb means "basic ui", use /qn for no UI at all
echo Installing Office 2000 Post SP3 WINWORDff v3 patch
msiexec /i "\\MyServer\install\o2ksr1adm\data1.msi" /qn /l*
c:\wordv3.txt REINSTALL=WORDFiles UPGRADEWITHRECACHE=TRUE
REINSTALLMODE=vomu REBOOT=REALLYSUPPRESS ALLUSERS=1
echo ErrorLevel is %ErrorLevel%
echo done

You could pick a box and run this as a test to see if it fixes the path.
If it does, you could choose to reapply a tiny "feature" to all
machines, and this should fix the paths, or give the /fvm switch a try
after you've read up on it fully (I've never used it, but it sounds useful).
 
G

Gerry Hickman

Hi Phil,

I gave the keys in the thread, it's up to you if you want to change them
or how you do it. However, there's another option using MSIEXEC. It's a
bit like the CMD used to patch a client box (MSP file). When you patch a
client box from an AIP, it will reset the install source path

(at least this is true under Office 2000, not sure of 2003).

Here's an example of a batch file that patches a client, but BEWARE of
serious line wrap here!! (especially the line begins MSIEXEC.

@echo off
REM Install an office patch to a client PC by reinstalling the feature
from the Admin point
REM Runs on local machine but can be triggered from a remote script
REM /qb means "basic ui", use /qn for no UI at all
echo Installing Office 2000 Post SP3 WINWORDff v3 patch
msiexec /i "\\MyServer\install\o2ksr1adm\data1.msi" /qn /l*
c:\wordv3.txt REINSTALL=WORDFiles UPGRADEWITHRECACHE=TRUE
REINSTALLMODE=vomu REBOOT=REALLYSUPPRESS ALLUSERS=1
echo ErrorLevel is %ErrorLevel%
echo done

You could pick a box and run this as a test to see if it fixes the path.
If it does, you could choose to reapply a tiny "feature" to all
machines, and this should fix the paths, or give the /fvm switch a try
after you've read up on it fully (I've never used it, but it sounds useful).
 
G

Gerry Hickman

Hi Phil,

I gave the keys in the thread, it's up to you if you want to change them
or how you do it. However, there's another option using MSIEXEC. It's a
bit like the CMD used to patch a client box (MSP file). When you patch a
client box from an AIP, it will reset the install source path

(at least this is true under Office 2000, not sure of 2003).

Here's an example of a batch file that patches a client, but BEWARE of
serious line wrap here!! (especially the line begins MSIEXEC.

@echo off
REM Install an office patch to a client PC by reinstalling the feature
from the Admin point
REM Runs on local machine but can be triggered from a remote script
REM /qb means "basic ui", use /qn for no UI at all
echo Installing Office 2000 Post SP3 WINWORDff v3 patch
msiexec /i "\\MyServer\install\o2ksr1adm\data1.msi" /qn /l*
c:\wordv3.txt REINSTALL=WORDFiles UPGRADEWITHRECACHE=TRUE
REINSTALLMODE=vomu REBOOT=REALLYSUPPRESS ALLUSERS=1
echo ErrorLevel is %ErrorLevel%
echo done

You could pick a box and run this as a test to see if it fixes the path.
If it does, you could choose to reapply a tiny "feature" to all
machines, and this should fix the paths, or give the /fvm switch a try
after you've read up on it fully (I've never used it, but it sounds useful).
 
G

Gerry Hickman

Hi Phil,

I gave the keys in the thread, it's up to you if you want to change them
or how you do it. However, there's another option using MSIEXEC. It's a
bit like the CMD used to patch a client box (MSP file). When you patch a
client box from an AIP, it will reset the install source path

(at least this is true under Office 2000, not sure of 2003).

Here's an example of a batch file that patches a client, but BEWARE of
serious line wrap here!! (especially the line begins MSIEXEC.

@echo off
REM Install an office patch to a client PC by reinstalling the feature
from the Admin point
REM Runs on local machine but can be triggered from a remote script
REM /qb means "basic ui", use /qn for no UI at all
echo Installing Office 2000 Post SP3 WINWORDff v3 patch
msiexec /i "\\MyServer\install\o2ksr1adm\data1.msi" /qn /l*
c:\wordv3.txt REINSTALL=WORDFiles UPGRADEWITHRECACHE=TRUE
REINSTALLMODE=vomu REBOOT=REALLYSUPPRESS ALLUSERS=1
echo ErrorLevel is %ErrorLevel%
echo done

You could pick a box and run this as a test to see if it fixes the path.
If it does, you could choose to reapply a tiny "feature" to all
machines, and this should fix the paths, or give the /fvm switch a try
after you've read up on it fully (I've never used it, but it sounds useful).
 
G

Gerry Hickman

Hi Phil,

I gave the keys in the thread, it's up to you if you want to change them
or how you do it. However, there's another option using MSIEXEC. It's a
bit like the CMD used to patch a client box (MSP file). When you patch a
client box from an AIP, it will reset the install source path

(at least this is true under Office 2000, not sure of 2003).

Here's an example of a batch file that patches a client, but BEWARE of
serious line wrap here!! (especially the line begins MSIEXEC.

@echo off
REM Install an office patch to a client PC by reinstalling the feature
from the Admin point
REM Runs on local machine but can be triggered from a remote script
REM /qb means "basic ui", use /qn for no UI at all
echo Installing Office 2000 Post SP3 WINWORDff v3 patch
msiexec /i "\\MyServer\install\o2ksr1adm\data1.msi" /qn /l*
c:\wordv3.txt REINSTALL=WORDFiles UPGRADEWITHRECACHE=TRUE
REINSTALLMODE=vomu REBOOT=REALLYSUPPRESS ALLUSERS=1
echo ErrorLevel is %ErrorLevel%
echo done

You could pick a box and run this as a test to see if it fixes the path.
If it does, you could choose to reapply a tiny "feature" to all
machines, and this should fix the paths, or give the /fvm switch a try
after you've read up on it fully (I've never used it, but it sounds useful).
 
G

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.
 
G

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.
 
G

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.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Best way to move administrative installation point? 24
Change Administrative installation Point 0
Patching a 2003 administrative install 9
Changing and Administrative Install point 6
Office 2003 SP2 installation via AIP for future use with WSUS 18
Access Runtime 2003 when slipstreaming SP2 27
Patch Management - Administrative Install 0
Outlook 2003 SP1 Administrative upgrade to SP2 27

Top