I have a PXE server for deploying Windows XP and Windows 7 to workstations.

The process is as follows:

  1. Boot the workstation from the NIC.
  2. Workstation sends a DHCP request.
  3. DHCP server responds with an IP address and the location of the PXE server.
  4. Workstation downloads WinPE image file from PXE server via TFTP
  5. Workstation stores WinPE image file in memory and executes it.
  6. Once booted into WinPE, I connect to a network share to gain access to either the Windows XP or Windows 7 installation files.
  7. A custom script is launched to guide you through the process of formatting and partitioning the hard drive(s) (using DISKPART and FORMAT).
  8. Another custom script asks for details such as the hostname to assign to the workstation. The answers provided are used to build an unattended answer file (SIF [Setup Information File] for WinXP and XML for Win7).
  9. The Windows setup EXE is launched, passing the unattended answer file to it as a parameter.

The Windows XP and Windows 7 installation sources have been customised to include the drivers for our Dell workstations. They also run a number of scripts upon first booting up to install software packages.

This process works very well for our workstations and I would now like to use it for building our servers too. The vast majority of our servers are HP Proliant DL360 G6, DL380 G5 and DL380 G6. They’re running Windows Server 2003 (various editions) or 2008 (various editions).

To date, we have always built the HP Proliant servers using the SmartStart CD provided. SmartStart does three useful things for us:

  1. Setup RAID with HP Array Configuration Utility (ACU).
  2. Installs and configures SNMP
  3. Installs various HP Tools for Windows (HP Array Configuration Utility, HP Array Diagnostic Utility, HP Proliant Integrated Management Log Viewer, etc)

Using SmartStart I have never had to manually download and install Windows drivers for network, sound, video, etc. I'm not sure if this is because SmartStart copies drivers from the CD during setup, or whether Windows just has the drivers natively in its driver CAB.

If I abandon the SmartStart CD in favour of my PXE server I would have to do the following:

  • As I wont have access to ACU, I'll configure the RAID (before booting to the PXE server) by pressing F8 (during the boot process) to access Option ROM Configuration for Arrays (ORCA).
  • Installation of SNMP and the HP Tools will have to be installed once the Windows installation is complete using the Proliant Support Pack.

Is this method OK? Is there anything that the SmartStart CD does that I'll be unable to do by other means? Are there any disadvantages to not using the SmartStart CD?

Many thanks.

UPDATE 05/01/12

I’ve been reading through the SmartStart Scripting Toolkit documentation.

The scripting toolkit contains command line tools which work within WinPE and can such things as configure BIOS settings, configure an array and setup ILO.

I’m personally not too bothered about configuring BIOS settings as I rarely deviate from the defaults (unless the server is to be a Hyper-V host).

I’m not too fussed about being able to configure the array from within WinPE, as I’m happy to just press F8 and use Option ROM Configuration for Arrays (ORCA). Although, if it’s easy enough to do, I will explore this further, as it saves time if everything can be configured from within WinPE.

One of the nice features all the tools possess is that you can pass input files to them. EG. Configure one server to your requirements, capture its configuration to a file (using the appropriate tool), you can then use the tool on other servers passing the input file with the captured configuration.

Array controller drivers appear to be included with the toolkit along with example of how to incorporate them within a WinPE build.

I suppose WinPE won’t be able to see logical volumes (I.E 2x physical disks in a RAID 1 configuration) without the array controller drivers?

I mentioned in my post that SmartStart normally installs a bunch of Windows HP tools for you. I’ve had a look today, and if you run the SmartStart CD from within Windows all the tools can be installed. Therefore I can do this after the Windows installation is complete.

The SmartStart CD appears to contain a lot Windows drivers. I can customise my Windows 2008 source to incorporate these drivers.

However, I understand that incorporating an array controller driver is a little different to most drivers. I believe that you have to provide the driver during the very early stages of the Windows setup. I’m working through the Scripting Toolkit documentation to try and work this out...

  • Just wanted t being this post to rest. – Fitzroy Feb 23 '12 at 23:04
  • Just wanted to bring this post to rest. I am now successfully building HP Proliant servers without the SmartStart CD. I incorporated the drivers from the SmartStart Scripting Toolkit into my WinPE WIM file. I tested booting to WinPE before and after adding the drivers, the only difference seemed to be that WinPE couldnt see the NIC before adding the drivers. Once Windows Server 2008 has finished installing, I have configured runonceex to launch the Proliant Support Pack to install tools and drivers upon first logging in. – Fitzroy Feb 23 '12 at 23:13
  • If your comment is the resolution to this question, please post it as an answer, and mark it accepted. This will resolve the question and will remove it from the "unanswered" category. – jscott Apr 15 '12 at 12:00

You should use HP's solution named Rapid Deployment Pack which is part of HP Insight Control

It's exact purpose is deploying various OS to HP Proliant servers.

| improve this answer | |

We've had ZERO luck doing this without the SmartStart disk. Every time we try it, the server eventually blue screens. Unfortunately, I haven't had time to investigate the actual cause. We use DL180, DL360, DL380, and various BLXXX flavors (mostly G5 and G6).

| improve this answer | |
  • How were you kicking off the Windows installations. By using a CD or using a PXE server? – Fitzroy Jan 5 '12 at 23:30
  • We use Windows Deployment Server for client installations (and servers when we can), so PXE. – JeffM Jan 9 '12 at 20:59

Doesn't SmartStart have an option to essentially deploy an image you can use via PXE to boot? I know you can use Windows Deployment and Ghost together (there is even an MSDN article on it) so I would be surprised if HP did not offer a way to do this too.

Edit: SmartStart Scripting toolkit (http://h18002.www1.hp.com/products/servers/management/toolkit/questionsanswers.html) is what I was thinking of.

| improve this answer | |
  • I was just starting to read through the Scripting Toolkit documentation before I composed this question. I had hoped that I wouldnt need to resort to using it,but actually it does appear to necessary to fulfil my requirements. I've edited my post to detail where I am so far. – Fitzroy Jan 5 '12 at 23:22

we have done this many times ... you can look at HP RDP (HP remote deployement) wich come with many images to remote install via (PXE) i do not remember all the details .. but i know it s doable .. you can take the images from RDP and follow the tasks they do before/after the install image the end system is exactly the same as if you ve done the installation with smartstart ps. i ve found the smartstart scripting toolkit document hard to follow .. copying the images and install setps from HP RDP was easier for me .. good luck

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.