Intelligent Provisioning and Server 2012R2 from USB

[GrahamElder]

Hi,

I am trying to install Windows Server 2012 R2 Standard from USB via Intelligent Provisioning on a brand new DL380 Gen9.

The documentation states that IP can only read FAT32 formatted USB drives, but the ISO for Windows Server 2012 R2 Standard which I have from Microsoft MVLS is 5.24GB and has individual files larger than can fit on a FAT32 formatted USB drive. The drive therefore needs to be formatted as NTFS.

I don't have a DVD drive to plug in, and setting up a network share is as useless as trying to get the USB working.

Is there a straightforward solution to allowing Intelligent Provisioning to be able to read NTFS formatted USB drives? Otherwise its a very big omission where an OS such as Windows Server cannot be installed from USB in this way.

I'm amazed that the latest generation of HP business servers are affected by such a short-sighted flaw.

Graham

[Suman_1978]

Hello,

One straight forward solution is to skip IP and install OS directly.

For OS image files that cannot copy to the USB unless it is NTFS-formatted, use a different source media, such as a DVD, network share, or FTP server.

Thank You!
I am a HP employee.

Useful Links for ProLiant Servers

[JohnsITSvcs]

One has to wonder if Suman_1978 even read the post.  

I too have been seeking a solution to this problem.  Thumb drives are faster, smaller, and easier to pack than disk images. 

I would like to know how to use intelligent providioning with an NTFS formatted flash drive, or if there is a special build of win2012r2ROK that will fit on a fat32 thumb drive.  Also, if the latter is the available option, where do I get such an iso?  

[Raffis]

I have the same problem with Windows 2016.  Files are too big to fit on USB formated in fat32, but Inteligent Provisioning can not read NTFS and extFAT system. It is really stupid. To spend so many hours to install the system.

Raffis

[Deb_Blue]

Use either Windows7-USB-DVD-Download-tool-Installer or the HP USB Key Utility for Windows to create your bootable USB drive.. works for both win2012 R2 and Win2016

[0ST0LA]

Hello everyone.

I had the same issue, but I tried to install the Operating System using the Integrated Remote Console, following the same steps and it works.

[AlanLive]

i had the same issue too. your intergrade remote console izzit mean iLo?

[AlanLive]

Finally the issue solve by using iLo intergrated remote console - then go to virtual drive map iso to image file to CD/DVD-ROM.

Next reboot to Intelligent Provisioning and select OS deployment - select image drive from iLO next follow the instruction and finally it work. 

Thanks OSTOLA

[Barren23]

Finally the issue solve by using iLo intergrated remote console - then go to virtual drive map iso to image file to CD/DVD-ROM.

The only problem with this is that you need an ILO license in order to utilize the virtual media feature... ugh, this is so annoying.  I'm going to end up loading off the USB directly after booting, which makes driving loading a huge pain.

Why haven't they allowed NTFS formatted USB drives in the Intelligent Provisionsing?

[thutchings]

IP 2.60 (and later) allows for the use of exFAT. This provides many of the features of NTFS without the security features. NTFS has some driver requirements which do not always work consistently, so have never been supported with any version of Intelligent Provisioning.

http://h20566.www2.hpe.com/hpsc/swd/public/detail?sp4ts.oid=1008862660&swItemId=MTX_77b94511492441a08eb272ed27&swEnvOid=4231#tab1

Thanks,

Terry

[MattColburn]

I had the same issue with my new DL380 Gen 9 when trying to install Server 2012 Standard R2.

Tried my normal installation methods that work on every other server: creating a bootable USB drive with rufus. Intelligent Provisioning never found it. Tried skipping IP and booting directly to the USB. No luck. 

Updated USB Firmware, tried legacy BIOS boot, made an exFAT32 USB disk, tried to use HPE's USB KEY Utility for Windows to create a bootable USB. Nope. Nope. Nope.

I finally got "Intelligent" Provisioning to recognize a network share on my FreeNAS box. Plugged in my IP address, domain info, and credentials, and wonder of wonders, my .iso appeared.  It didn't install as quickly as it would have using a USB drive, but after five hours of not installing at all, I didn't care. 

[Yiddam]

They will not complicate life there is so easy to install with a usb is best to use the dvd that came with the computer and a simple reader. :)

No se compliquen la vida no hay modo Facil de instalar con una usb lo mejor es usar el dvd que viene con el equipo y un simple lector. :)

[wooju]

Hello,

Did anyone find a solution? I was able to install windows from the usb stick (using an iso file) on dl360 gen8 servers and some of the ealrier gen 9, but now for a while i can't. It sees the drive but not the ISO file on it. I tried formating the drive using different file formats, but it made no difference.

Can somebody assist please?

[alinnesilva]

Install with iLo intergrated remote console - then go to virtual drive map iso to image file to CD/DVD-ROM, like AlanLive said. It works for me.

[wooju]

I know it can be done using an ilo, but it is a lot of "faffing" around in my enviroment. What is the point of having a feature if it doesn't work? 

I may open a case with HP to see what they have to say about it...

[Zuka007]

Hello,

Seems to me like an IP version issue rather than IP not supporting NTFS formatted USB sticks as previously mentionned.

I only experienced this issue on version 2.50 of IP for our ML350 GEN9 servers but it was not an issue with IP version 2.30 and IP version 2.61(latest available version at present) therefor you can always update your Intelligent Provisioning with the latest version. To update/flash your IP to the latest version you will need the latest IP ISO for your model and the HP USB Key Utility for Windows.

You can download the HP USB Key Utility for Windows at: https://h20565.www2.hpe.com/hpsc/swd/public/detail?sp4ts.oid=1008862658&swItemId=MTX_360731071b404454b454390208&swEnvOid=4168#tab1

*Alternatively, you can also use this same tool to simply create a bootable USB with Windwos 2012R2 if you don't want to use IP to deploy your OS to your server.

I also would like to confirm as many have already pointed out, that it is also possible to connect to your server via iLO and mount a virtual drive via the remote console to the Win2012R2 ISO and then boot to IP and select CD-ROM(iLO virtual media) as the OS source. Unlike what a previous user commented,  you can actually use this methode even if you don't have a fully licensed version of iLO. Note that once the OS is installed you will no longer be able to use the remote connection feature in iLO until you activate a license for it but you can certainly use it to initially install your OS. Clearly, the person who commented on needing a licensed version of iLO simply didn't try it. 

Hope this helps someone

[corrigun]

I know this is old but we just bought a G10 and unlike on my G7's, 8's and 9's none of these solutions work.

I have tried the HP USB tool from v 1.8 to 3.0. None will read an iso of any kind. Linux or Windows.
I have tried 3rd party USB tools but the server does not recognize any of them as bootable media.
I have tried iL0 but all virtual media is disabled without a license. I can provide a screenshot if this is in dispute.
I'm not setting up a network share and hope I can map it from iLO to install an O/S on a $7000 server. This is nuts.

I'm trying the Windows7 tool now and after that a high capacity DVD. That will be the last stop before sending this back to my rep.

EDIT: Windows7 USB tool does work.

[Torsten.]

>> I have tried the HP USB tool from v 1.8 to 3.0.

To create an USB from which ISO?

The USB tool (current version is 3.00) is used to create a bootable USB from SPP or IP ISO.

It expects several configuration settings stored in a file inside the ISO, hence it will not work with any ISO.

[Leaner]

Hi

I have HP DL560 Gen 9 Server. I am trying to install Windows Server 2012 R2 using Bootable USB Drive. After boots, its giving the error that "Windows Cannot find tjhe Micrsoft Software License Terms. Make sure the installation sources are valid and restart the installation".

Please help me to solve this issue.

[PeteLong]

I had this very problem today, I can confirmthe ILO and ExFAT approaches were both sucessful;

HP Intelligent Provisioning Cant See USB Media?

Regards,

Pete

[FluxLegend]

This should work just supplement server for 10  Step 1 - Format the drive and set the primary partition as active

1. Connect the USB flash drive to your technician PC.

2. Open Disk Management: Right-click on Start and choose Disk Management.

3. Format the partition: Right-click the USB drive partition and choose Format. Select the FAT32 file system to be able to boot either BIOS-based or UEFI-based PCs.

4. Set the partition as active: Right-click the USB drive partition and click Mark Partition as Active.

    Note

   If Mark Partition as Active isn't available, you can instead use diskpart to select the partition and mark it active.

Step 2 - Copy Windows Setup to the USB flash drive

1. Use File Explorer to copy and paste the entire contents of the Windows product DVD or ISO to the USB flash drive.

2. Optional: add an unattend file to automate the installation process. For more information, see Automate Windows Setup.

Step 3 - Install Windows to the new PC

1. Connect the USB flash drive to a new PC.

2. Turn on the PC and press the key that opens the boot-device selection menu for the computer, such as the Esc/F10/F12 keys. Select the option that boots the PC from the USB flash drive.

   Windows Setup starts. Follow the instructions to install Windows.

3. Remove the USB flash drive.

Troubleshooting: file copy fails

This can happen when the Windows image file is over the FAT32 file size limit of 4GB. When this happens:

1. Copy everything except the Windows image file (sources\install.wim) to the USB drive (either drag and drop, or use this command, where is the mounted ISO and E: is the USB flash drive.)

   Copy

   robocopy D: E: /s /max:3800000000

2. Split the Windows image file into smaller files, and put the smaller files onto the USB drive:

   Copy

   Dism /Split-Image /ImageFile:D:\sources\install.wim /SWMFile:E:\sources\install.swm /FileSize:3800

   Note, Windows Setup automatically installs from this file, so long as you name it install.swm.

[DeeGreez]

Hey, guys.
I'm not aware of any copyright, so I'll tell you my dream.

In the dream I was updating the IP to version 1.67 in my DL380p g8.
I did this by downloading the ISO image and burning it to USB(fat fs). Then I decided to install 2016. Went to IP, reached the choice of the carrier, chose USB and pressed next. I saw that displays the wrong content and realized that did not change the USB stick. I went to server, took out USB with an image of IP and inserted USB C NTFS with an image of 2016 written through Rufus. Then he returned to his ILO pressed the rescan button but nothing changed. I clicked "back" then again" forward " appeared USB cMS 2016. I went inside it and.... "Hallelujah brother.".. IP showed me files on the interface with NTFS. The "next" button became active. And I installed the system. I checked this method with the substitution of the flash drive twice. Everything worked. Then I woke up.

p/s sorry? google translator

[davey1]

Yeah, I think claiming that Intelligent Provisioning not being able to support NTFS is a cop-out.  All flavours of Linux that I've used support NTFS, and have been able to since maybe 2003, since kernel 2.6 for read-write, and that is what Intelligent Provisioning is; Linux.

Either way, my solution was to format the pendrive exFAT.  Still failed until, with my ML310e Gen8, I used a USB 2.0 pendrive (as opposed to USB 3.0 pendrive in the server's USB 2.0.  <-- That didn't work.  Intelligent provisioning ignores my Pendrive in exFAT too.

I've tried USB Key Utility from HP.  It doesn't work.  Its intended use is with certain iso files provided by HPE like the reinstallation DVD for Intelligent Provisioning, turning them in to a bootable pendrive.  In that regard, it is like Rufus or UNetbootin.  I tried USB key utility 2.1.0.0 that Zuka007 linked, and latest 3.0.  So, don't try to use it with a Windows iso.  It. Won't. Work.

There's a reason I'm using Intelligent Provisioning; I have been given Server 2019 on DVD, and I have my pendrive prepped with 2016 on exFAT.  If I ignore Intelligent Provisioning, boot directly off either DVD or pendrive, then install the RAID driver to get a device to install to, I get this error:

Windows cannot be installed to this disk.  This computer's hardware may not support booting to this disk.  Ensure that the disk's controller is enabled in the computer's BIOS menu.

And when I look in the BIOS or RAID configuration utility to check, I can't see a setting to allow for this.  Hence, I'm persevering with Intelligent Provisioning to see if that can overcome this basic installation fail.

This sucks.  I know more about web-hosting on Ubuntu than installing or using an MS OS on a server. Commandline configuring a LAMP stack was FUN!  A joyous and rewarding experience.

!!STOP PRESS!!  I think I've just read now that if you put your Windows install iso directly on the exFAT pendrive, instead of extracting all files from the iso, it might just work.  Also, I've seen that booting from pendrive without Intelligent Provisioning, installing the RAID driver from a second pendrive and then removing that pendrive before selecting an installation destination is a suitable fix.  Trying now, in the order I've presented them in.

UPDATE:  Using intelligent provisioning to install Windows Server 2016/2019 on an HP ML310e Gen8, using a DVD or a pendrive formatted in exFAT, either with the iso file or the contents of the iso extracted does not work.  If anyone can suggest a method, I'd like to know I am utterly beyond caring.  However, I've now got it installed.  One of two things fixed it for me.  Either, as I suggested earlier, removing the secondary pendrive immediately after installing the RAID driver, or it was caused by a quirk of my RAID config, in that I'm using two RAID1 pairs, and had them both set to be bootable.  Disabling the bootable option on the second RAID1 pair might've been the trick.  One or the other worked.  Either way, I'm installed, and not by using so-called Intelligent Provisioning.

If I could write emoticons here, it would be whale, oil drum, steak, fishing pole.