T
Tony
I am currently upgrading users from Office 2000 to Office 2003. I am
using an mst file, and migrating users settings. After installing to
6 machines, 2 have worked. There seems to be an issue with the other
4 regarding the migration of the user settings. When the user first
launches an application, it starts the process of migrating the
settings, but then rolls back. All of the apps roll back, but then
create the HKCU keys except for outlook, which gives an error about
the UserData key not existing. I can manually create this key to get
outlook to open. However, after getting in to the applications, there
are problems. Installing add-ins does not work properly. Watching
regmon and filemon logs shows it running msiexec.exe and subsequently
ose.exe. However, it eventually runs the rollback script and gives an
error. The one strange thing that I can see is in Filemon. Msiexec
accesses and reads normal.dot, then it runs the rollback script. I
just deleted the user's normal.dot, and everything seems to work.
What could be the cause of this? I don't think the file is corrupted,
because i copied it to another machine, and ran the upgrade and it
worked fine. (I am trying to distribute a normal.dot to everyone, so
that Word will stop attempting to use our WorkgroupTemplate directory
to save it.) Any help would be appreciated, thanks.
-tony
using an mst file, and migrating users settings. After installing to
6 machines, 2 have worked. There seems to be an issue with the other
4 regarding the migration of the user settings. When the user first
launches an application, it starts the process of migrating the
settings, but then rolls back. All of the apps roll back, but then
create the HKCU keys except for outlook, which gives an error about
the UserData key not existing. I can manually create this key to get
outlook to open. However, after getting in to the applications, there
are problems. Installing add-ins does not work properly. Watching
regmon and filemon logs shows it running msiexec.exe and subsequently
ose.exe. However, it eventually runs the rollback script and gives an
error. The one strange thing that I can see is in Filemon. Msiexec
accesses and reads normal.dot, then it runs the rollback script. I
just deleted the user's normal.dot, and everything seems to work.
What could be the cause of this? I don't think the file is corrupted,
because i copied it to another machine, and ran the upgrade and it
worked fine. (I am trying to distribute a normal.dot to everyone, so
that Word will stop attempting to use our WorkgroupTemplate directory
to save it.) Any help would be appreciated, thanks.
-tony