ProLiant Deployment and Provisioning
1827294 Members
1251 Online
109960 Solutions
New Discussion

Images on multiple Hardware Platforms

 
John Shaw_6
Occasional Contributor

Images on multiple Hardware Platforms

With RDP (2.1) we currently deploy servers after creating an image from a smartstart boot. This way, each platform (G3, G2, G4, Blade, Rack Mount) must have a unique image.

This is getting unmanageable/

Is there a way to create an image and have it apply across platforms?

How would we need to change our process to accomodate the different types of hardware deployed through RDP?
3 REPLIES 3
Gopi Sekar
Honored Contributor

Re: Images on multiple Hardware Platforms


I am not sure about the process of how you are creating the image. But I believe you are not using RDP to capture images.

If your question is about hardware independent imaging, then RDP is not there yet virtually.

If you are trying to capture windows images then you can use sysprep (from microsoft) before RDP to make the image generic which can be captured and deployed across different hardwares. There are well written articles on how to achieve this.

Regards,
Gopi
Never Never Never Giveup
Gordon Leonard
Honored Contributor

Re: Images on multiple Hardware Platforms

The RDP 2.1 package also allows you to deploy the OS via an unattended install. You may want to explore using this process to deploy your OS. You can also create custom "follow-on" packages and make them part of the deployment. RDP comes with a software tool called Rapid Install - It's very much like Windows SYSDIF; where it takes a before and after snap shot. You can use this tool to create your "follow-on" packages. Hope this helps.
Steven Clementi
Honored Contributor

Re: Images on multiple Hardware Platforms

John:

If you wanted to... lets say take an image that worked on a 380G2, G3 and G4...

First, build your OS on the G2. Once complete, update the registry with the 6i registry key and make sure yo uhave the most uptodate Smart Array drivers.

Second, remove the drives from the g2 and put them into a g3. They should boot up with no issues, but will look to load additional drivers for new system devices found. Let them load and reboot.

Third, once the g3 is rebooted and all is well... shut it down and put the drives into the g4. Let it boot up and find all new hardware. Reboot and your ready to image the g4. Now you should have an image that works on the DL380 G2, G3 and G4.

You should be able to also put this image on a BL20pG2 and G3 as they are the same class servers as the Dl380G3 and G4, minus the extra hard drive space. Following this pattern, you should be able to reduce your images.

Alternatively, you can us the "unattended setup" features of Windows which allow you to to add/remove and set every normal setting within windows... all during the set up phase. This includes setting up AD, Clustering and really any accessory and/or builtin application on Windows.

Granted, the imaging scenario I laid out for you is not VERY clean, but it should work.

Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)