delcor1
asked on
Office 2003 Deployment via GP / Transform / Outlook Profile rolls back depending of user Windows Profiles
Setting:
Exchange 2000. Windows XPSP2. Office XP Professional with Front Page in place on user desktops. Rollout Office 2003 with various MST's, PRF's and OPS's.
Symptom:
Office 2003 installs via GP and/or as Admin using setup arguments for use of Transform file. Office 2003 Installs successfully. Create a new profile on the PC. Office 2003 successfully installs for that new user. Login to the existing profile on the machine, ostensibly for the user who was targeted with the upgrade in the first place. Start Word 2003. The Profile Installation of Word 2003 starts (you know, the first time the user uses word after a fresh 2003 install) and then rolls back. Ultimately, Word2003 opens, but the install/rollback occurs every time you start the app. Outlook 2003 cannot initialize at all and fails.
If I kill this user's profile, and create a new one. No problem. It runs. Obviously, we don't want to recreate profiles for 115 users, or some large percentage of those users.
I have tinkered with the MST and PRF and OPS till blue in the face. I have pulled the PRF file. I am creating them from scratch just in case I keep on passing the error on from file to file.
I have seen this description of the error posted here:
http://www.mcse.ms/archive175-2005-6-1391108.html
and here:
http://www.mcse.ms/message1090301-2.html
I think the bug is tied into the combination of existing Office XP Pro with Front Page Installations, existing profiles on Windows XP and the use of Transforms.
Exchange 2000. Windows XPSP2. Office XP Professional with Front Page in place on user desktops. Rollout Office 2003 with various MST's, PRF's and OPS's.
Symptom:
Office 2003 installs via GP and/or as Admin using setup arguments for use of Transform file. Office 2003 Installs successfully. Create a new profile on the PC. Office 2003 successfully installs for that new user. Login to the existing profile on the machine, ostensibly for the user who was targeted with the upgrade in the first place. Start Word 2003. The Profile Installation of Word 2003 starts (you know, the first time the user uses word after a fresh 2003 install) and then rolls back. Ultimately, Word2003 opens, but the install/rollback occurs every time you start the app. Outlook 2003 cannot initialize at all and fails.
If I kill this user's profile, and create a new one. No problem. It runs. Obviously, we don't want to recreate profiles for 115 users, or some large percentage of those users.
I have tinkered with the MST and PRF and OPS till blue in the face. I have pulled the PRF file. I am creating them from scratch just in case I keep on passing the error on from file to file.
I have seen this description of the error posted here:
http://www.mcse.ms/archive175-2005-6-1391108.html
and here:
http://www.mcse.ms/message1090301-2.html
I think the bug is tied into the combination of existing Office XP Pro with Front Page Installations, existing profiles on Windows XP and the use of Transforms.
Hello delcor1,
I'm not offering any answer here but both those keys are where word or outlook store their user custom settings like toolbar settings or app window states etc....
in your first comment you said that deleting and recreating a new user profile solves the problem, that's probably because you have no problem creating those data keys is there something in the old profile that prevents the installer from creating those keys? maybe there is a similar key and does the GUID not match
maybe for a test if you create those keys yourself and run the install again as if nothing happened then it would run? [this is no solution just see if that goes through]
bruintje
I'm not offering any answer here but both those keys are where word or outlook store their user custom settings like toolbar settings or app window states etc....
in your first comment you said that deleting and recreating a new user profile solves the problem, that's probably because you have no problem creating those data keys is there something in the old profile that prevents the installer from creating those keys? maybe there is a similar key and does the GUID not match
maybe for a test if you create those keys yourself and run the install again as if nothing happened then it would run? [this is no solution just see if that goes through]
bruintje
ASKER
I'm trying various things. One of my hunches has to do with the placement of the normal.dot file. The current Office XP installation has all users pointing to a shared, read only, normal.dot file, which I don't like. One thing the CIW might allow me to do is push a new one down.
I opened up a case with MS and I'm working with a very good Office Deployment tech support person who sent me the following registry entry to allow for verbose logging during the final install process. Of course, then I had to re-create the error so I could send him the logs.
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWA
"Debug"=dword:00000007
"Logging"="voicewarmup"
As I was writing this comment, I just received a call from the MS Tech (yes, he's called me numerous times today!). He just sent me a link to a hotfix for the Office Resource Kit that is not yet released. I don't think I can share it yet, but this certainly looks like a bug in the CIW.
I opened up a case with MS and I'm working with a very good Office Deployment tech support person who sent me the following registry entry to allow for verbose logging during the final install process. Of course, then I had to re-create the error so I could send him the logs.
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWA
"Debug"=dword:00000007
"Logging"="voicewarmup"
As I was writing this comment, I just received a call from the MS Tech (yes, he's called me numerous times today!). He just sent me a link to a hotfix for the Office Resource Kit that is not yet released. I don't think I can share it yet, but this certainly looks like a bug in the CIW.
ASKER
MS supplied me with the following hotfix:
office2003-KB835209-ENU.ex
which from what I can see is referenced in the TID:
http://support.microsoft.com/kb/835209
My initial tests indicate that this hotfix is correcting the problem on my test deployment machines. Mind you, that the hotfix is not applied to individual machines. It is a hotfix for the Office 2003 ORK. It updates the ORK and the CIW. I reopened my custom transform MST and resaved it using the updated CIW.
Another bug that was confirmed was that the Office 2003 CIW is unable to uninstall FrontPage XP. The default behavior of the 2003 install is supposed to uninstall FrontPage XP, but it fails and this was reproduced by MS. Even if you specifically chain an uninstall procedure in the CIW.
The tech supplied the following command line for uninstalling FrontPage XP:
msiexec /x {90280409-6000-11D3-8CFE-0
I hope this info helps others who are banging their head against this problem. In my case, I'm at least gratified that it was a bug, and not something I was doing wrong.
office2003-KB835209-ENU.ex
which from what I can see is referenced in the TID:
http://support.microsoft.com/kb/835209
My initial tests indicate that this hotfix is correcting the problem on my test deployment machines. Mind you, that the hotfix is not applied to individual machines. It is a hotfix for the Office 2003 ORK. It updates the ORK and the CIW. I reopened my custom transform MST and resaved it using the updated CIW.
Another bug that was confirmed was that the Office 2003 CIW is unable to uninstall FrontPage XP. The default behavior of the 2003 install is supposed to uninstall FrontPage XP, but it fails and this was reproduced by MS. Even if you specifically chain an uninstall procedure in the CIW.
The tech supplied the following command line for uninstalling FrontPage XP:
msiexec /x {90280409-6000-11D3-8CFE-0
I hope this info helps others who are banging their head against this problem. In my case, I'm at least gratified that it was a bug, and not something I was doing wrong.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 4/10/2006
Time: 1:59:51 PM
User: N/A
Computer: ABCDE
Description:
Detection of product '{90110409-6000-11D3-8CFE-
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 4/10/2006
Time: 1:59:30 PM
User: N/A
Computer: ABCDE
Description:
Detection of product '{90110409-6000-11D3-8CFE-
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.