asked on

Problems with virtual servers running Windows Server 2008 R2 licence activation after migrating to new hardware

I have recently migrated Windows Server 2008 R2 virtual servers running in a VM environment onto new hardware. i.e. new esxi host servers and new physical datastore. Since then I have been receiving messages on my server saying that Windows is not activated. There does not seem to be any way of activating the operating system now.

ASKER CERTIFIED SOLUTION

dfke

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rabpwh1000

ASKER

Thanks for the response dfke. Unfortunately it looks like I have made the mistake you have referred to in your post. Is there a way of reactivating windows once the virtual machines have new hardware identifiers? I keep getting a message reactivation failed or unable to reactivate windows.

SOLUTION

RAFA

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

RAFA

Execute a sysprep in the operating system, to create a new identifier of the VM and select the option Generalize.

RAFA

I indicate the route:

C: \ Windows \ System32 \ sysprep

Run the sysprep as administrator
Leave the option that appears by default
Enable the Generalize
And accept, after generating the new identifier, the server restarts and validates if you still see the message to activate the license.

Slaudos ...

dfke

Hi,

If you are unable to re-export then I think there is little chance. If I'm not mistaken Microsoft does not legally allow a P2V to a different server, so your best bet is to get rid of the target server, acquire another server license, and install it from scratch. Then migrate over what you have from the source server to the target server.

Cheers

RAFA

Hello

Could you perform the aforementioned tests?

did you execute the sysprep?

Greetings.

rabpwh1000

ASKER

Thanks everybody for your help. I eventually managed to speak to the engineer who did the migration and he said all vm's were created from new and all that needed to be done was open up the server manager on each local machine and re-enter the MAK key manually. This seems to have worked for me. The expert comments have been useful to me and I am now more aware of some the pitfalls during the migration process if I have to do this again.