So here's what I've come up with. I don't know why this didn't click
with me before, but we use a PXE server (and LANDesk) to push out
workstations images via a network boot. I don't really have anything to
do with that side of our ops, so I guess that's why it slipped my mind.
Anyway, I will start testing this:
Add necessary drivers to the PXE server (for VMware and the target HP
server)
Make a test VM (same settings - VMware disk adapter, etc) as my
production VM
Pre-install the HP RAID and NIC drivers to the VM
Network boot it into my PXE server
Make an image of it (we have scripts to do that for our various
workstation models, so one of my guys will just adapt one)
Network boot the blade it will end up on (HP BL460 G6)
Push the image down onto the blade
Power up the blade, and let it reboot as many times as it wants, since
it should find all the HP drivers it wants, already installed into
Windows, for all the new hardware it will see
Cross fingers and hope the application itself works properly.
Tweak steps as needed
When I see that the new physical box works, I will repeat it with the
production VM (after snapshotting it. Maybe also keeping a powered off
copy, as well). The new box will have the same SID, so no worries there.
No application changes (the big concern), so no worries there. The
properly running powered-off VM available as fallback, if and/or when.
Thoughts? Flaws? Concerns not covered?
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin
