CMW Not Working

S

Shaun Phurrough

We use Administrative Installation Points (AIP) in a central location to
deploy Office 2003 (with SP1). At this time, we are only deploying Outlook
2003, so I have setup a custom MST which is applied at installation. The MST
installs Outlook 2003 only and locks out everything else (except shared
files, of course). The installations work without issue and Outlook works
without issue.

We now want to deploy InfoPath 2003. Because it is locked out (and there
were administrative reasons we had to do that at the time), the user cannot
simply go to Add/Remove Programs to install it. Therefore, there are two
options, both of which work half the time and are broken the other half:

(1) Run PRO.MSI from the AIP (which shows all the entries and allows the
installaton to be completely updated).

(2) Create a CMW (Custom Maintenance Wizard) file which installs InfoPath
and keeps the current settings for everything else.

In BOTH of these scenarios, sometimes InfoPath installs while other times it
does not. In BOTH scenarios, everything progresses AS IF the installation
was successful. There are no errors, the progress bar scrolls along and the
process takes the same amount of time. However, sometimes, we go to find the
InfoPath shortcut and it isn't there. Checking for the executable also
yields nothing.

I can't figure out why it isn't installing sometimes. We've tried different
things which sometimes help, but there is not consistent result:

- Run PRO.MSI and attempt to install InfoPath (Fails); immediately follow
that by applying the CMW and everything works fine

- Sometimes the above won't work, but doing the reverse will

- Sometimes neither of the above work, but running a repair first will work
(and sometimes this won't work either)

We haven't done anything to the AIP or the workstation which would break the
"tie" to the AIP (such as an update or service pack). Regardless, we have
tried the usual refresh and it doesn't help.

Elevated Priv is enabled (and I verified the HKLM and HKCU entries). An
uninstall and full reinstall without the MST works fine as the user.
Regardless, we still tried as Admin and we still get the same inconsistent
results. Tried a different MST and the same problem eventually crept up
again. It's as if Windows Installer 3.1 is broken or perhaps there is an
issue with the Custom Maintenance Wizard in 2003?

All of our computers are standard images, firmwide.

I'm really at a loss. I have a 1000 users to push this out to and no way to
do it, seemingly without a full uninstall/reinstall (which is unacceptable).

If no one has seen this before, do you have any recommendations on how else
to push out InfoPath? Any and all help is greatly appreciated!
 
B

Bob Buckland ?:-\)

Hi Shaun,

Are there differences in the log files for successful vs 'missing'
setting of Infopath to 'run from my computer'?

Were the users logged off when you did the update?

When you say you 'locked out' everything else what state did you
set the installation features to for Infopath in the initial install
(I'm assuming this is a single Adminpoint with the Office Enterprise
setup for Office 2003 Professional Edition?

========
We use Administrative Installation Points (AIP) in a central location to
deploy Office 2003 (with SP1). At this time, we are only deploying Outlook
2003, so I have setup a custom MST which is applied at installation. The MST
installs Outlook 2003 only and locks out everything else (except shared
files, of course). The installations work without issue and Outlook works
without issue.

We now want to deploy InfoPath 2003. Because it is locked out (and there
were administrative reasons we had to do that at the time), the user cannot
simply go to Add/Remove Programs to install it. Therefore, there are two
options, both of which work half the time and are broken the other half:

(1) Run PRO.MSI from the AIP (which shows all the entries and allows the
installaton to be completely updated).

(2) Create a CMW (Custom Maintenance Wizard) file which installs InfoPath
and keeps the current settings for everything else.

In BOTH of these scenarios, sometimes InfoPath installs while other times it
does not. In BOTH scenarios, everything progresses AS IF the installation
was successful. There are no errors, the progress bar scrolls along and the
process takes the same amount of time. However, sometimes, we go to find the
InfoPath shortcut and it isn't there. Checking for the executable also
yields nothing.

I can't figure out why it isn't installing sometimes. We've tried different
things which sometimes help, but there is not consistent result:

- Run PRO.MSI and attempt to install InfoPath (Fails); immediately follow
that by applying the CMW and everything works fine

- Sometimes the above won't work, but doing the reverse will

- Sometimes neither of the above work, but running a repair first will work
(and sometimes this won't work either)

We haven't done anything to the AIP or the workstation which would break the
"tie" to the AIP (such as an update or service pack). Regardless, we have
tried the usual refresh and it doesn't help.

Elevated Priv is enabled (and I verified the HKLM and HKCU entries). An
uninstall and full reinstall without the MST works fine as the user.
Regardless, we still tried as Admin and we still get the same inconsistent
results. Tried a different MST and the same problem eventually crept up
again. It's as if Windows Installer 3.1 is broken or perhaps there is an
issue with the Custom Maintenance Wizard in 2003?

All of our computers are standard images, firmwide.

I'm really at a loss. I have a 1000 users to push this out to and no way to
do it, seemingly without a full uninstall/reinstall (which is unacceptable).

If no one has seen this before, do you have any recommendations on how else
to push out InfoPath? Any and all help is greatly appreciated! >>
 
B

Bob Buckland ?:-\)

Hi Shaun,

Are there differences in the log files for successful vs 'missing'
setting of Infopath to 'run from my computer'?

Were the users logged off when you did the update?

When you say you 'locked out' everything else what state did you
set the installation features to for Infopath in the initial install
(I'm assuming this is a single Adminpoint with the Office Enterprise
setup for Office 2003 Professional Edition?

========
We use Administrative Installation Points (AIP) in a central location to
deploy Office 2003 (with SP1). At this time, we are only deploying Outlook
2003, so I have setup a custom MST which is applied at installation. The MST
installs Outlook 2003 only and locks out everything else (except shared
files, of course). The installations work without issue and Outlook works
without issue.

We now want to deploy InfoPath 2003. Because it is locked out (and there
were administrative reasons we had to do that at the time), the user cannot
simply go to Add/Remove Programs to install it. Therefore, there are two
options, both of which work half the time and are broken the other half:

(1) Run PRO.MSI from the AIP (which shows all the entries and allows the
installaton to be completely updated).

(2) Create a CMW (Custom Maintenance Wizard) file which installs InfoPath
and keeps the current settings for everything else.

In BOTH of these scenarios, sometimes InfoPath installs while other times it
does not. In BOTH scenarios, everything progresses AS IF the installation
was successful. There are no errors, the progress bar scrolls along and the
process takes the same amount of time. However, sometimes, we go to find the
InfoPath shortcut and it isn't there. Checking for the executable also
yields nothing.

I can't figure out why it isn't installing sometimes. We've tried different
things which sometimes help, but there is not consistent result:

- Run PRO.MSI and attempt to install InfoPath (Fails); immediately follow
that by applying the CMW and everything works fine

- Sometimes the above won't work, but doing the reverse will

- Sometimes neither of the above work, but running a repair first will work
(and sometimes this won't work either)

We haven't done anything to the AIP or the workstation which would break the
"tie" to the AIP (such as an update or service pack). Regardless, we have
tried the usual refresh and it doesn't help.

Elevated Priv is enabled (and I verified the HKLM and HKCU entries). An
uninstall and full reinstall without the MST works fine as the user.
Regardless, we still tried as Admin and we still get the same inconsistent
results. Tried a different MST and the same problem eventually crept up
again. It's as if Windows Installer 3.1 is broken or perhaps there is an
issue with the Custom Maintenance Wizard in 2003?

All of our computers are standard images, firmwide.

I'm really at a loss. I have a 1000 users to push this out to and no way to
do it, seemingly without a full uninstall/reinstall (which is unacceptable).

If no one has seen this before, do you have any recommendations on how else
to push out InfoPath? Any and all help is greatly appreciated! >>
 
B

Bob Buckland ?:-\)

Hi Shaun,

Are there differences in the log files for successful vs 'missing'
setting of Infopath to 'run from my computer'?

Were the users logged off when you did the update?

When you say you 'locked out' everything else what state did you
set the installation features to for Infopath in the initial install
(I'm assuming this is a single Adminpoint with the Office Enterprise
setup for Office 2003 Professional Edition?

========
We use Administrative Installation Points (AIP) in a central location to
deploy Office 2003 (with SP1). At this time, we are only deploying Outlook
2003, so I have setup a custom MST which is applied at installation. The MST
installs Outlook 2003 only and locks out everything else (except shared
files, of course). The installations work without issue and Outlook works
without issue.

We now want to deploy InfoPath 2003. Because it is locked out (and there
were administrative reasons we had to do that at the time), the user cannot
simply go to Add/Remove Programs to install it. Therefore, there are two
options, both of which work half the time and are broken the other half:

(1) Run PRO.MSI from the AIP (which shows all the entries and allows the
installaton to be completely updated).

(2) Create a CMW (Custom Maintenance Wizard) file which installs InfoPath
and keeps the current settings for everything else.

In BOTH of these scenarios, sometimes InfoPath installs while other times it
does not. In BOTH scenarios, everything progresses AS IF the installation
was successful. There are no errors, the progress bar scrolls along and the
process takes the same amount of time. However, sometimes, we go to find the
InfoPath shortcut and it isn't there. Checking for the executable also
yields nothing.

I can't figure out why it isn't installing sometimes. We've tried different
things which sometimes help, but there is not consistent result:

- Run PRO.MSI and attempt to install InfoPath (Fails); immediately follow
that by applying the CMW and everything works fine

- Sometimes the above won't work, but doing the reverse will

- Sometimes neither of the above work, but running a repair first will work
(and sometimes this won't work either)

We haven't done anything to the AIP or the workstation which would break the
"tie" to the AIP (such as an update or service pack). Regardless, we have
tried the usual refresh and it doesn't help.

Elevated Priv is enabled (and I verified the HKLM and HKCU entries). An
uninstall and full reinstall without the MST works fine as the user.
Regardless, we still tried as Admin and we still get the same inconsistent
results. Tried a different MST and the same problem eventually crept up
again. It's as if Windows Installer 3.1 is broken or perhaps there is an
issue with the Custom Maintenance Wizard in 2003?

All of our computers are standard images, firmwide.

I'm really at a loss. I have a 1000 users to push this out to and no way to
do it, seemingly without a full uninstall/reinstall (which is unacceptable).

If no one has seen this before, do you have any recommendations on how else
to push out InfoPath? Any and all help is greatly appreciated! >>
 
B

Bob Buckland ?:-\)

Hi Shaun,

Are there differences in the log files for successful vs 'missing'
setting of Infopath to 'run from my computer'?

Were the users logged off when you did the update?

When you say you 'locked out' everything else what state did you
set the installation features to for Infopath in the initial install
(I'm assuming this is a single Adminpoint with the Office Enterprise
setup for Office 2003 Professional Edition?

========
We use Administrative Installation Points (AIP) in a central location to
deploy Office 2003 (with SP1). At this time, we are only deploying Outlook
2003, so I have setup a custom MST which is applied at installation. The MST
installs Outlook 2003 only and locks out everything else (except shared
files, of course). The installations work without issue and Outlook works
without issue.

We now want to deploy InfoPath 2003. Because it is locked out (and there
were administrative reasons we had to do that at the time), the user cannot
simply go to Add/Remove Programs to install it. Therefore, there are two
options, both of which work half the time and are broken the other half:

(1) Run PRO.MSI from the AIP (which shows all the entries and allows the
installaton to be completely updated).

(2) Create a CMW (Custom Maintenance Wizard) file which installs InfoPath
and keeps the current settings for everything else.

In BOTH of these scenarios, sometimes InfoPath installs while other times it
does not. In BOTH scenarios, everything progresses AS IF the installation
was successful. There are no errors, the progress bar scrolls along and the
process takes the same amount of time. However, sometimes, we go to find the
InfoPath shortcut and it isn't there. Checking for the executable also
yields nothing.

I can't figure out why it isn't installing sometimes. We've tried different
things which sometimes help, but there is not consistent result:

- Run PRO.MSI and attempt to install InfoPath (Fails); immediately follow
that by applying the CMW and everything works fine

- Sometimes the above won't work, but doing the reverse will

- Sometimes neither of the above work, but running a repair first will work
(and sometimes this won't work either)

We haven't done anything to the AIP or the workstation which would break the
"tie" to the AIP (such as an update or service pack). Regardless, we have
tried the usual refresh and it doesn't help.

Elevated Priv is enabled (and I verified the HKLM and HKCU entries). An
uninstall and full reinstall without the MST works fine as the user.
Regardless, we still tried as Admin and we still get the same inconsistent
results. Tried a different MST and the same problem eventually crept up
again. It's as if Windows Installer 3.1 is broken or perhaps there is an
issue with the Custom Maintenance Wizard in 2003?

All of our computers are standard images, firmwide.

I'm really at a loss. I have a 1000 users to push this out to and no way to
do it, seemingly without a full uninstall/reinstall (which is unacceptable).

If no one has seen this before, do you have any recommendations on how else
to push out InfoPath? Any and all help is greatly appreciated! >>
 
B

Bob Buckland ?:-\)

Hi Shaun,

Are there differences in the log files for successful vs 'missing'
setting of Infopath to 'run from my computer'?

Were the users logged off when you did the update?

When you say you 'locked out' everything else what state did you
set the installation features to for Infopath in the initial install
(I'm assuming this is a single Adminpoint with the Office Enterprise
setup for Office 2003 Professional Edition?

========
We use Administrative Installation Points (AIP) in a central location to
deploy Office 2003 (with SP1). At this time, we are only deploying Outlook
2003, so I have setup a custom MST which is applied at installation. The MST
installs Outlook 2003 only and locks out everything else (except shared
files, of course). The installations work without issue and Outlook works
without issue.

We now want to deploy InfoPath 2003. Because it is locked out (and there
were administrative reasons we had to do that at the time), the user cannot
simply go to Add/Remove Programs to install it. Therefore, there are two
options, both of which work half the time and are broken the other half:

(1) Run PRO.MSI from the AIP (which shows all the entries and allows the
installaton to be completely updated).

(2) Create a CMW (Custom Maintenance Wizard) file which installs InfoPath
and keeps the current settings for everything else.

In BOTH of these scenarios, sometimes InfoPath installs while other times it
does not. In BOTH scenarios, everything progresses AS IF the installation
was successful. There are no errors, the progress bar scrolls along and the
process takes the same amount of time. However, sometimes, we go to find the
InfoPath shortcut and it isn't there. Checking for the executable also
yields nothing.

I can't figure out why it isn't installing sometimes. We've tried different
things which sometimes help, but there is not consistent result:

- Run PRO.MSI and attempt to install InfoPath (Fails); immediately follow
that by applying the CMW and everything works fine

- Sometimes the above won't work, but doing the reverse will

- Sometimes neither of the above work, but running a repair first will work
(and sometimes this won't work either)

We haven't done anything to the AIP or the workstation which would break the
"tie" to the AIP (such as an update or service pack). Regardless, we have
tried the usual refresh and it doesn't help.

Elevated Priv is enabled (and I verified the HKLM and HKCU entries). An
uninstall and full reinstall without the MST works fine as the user.
Regardless, we still tried as Admin and we still get the same inconsistent
results. Tried a different MST and the same problem eventually crept up
again. It's as if Windows Installer 3.1 is broken or perhaps there is an
issue with the Custom Maintenance Wizard in 2003?

All of our computers are standard images, firmwide.

I'm really at a loss. I have a 1000 users to push this out to and no way to
do it, seemingly without a full uninstall/reinstall (which is unacceptable).

If no one has seen this before, do you have any recommendations on how else
to push out InfoPath? Any and all help is greatly appreciated! >>
 
B

Bob Buckland ?:-\)

Hi Shaun,

Are there differences in the log files for successful vs 'missing'
setting of Infopath to 'run from my computer'?

Were the users logged off when you did the update?

When you say you 'locked out' everything else what state did you
set the installation features to for Infopath in the initial install
(I'm assuming this is a single Adminpoint with the Office Enterprise
setup for Office 2003 Professional Edition?

========
We use Administrative Installation Points (AIP) in a central location to
deploy Office 2003 (with SP1). At this time, we are only deploying Outlook
2003, so I have setup a custom MST which is applied at installation. The MST
installs Outlook 2003 only and locks out everything else (except shared
files, of course). The installations work without issue and Outlook works
without issue.

We now want to deploy InfoPath 2003. Because it is locked out (and there
were administrative reasons we had to do that at the time), the user cannot
simply go to Add/Remove Programs to install it. Therefore, there are two
options, both of which work half the time and are broken the other half:

(1) Run PRO.MSI from the AIP (which shows all the entries and allows the
installaton to be completely updated).

(2) Create a CMW (Custom Maintenance Wizard) file which installs InfoPath
and keeps the current settings for everything else.

In BOTH of these scenarios, sometimes InfoPath installs while other times it
does not. In BOTH scenarios, everything progresses AS IF the installation
was successful. There are no errors, the progress bar scrolls along and the
process takes the same amount of time. However, sometimes, we go to find the
InfoPath shortcut and it isn't there. Checking for the executable also
yields nothing.

I can't figure out why it isn't installing sometimes. We've tried different
things which sometimes help, but there is not consistent result:

- Run PRO.MSI and attempt to install InfoPath (Fails); immediately follow
that by applying the CMW and everything works fine

- Sometimes the above won't work, but doing the reverse will

- Sometimes neither of the above work, but running a repair first will work
(and sometimes this won't work either)

We haven't done anything to the AIP or the workstation which would break the
"tie" to the AIP (such as an update or service pack). Regardless, we have
tried the usual refresh and it doesn't help.

Elevated Priv is enabled (and I verified the HKLM and HKCU entries). An
uninstall and full reinstall without the MST works fine as the user.
Regardless, we still tried as Admin and we still get the same inconsistent
results. Tried a different MST and the same problem eventually crept up
again. It's as if Windows Installer 3.1 is broken or perhaps there is an
issue with the Custom Maintenance Wizard in 2003?

All of our computers are standard images, firmwide.

I'm really at a loss. I have a 1000 users to push this out to and no way to
do it, seemingly without a full uninstall/reinstall (which is unacceptable).

If no one has seen this before, do you have any recommendations on how else
to push out InfoPath? Any and all help is greatly appreciated! >>
 
B

Bob Buckland ?:-\)

Hi Shaun,

Are there differences in the log files for successful vs 'missing'
setting of Infopath to 'run from my computer'?

Were the users logged off when you did the update?

When you say you 'locked out' everything else what state did you
set the installation features to for Infopath in the initial install
(I'm assuming this is a single Adminpoint with the Office Enterprise
setup for Office 2003 Professional Edition?

========
We use Administrative Installation Points (AIP) in a central location to
deploy Office 2003 (with SP1). At this time, we are only deploying Outlook
2003, so I have setup a custom MST which is applied at installation. The MST
installs Outlook 2003 only and locks out everything else (except shared
files, of course). The installations work without issue and Outlook works
without issue.

We now want to deploy InfoPath 2003. Because it is locked out (and there
were administrative reasons we had to do that at the time), the user cannot
simply go to Add/Remove Programs to install it. Therefore, there are two
options, both of which work half the time and are broken the other half:

(1) Run PRO.MSI from the AIP (which shows all the entries and allows the
installaton to be completely updated).

(2) Create a CMW (Custom Maintenance Wizard) file which installs InfoPath
and keeps the current settings for everything else.

In BOTH of these scenarios, sometimes InfoPath installs while other times it
does not. In BOTH scenarios, everything progresses AS IF the installation
was successful. There are no errors, the progress bar scrolls along and the
process takes the same amount of time. However, sometimes, we go to find the
InfoPath shortcut and it isn't there. Checking for the executable also
yields nothing.

I can't figure out why it isn't installing sometimes. We've tried different
things which sometimes help, but there is not consistent result:

- Run PRO.MSI and attempt to install InfoPath (Fails); immediately follow
that by applying the CMW and everything works fine

- Sometimes the above won't work, but doing the reverse will

- Sometimes neither of the above work, but running a repair first will work
(and sometimes this won't work either)

We haven't done anything to the AIP or the workstation which would break the
"tie" to the AIP (such as an update or service pack). Regardless, we have
tried the usual refresh and it doesn't help.

Elevated Priv is enabled (and I verified the HKLM and HKCU entries). An
uninstall and full reinstall without the MST works fine as the user.
Regardless, we still tried as Admin and we still get the same inconsistent
results. Tried a different MST and the same problem eventually crept up
again. It's as if Windows Installer 3.1 is broken or perhaps there is an
issue with the Custom Maintenance Wizard in 2003?

All of our computers are standard images, firmwide.

I'm really at a loss. I have a 1000 users to push this out to and no way to
do it, seemingly without a full uninstall/reinstall (which is unacceptable).

If no one has seen this before, do you have any recommendations on how else
to push out InfoPath? Any and all help is greatly appreciated! >>
 
B

Bob Buckland ?:-\)

Hi Shaun,

Are there differences in the log files for successful vs 'missing'
setting of Infopath to 'run from my computer'?

Were the users logged off when you did the update?

When you say you 'locked out' everything else what state did you
set the installation features to for Infopath in the initial install
(I'm assuming this is a single Adminpoint with the Office Enterprise
setup for Office 2003 Professional Edition?

========
We use Administrative Installation Points (AIP) in a central location to
deploy Office 2003 (with SP1). At this time, we are only deploying Outlook
2003, so I have setup a custom MST which is applied at installation. The MST
installs Outlook 2003 only and locks out everything else (except shared
files, of course). The installations work without issue and Outlook works
without issue.

We now want to deploy InfoPath 2003. Because it is locked out (and there
were administrative reasons we had to do that at the time), the user cannot
simply go to Add/Remove Programs to install it. Therefore, there are two
options, both of which work half the time and are broken the other half:

(1) Run PRO.MSI from the AIP (which shows all the entries and allows the
installaton to be completely updated).

(2) Create a CMW (Custom Maintenance Wizard) file which installs InfoPath
and keeps the current settings for everything else.

In BOTH of these scenarios, sometimes InfoPath installs while other times it
does not. In BOTH scenarios, everything progresses AS IF the installation
was successful. There are no errors, the progress bar scrolls along and the
process takes the same amount of time. However, sometimes, we go to find the
InfoPath shortcut and it isn't there. Checking for the executable also
yields nothing.

I can't figure out why it isn't installing sometimes. We've tried different
things which sometimes help, but there is not consistent result:

- Run PRO.MSI and attempt to install InfoPath (Fails); immediately follow
that by applying the CMW and everything works fine

- Sometimes the above won't work, but doing the reverse will

- Sometimes neither of the above work, but running a repair first will work
(and sometimes this won't work either)

We haven't done anything to the AIP or the workstation which would break the
"tie" to the AIP (such as an update or service pack). Regardless, we have
tried the usual refresh and it doesn't help.

Elevated Priv is enabled (and I verified the HKLM and HKCU entries). An
uninstall and full reinstall without the MST works fine as the user.
Regardless, we still tried as Admin and we still get the same inconsistent
results. Tried a different MST and the same problem eventually crept up
again. It's as if Windows Installer 3.1 is broken or perhaps there is an
issue with the Custom Maintenance Wizard in 2003?

All of our computers are standard images, firmwide.

I'm really at a loss. I have a 1000 users to push this out to and no way to
do it, seemingly without a full uninstall/reinstall (which is unacceptable).

If no one has seen this before, do you have any recommendations on how else
to push out InfoPath? Any and all help is greatly appreciated! >>
 
B

Bob Buckland ?:-\)

Hi Shaun,

Are there differences in the log files for successful vs 'missing'
setting of Infopath to 'run from my computer'?

Were the users logged off when you did the update?

When you say you 'locked out' everything else what state did you
set the installation features to for Infopath in the initial install
(I'm assuming this is a single Adminpoint with the Office Enterprise
setup for Office 2003 Professional Edition?

========
We use Administrative Installation Points (AIP) in a central location to
deploy Office 2003 (with SP1). At this time, we are only deploying Outlook
2003, so I have setup a custom MST which is applied at installation. The MST
installs Outlook 2003 only and locks out everything else (except shared
files, of course). The installations work without issue and Outlook works
without issue.

We now want to deploy InfoPath 2003. Because it is locked out (and there
were administrative reasons we had to do that at the time), the user cannot
simply go to Add/Remove Programs to install it. Therefore, there are two
options, both of which work half the time and are broken the other half:

(1) Run PRO.MSI from the AIP (which shows all the entries and allows the
installaton to be completely updated).

(2) Create a CMW (Custom Maintenance Wizard) file which installs InfoPath
and keeps the current settings for everything else.

In BOTH of these scenarios, sometimes InfoPath installs while other times it
does not. In BOTH scenarios, everything progresses AS IF the installation
was successful. There are no errors, the progress bar scrolls along and the
process takes the same amount of time. However, sometimes, we go to find the
InfoPath shortcut and it isn't there. Checking for the executable also
yields nothing.

I can't figure out why it isn't installing sometimes. We've tried different
things which sometimes help, but there is not consistent result:

- Run PRO.MSI and attempt to install InfoPath (Fails); immediately follow
that by applying the CMW and everything works fine

- Sometimes the above won't work, but doing the reverse will

- Sometimes neither of the above work, but running a repair first will work
(and sometimes this won't work either)

We haven't done anything to the AIP or the workstation which would break the
"tie" to the AIP (such as an update or service pack). Regardless, we have
tried the usual refresh and it doesn't help.

Elevated Priv is enabled (and I verified the HKLM and HKCU entries). An
uninstall and full reinstall without the MST works fine as the user.
Regardless, we still tried as Admin and we still get the same inconsistent
results. Tried a different MST and the same problem eventually crept up
again. It's as if Windows Installer 3.1 is broken or perhaps there is an
issue with the Custom Maintenance Wizard in 2003?

All of our computers are standard images, firmwide.

I'm really at a loss. I have a 1000 users to push this out to and no way to
do it, seemingly without a full uninstall/reinstall (which is unacceptable).

If no one has seen this before, do you have any recommendations on how else
to push out InfoPath? Any and all help is greatly appreciated! >>
 
S

Shaun Phurrough

Bob:

I've been looking at the logs and haven't found anything that stands out.
Still comparing though as there is a lot to compare with all the
inconsistencies.

No. They have access to the AIP (which is what I assume you are getting
at). If they didn't, then I would have received different indications. As
it is, everything seems as if it is working normally.

InfoPath was originally locked out as well. Only Outlook and the shared
files were installed. I've have used the exact same procedures with Office
Prof 2002 without any of these issues in the past. It is only using Office
2003 that the issue arises.

Yes, single AIP for Office 2003 Prof (created using the standard method of
creating and admin point from the office msi).

Thanks!
 
S

Shaun Phurrough

Bob:

I've been looking at the logs and haven't found anything that stands out.
Still comparing though as there is a lot to compare with all the
inconsistencies.

No. They have access to the AIP (which is what I assume you are getting
at). If they didn't, then I would have received different indications. As
it is, everything seems as if it is working normally.

InfoPath was originally locked out as well. Only Outlook and the shared
files were installed. I've have used the exact same procedures with Office
Prof 2002 without any of these issues in the past. It is only using Office
2003 that the issue arises.

Yes, single AIP for Office 2003 Prof (created using the standard method of
creating and admin point from the office msi).

Thanks!
 
S

Shaun Phurrough

Bob:

I've been looking at the logs and haven't found anything that stands out.
Still comparing though as there is a lot to compare with all the
inconsistencies.

No. They have access to the AIP (which is what I assume you are getting
at). If they didn't, then I would have received different indications. As
it is, everything seems as if it is working normally.

InfoPath was originally locked out as well. Only Outlook and the shared
files were installed. I've have used the exact same procedures with Office
Prof 2002 without any of these issues in the past. It is only using Office
2003 that the issue arises.

Yes, single AIP for Office 2003 Prof (created using the standard method of
creating and admin point from the office msi).

Thanks!
 
S

Shaun Phurrough

Bob:

I've been looking at the logs and haven't found anything that stands out.
Still comparing though as there is a lot to compare with all the
inconsistencies.

No. They have access to the AIP (which is what I assume you are getting
at). If they didn't, then I would have received different indications. As
it is, everything seems as if it is working normally.

InfoPath was originally locked out as well. Only Outlook and the shared
files were installed. I've have used the exact same procedures with Office
Prof 2002 without any of these issues in the past. It is only using Office
2003 that the issue arises.

Yes, single AIP for Office 2003 Prof (created using the standard method of
creating and admin point from the office msi).

Thanks!
 
S

Shaun Phurrough

Bob:

I've been looking at the logs and haven't found anything that stands out.
Still comparing though as there is a lot to compare with all the
inconsistencies.

No. They have access to the AIP (which is what I assume you are getting
at). If they didn't, then I would have received different indications. As
it is, everything seems as if it is working normally.

InfoPath was originally locked out as well. Only Outlook and the shared
files were installed. I've have used the exact same procedures with Office
Prof 2002 without any of these issues in the past. It is only using Office
2003 that the issue arises.

Yes, single AIP for Office 2003 Prof (created using the standard method of
creating and admin point from the office msi).

Thanks!
 
S

Shaun Phurrough

Bob:

I've been looking at the logs and haven't found anything that stands out.
Still comparing though as there is a lot to compare with all the
inconsistencies.

No. They have access to the AIP (which is what I assume you are getting
at). If they didn't, then I would have received different indications. As
it is, everything seems as if it is working normally.

InfoPath was originally locked out as well. Only Outlook and the shared
files were installed. I've have used the exact same procedures with Office
Prof 2002 without any of these issues in the past. It is only using Office
2003 that the issue arises.

Yes, single AIP for Office 2003 Prof (created using the standard method of
creating and admin point from the office msi).

Thanks!
 
S

Shaun Phurrough

Bob:

I've been looking at the logs and haven't found anything that stands out.
Still comparing though as there is a lot to compare with all the
inconsistencies.

No. They have access to the AIP (which is what I assume you are getting
at). If they didn't, then I would have received different indications. As
it is, everything seems as if it is working normally.

InfoPath was originally locked out as well. Only Outlook and the shared
files were installed. I've have used the exact same procedures with Office
Prof 2002 without any of these issues in the past. It is only using Office
2003 that the issue arises.

Yes, single AIP for Office 2003 Prof (created using the standard method of
creating and admin point from the office msi).

Thanks!
 
S

Shaun Phurrough

Bob:

I've been looking at the logs and haven't found anything that stands out.
Still comparing though as there is a lot to compare with all the
inconsistencies.

No. They have access to the AIP (which is what I assume you are getting
at). If they didn't, then I would have received different indications. As
it is, everything seems as if it is working normally.

InfoPath was originally locked out as well. Only Outlook and the shared
files were installed. I've have used the exact same procedures with Office
Prof 2002 without any of these issues in the past. It is only using Office
2003 that the issue arises.

Yes, single AIP for Office 2003 Prof (created using the standard method of
creating and admin point from the office msi).

Thanks!
 
S

Shaun Phurrough

Bob:

I've been looking at the logs and haven't found anything that stands out.
Still comparing though as there is a lot to compare with all the
inconsistencies.

No. They have access to the AIP (which is what I assume you are getting
at). If they didn't, then I would have received different indications. As
it is, everything seems as if it is working normally.

InfoPath was originally locked out as well. Only Outlook and the shared
files were installed. I've have used the exact same procedures with Office
Prof 2002 without any of these issues in the past. It is only using Office
2003 that the issue arises.

Yes, single AIP for Office 2003 Prof (created using the standard method of
creating and admin point from the office msi).

Thanks!
 

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

Top