Follow the instructions on this website, and you should be able to enter a
different product key:
http://www.mcgimpsey.com/macoffice/office/pid.html
Also, to uninstall Office completely, you need to use the uninstaller
provided by Microsoft (Applications/Office 2004/Additional Tools/Remove
Office); simply deleting the applications will leave the PID files
untouched.
On 25.09.05 23:46, in article BF5CA0FD.BBD6B%rlhaar@comcast.net, "Robert L.
Haar" <rlhaar@comcast.net> wrote:
> I ran into a problem where I think I need to establish a new product key for
> Office:Mac 2004, but I cannot figure out how.
[quoted text clipped - 14 lines]
>
> I'm hoping someone on the newsgroup can help.
Robert L. Haar - 26 Sep 2005 03:27 GMT
> Follow the instructions on this website, and you should be able to enter a
> different product key:
[quoted text clipped - 5 lines]
> Office); simply deleting the applications will leave the PID files
> untouched.
I followed the command line procedure since I am running Tiger, but that
wasn't good enough. Office still came up with the old PID.
It turned out that I had to remove both Office 2004 and the previous Office
v.X version. Then I could re-install and supply the second Product Key. I
was a bit worried about loosing my email settings and saved files. But it
seems fine.
JE McGimpsey - 26 Sep 2005 05:33 GMT
> I followed the command line procedure since I am running Tiger, but that
> wasn't good enough. Office still came up with the old PID.
[quoted text clipped - 3 lines]
> was a bit worried about loosing my email settings and saved files. But it
> seems fine.
Hmmm....
That shouldn't have been necessary - I have XL98, XL01, XLv.X and XL04
installed on my machine, and I can run the procedure with no problems.
Robert L. Haar - 26 Sep 2005 09:12 GMT
>> I followed the command line procedure since I am running Tiger, but that
>> wasn't good enough. Office still came up with the old PID.
[quoted text clipped - 8 lines]
> That shouldn't have been necessary - I have XL98, XL01, XLv.X and XL04
> installed on my machine, and I can run the procedure with no problems.
I don't know. The PID must be stored somewhere. It was like a zombie coming
back from the dead.
I used the admin account to do the command line procedure. I even ran a find
command afterwards looking for anything named "*PID*" afterwards.