Office 2007 Deployment via GPO

Working for a computer support company in Baltimore, MD, I run into many server and domain issues that I have never seen before. The other day I ran into the following error when deploying Office 2007 via a GPO in Server 2003.
Error 25004: Per-User install not supported.
The error is pretty much self-explanatory. I attempted to deploy the software under "User Configuration" in the GPO, but that is not supported with Office 2007. You can only use the "Computer Configuration."

This seemed easy to remedy. I would delete the incorrect GPO and create a new one with the proper configuration. So that's what I did.

It wasn't that easy. No matter what I did I always got that same error. I removed the bad GPO and logged in. When I tried to run Word 2007, I got the error. I then created the new GPO and restarted my PC for the group policy to refresh. Then I logged in, opened Word, and got the same error. I even tried to install Office from the CD. I got the same error again. It seemed like the incorrectly configured GPO would not go away. I even used RSOP.msc to see what policies were being applied, and the bad GPO was not being applied.

After hours of ripping what little hair I have out, and multiple phone calls to my friend, a computer repair technician in Columbia and Laurel, MD, I came to a realization. I was going to delete the user account I was using, and recreate the account. My thought was that this user account was having trouble forgetting about the "Per-User" installation of Office 2007 that I tried.

Sure enough, as soon as I logged in with my newly created account everything was perfect. The new GPO (properly configured) was applied at startup and I was able to open Office 2007 with no issues.

I was lucky because this was a new domain. Obviously, you cannot just go deleting and recreating users in a production domain, but if you can, this is the resolution to the 25004: Per-User install not supported" error.