YeOldeStonecat
Well-Known Member
- Reaction score
- 6,546
- Location
- Englewood Florida
Got a client that I have to nurse 1x more year out of an existing server of theirs, and sadly it's an OEM Server 2003 Standard install on an HP Proliant 350 that needs to be retired. I'm trying to suck them into a new Hyper-V box that I've migrated their other servers to.
It's really too complicated of a server to rebuild from scratch, Canon imageWare document cabinet, plus 2x other SQL databases which were proprietary. So I'm getting desperate in just flipping this to a hyper-v guest.
They have the VLK licensing...from another server that got retired. As far a legality with the Microsoft police I'm fine.
I've attempted the "repair install"....which I've done in the past with VMWare and it worked...bring over the VHD files, copy a Server 2k3 ISO over...mount, bootup..do the repair install, enter the new key, reboot..re-catch up on a ton of Windows updates and installed apps and settings remain and you're good.
This one ain't working...keeps getting stuck in a loop where I go back to "setup is restarting" and I select the time zone 'n keyboard and install the key...and it proceeds for "32 minutes remaining"...goes for a while, reboots, repeat cycle.
As you know, booting up an OEM Server 2003 instance...you get to login, type in the password...and within a few seconds you're faced with a screen that forces you to activate...either online, or by calling Microsoft. Which denies you because it's OEM. If you can't satisfy that screen you can't go further, only choice is to shut down.
Man I can't stand OEM server licenses! One of several examples why we stay away from them for our clients...but in this case, I'm stuck with this scenario.
It's really too complicated of a server to rebuild from scratch, Canon imageWare document cabinet, plus 2x other SQL databases which were proprietary. So I'm getting desperate in just flipping this to a hyper-v guest.
They have the VLK licensing...from another server that got retired. As far a legality with the Microsoft police I'm fine.
I've attempted the "repair install"....which I've done in the past with VMWare and it worked...bring over the VHD files, copy a Server 2k3 ISO over...mount, bootup..do the repair install, enter the new key, reboot..re-catch up on a ton of Windows updates and installed apps and settings remain and you're good.
This one ain't working...keeps getting stuck in a loop where I go back to "setup is restarting" and I select the time zone 'n keyboard and install the key...and it proceeds for "32 minutes remaining"...goes for a while, reboots, repeat cycle.
As you know, booting up an OEM Server 2003 instance...you get to login, type in the password...and within a few seconds you're faced with a screen that forces you to activate...either online, or by calling Microsoft. Which denies you because it's OEM. If you can't satisfy that screen you can't go further, only choice is to shut down.
Man I can't stand OEM server licenses! One of several examples why we stay away from them for our clients...but in this case, I'm stuck with this scenario.