Topics created by kyle.heath

@Joe-Schmitt Yep I had bat for some reason…No idea how because I used to have.cmd

The error in the 3rd photo says (paraphrasing) that you’re trying to put a 240GB image onto a 120GB disk, that won’t work. There are a few ways to solve that issue. My recommendation is to deploy the image to a disk that is 240GB or larger and then create a new image in FOG and set it as resizable, and then capture the image you just deployed. This way you have a resizable image that will fit on a smaller disk than what it came from. In addition to that benefit, the image would also expand to use all space available on a larger disk than what it came from.

For the other errors, they are weird. Not sure what’s going on there. It would behoove of you to share what OS you’re running fog on. Also, check how much free space you have available on your server with df -h. In the output from that command, look for partitions with 99% or 100% usage - if you see that, that’s bad. If you see that and need help with it, just ask here.

0_1481896545682_upload-57c7ed4c-bdca-461e-80d8-f39b373b2438

0_1481896570352_upload-88e1b112-ac45-4a5e-905b-72b4fc7adce7

So can I just put the product key in the second photo where it says ProductKey instead of putting it under OOBE

@Tom-Elliott Thanks! This worked.

@kyle.heath Does the bios updates only run in windows or is there a DOS option?

In our case we use a WinPE boot disk that has all of our dell bios drivers on it. We boot from usb flash drive that has WinPE on it then we launch the proper bios driver to update the system. We have scripted an automated process for this now, but that is the basics of how we install a consistent bios version on all of our bare metal computers (we use a winpe boot disk).