We have an existing W2K3 SBS running on aging hardware. We want to migrate to a newer Intel-based server platform. We are able to clone-image the existing W2K3sbs [which is still running in the production environment] to another disk. The other disk we are able to use in a 'sandbox' environment to successfully address any problems experienced in the migration on the new hardware.
We have successfully created a "slipstreamed" install CD with all the appropriate drivers and have been able to run the slipstreamed W2K3 SBS SP2 w drivers CD on the new hardware and have selected the non-destructive reinstall option to "repair" the installation.
The first iteration of repair-install went smoothly.
Upon the second iteration, which shows the typical splash-screen-countdown of 'setup will be completed in 39 minutes' etc-- the prompt-pages appear for the insertion of the product key.
We have entered the original product key from the original OEM box and license certificate, but the response is: "The CD key you entered is not valid."
The old-existing system is still running in the production environment and we have verified using ProduKey that we are, in fact, entering the correct key. Also on the existing system, we have used the msoobe.exe to confirm that the old-existing system is activated.
Question: on the new hardware-install, how do we get passed the error?
Since the "repair" is pulling its info from the 'repaired' registry, this would indicate that there is something wrong with the old-existing system's product key, even though it is running fine, and ProduKey confirms that the key is the same sequence of characters that are on our license.
There are instructions on the internet on how to reset a Windows XP's product key using msoobe.exe and editing the WPAEvents area of the local registry-- but does this method work in a W2K3 SBS environment?
All that being said-- the real issue is how to get passed the "The CD key you entered is not valid." error when the key we have is in fact the correct key.