Windows Server 2003 OEM to Volume license
Good afternoon,
I am in the process of virtualizing 20 dell OEM licensed Windows Server 2003 servers to a vmware environment. We purchased the volume licneses for the servers and I need to convert the OEM licensed installations to OEM so that it is compliant.
To my understanding, to perform this upgrade, I need to boot from the CD and perform a repair install. i found that it also gave me the option to perform an upgrade from within Windows after the server has been virtualized. Is there any difference if i start the process from within Windows after the P2V or by booting to the CD within the VM?
i dont want to make any changes to the physical machine so i am performing these steps after the P2V has completed. I also found that after the hardware changes have been detected, on the first server that we have tried so far it did not ask to be reactivated.
Thanks!
I am in the process of virtualizing 20 dell OEM licensed Windows Server 2003 servers to a vmware environment. We purchased the volume licneses for the servers and I need to convert the OEM licensed installations to OEM so that it is compliant.
To my understanding, to perform this upgrade, I need to boot from the CD and perform a repair install. i found that it also gave me the option to perform an upgrade from within Windows after the server has been virtualized. Is there any difference if i start the process from within Windows after the P2V or by booting to the CD within the VM?
i dont want to make any changes to the physical machine so i am performing these steps after the P2V has completed. I also found that after the hardware changes have been detected, on the first server that we have tried so far it did not ask to be reactivated.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This is the EXACT instructions from our MS Platforms Specialist, which I am cutting from my email and pasting in here:
OK, here is what I am going to recommend to the team:
1) Back up the original physical server. (Operations)
2) Run the upgrade from the EVL CD to change the licensing structure on the server. (Tech Management)
3) Verify the applications still work on the physical server. (Application Owner)
4) P2V the server back into VMWare. (Tech Management)
5) Verify the applications work on the virtual server. (Application Owner)
Fall back steps:
1) Restore backup to original physical server. (Operations)
2) Verify the applications still work on the physical server. (Application Owner)
OK, here is what I am going to recommend to the team:
1) Back up the original physical server. (Operations)
2) Run the upgrade from the EVL CD to change the licensing structure on the server. (Tech Management)
3) Verify the applications still work on the physical server. (Application Owner)
4) P2V the server back into VMWare. (Tech Management)
5) Verify the applications work on the virtual server. (Application Owner)
Fall back steps:
1) Restore backup to original physical server. (Operations)
2) Verify the applications still work on the physical server. (Application Owner)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you both for your advice. I will attempt the P2V first then if it allows me into Windows, I will then perform the upgrade. if it does not allow me into Windows then I will attempt a repair. if all else fails then i will do the upgrade to the physical machine. my goal is to limit the amount of changes that happen on the physical machine. I
Thanks again, they were both good advice.
Rob
Thanks again, they were both good advice.
Rob
Justin