Home

Unsuccessful in deploying to bare-metal with both .wim and .vhd methods

Chris Parker
Contributor

I've been slowly working my way towards deploying Nano server for the first time. I have a spare R710 with local storage available to me.

 

I've been referencing the following three guides:

 

  1. Instructions on creating a VHD or WIM file
    https://technet.microsoft.com/en-us/windows-server-docs/get-started/nano-server-quick-start
  2. Instructions on installing using a bootable USB drive and the VHD
    http://en.community.dell.com/techcenter/b/techcenter/archive/2016/05/20/how-to-deploy-nano-server-tp...
  3. Instructions on installing using a bootable USB drive and the WIM
    https://blogs.technet.microsoft.com/nanoserver/2016/07/29/bare-metal-machine-using-a-wim-and-winpe/

 

I've not been successful in following either the second or third guide.

 

I've created a bootable USB drive using the Server 2016 ISO. I created VHD and WIM files and copied them to the root of USB drive. I'm able to boot from the USB drive into the command prompt.

 

When I created the VHD I ended up with a ~700MB file. When I used the first deployment guide (second link) everything went fine until the `bcdboot <drive>:\Windows` command. That gave me an error saying something about not being able to copy the files. This appeared to be a generic error for bcdboot but all the solutions didn't seem relevant to me.

 

I went back to the first link and created the WIM which generated a 236MB file. Much smaller than the VHD so I question wether it has everything I need and may be part of the problem.

 

So far, no matter which guide I follow, every reboot ends with "No boot device available."

 

I've even tried changing the boot type of the server between BIOS and UEFI.

 

One final note. On the bcdboot command in the second guide, it finishes successfully but there are no files in the target drive.

 

edit: For clarity.

2 Replies

The problem is solved.

 

Turns out the issue was because the raid disk I was presenting to the OS was too large. I changed the virtual disk to be below 2TB total and then everything went as expected. (Used link #2.)

Nice work on fixing the issue, and even better for reporting back and letting everyone know your fix :)