In the second week of December 2009, we encountered a blue screen error of death on our Windows 2003 Server which hosts our SQL Server. This Server is responsible for all operations of our Microsoft Dynamics. We also have mobile sales being uploaded into Dynamics from another SQL Server that hosts the mobile system software. We made numerous attempts to repair the Windows 2003 server and being as critical as it is we eventually had to do a non-destructive build on it. The system was not accepting the original OS CD’s, so we borrowed an alternate Windows Server 2003 CD to rebuild the system using the product key on that CD. Due to the fact that the product key was different than the OEM copy that was installed previously we had to reinstall Microsoft SQL 2000, Microsoft Dynamics and also reconfigure settings on the Mobile Sales Server. Adhering to software agreement pertaining to having a genuine license we have now purchased a non OEM copy of Windows Server 2003. This copy is exactly the same as the one we borrowed that is installed on the server now. We will now like to have our Server 2003 registering the product key we have now bought. Is there a way you can assist us in allowing the system to register the product key now bought without affecting the SQL Server and the Mobile Sales software?

Hi, It sounds like you only need to change the key for the OS, this article covers how to change the key on Windows XP and 2003, http://support.microsoft.com/kb/328874/en-us -- Mike Burr

Hello Mike, That article is only for Volume License media and changing from one volume license key to another volume license product key, it does not apply to Retail media or OEM media. Betmck, Is this Retail media? If so and the machine is activated, you need to rename the wpa.dbl and wpa.bak files, that will change the activation status to unactivated, so at the next logon ( or after a reboot) you should be prompted to activate via the wizard where you would choose the phone option which has the button to change the product key.Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights. Volume Activation documentation on TechNet http://technet.microsoft.com/en-us/windows/dd197314.aspx http://technet.microsoft.com/en-us/library/dd996588.aspx VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Hi Darrell, What do you mean by Retail media? How do I know if it is a Retail media? Bearing in mind the problems we had initially with the SQL server, Microsoft Dynamics and the Mobile software. I do not want to have to repeat reinstalling them again. Do you think changing the product key will cause that to happen again? What I need is to be able to change the key and continue normal operations without having to reconfigure any thing else. Thanks

Darrell, I just found out that it is a Retail Media. However, I am still concern about the issues mentioned above.

Hello Betmck, You can change from an installed Retail key to another retail key without having to reinstall the OS, I was not aware that changing a product key would affect SQL server, Microsoft Dynamics, or the Mobile software or any other software, this is the first time I have ever heard that. That question however is best asked of those products support forums, that is not a Windows issue that is something that software would be checking for specificallyThanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights. Volume Activation documentation on TechNet http://technet.microsoft.com/en-us/windows/dd197314.aspx http://technet.microsoft.com/en-us/library/dd996588.aspx VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en