Windows 10 BIOS/UEFI 2021 edition
17-Mar-21 this post is currently being edited, so its not complete
First we’ll create the required directories. In this tutorial we will use a windows server/workstation to host the installer files. This is the easiest solution, but if your goal is to only use the FOG server follow the instructions at the end of this thread for SAMBA install instructions. On your file server copy the content of the Windows installation DVD to a folder on your file server. Be sure to set the permission so that everyone has read only access to that directory. Now share that directory. For this tutorial the Windows file server will be called \fileserv01 with the share name of \win10$
In this next step you will need a valid user ID. It can be a domain level or machine level. Create this user id and password. For this tutorial we will create a domain account called consento\user01
Beyond this point you will need a Windows 10 1909 (or later) workstation. You also need to be aware what version of windows 10 you intend to deploy. You need to download the proper version of Windows ADK for the version of Windows 10 you will execute these instructions against.
Launch the ADK installer. You will be presented with about 15 different modules to install. You only “need” the Deployment Tools feature from the “Windows ADK for Windows 10”. Now run the “Windows PE add-on for the ADK” installer . From this installer you will need (the only option) Windows Preinstallation Environment (Windows PE).
It might take as long as 20 minutes to install both packages depending on your network connection and target computer.
While this step is not necessary it is also a bit of an assurance that WinPE10 will have a good install of basic drivers needed to boot current hardware.
I realize that you may not be using a Dell for your imaging, don’t worry these drivers only cover network and disk subsystems.
Extract the winpe folder from the cab file and copy it in the winpe folder in the root of C drive (c:\winpe).
After the install launch the ADK environment from Start Button->Windows Kits->Windows ADK->Deployment and Imaging Tools Environment Make sure you run this command window as Administrator. FYI: you’ll need admin rights to use DISM.
In the Deployment and Imaging Tools Environment command window you just opened you will need to execute the following commands.
For the rest of the instructions we’ll just go copy and paste. Its fast and quick.
copype amd64 C:\WinPE_amd64
Dism /Mount-Image /ImageFile:"C:\WinPE_amd64\media\sources\boot.wim" /index:1 /MountDir:"C:\WinPE_amd64\mount"
Dism /Add-Driver /Image:"C:\WinPE_amd64\mount" /Driver:"c:\winpe\x64" /Recurse /ForceUnsigned
Now we need to edit the WinPE startup file to have it mount our windows (samba) network share.
echo Setting up WinPE
REM Set power configuration to Performance
powercfg /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c
echo Connecting to the remote share
net use z: \\<server_name>\<share_name> /user:<domain\uid> <pass>
I stopped here editing this document
15. Now that we have the settings the way we need them. Lets close the wim file and create our ISO.
Now move the C:\WinPE_amd64\WinPE_amd64.iso file to the FOG server in the /images/os/mswindows/7Pro-x64 directory.
The last bit of magic we need to do is setup a new FOG iPXE boot menu entry for this OS.
NOTE: This instruction is for legacy bios only. If you need to boot both uefi and bios installs follow the WinPE10 section above. The issue is that memdisk utility is not supported in uefi mode, so another method is required. For bios mode memdisk IS the quickest method to boot a small iso image. https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/10
In the fog WebGUI go to FOG Configuration->iPXE New Menu Entry
Set the following fields Menu Item: os.Win7Pro-x64 Description: Windows 7 Pro x64 OEM Parameters:
chain memdisk iso raw
boot || goto MENU Menu Show with: All Hosts
That’s it, just pxe boot your target system and pick Windows 7 Pro x64 OEM from the FOG iPXE boot menu.
Yes i can run the exe because it is an portable edition
Great this then gives us a path or at least an idea. In this post https://forums.fogproject.org/post/103323 it talks about building a winpe image that we can use to boot an OS. (sidebar: I’ve done this for a ghost imager). Starting at step 3 it shows how to build a winpe boot environment. You will place the files into the image path before the image is resealed back into the wim. This will place the files you need in the wim file that will get deployed. Once we get to the boot.wim we are done with this tutorial. There is no need to make the iso because that is only for bios mode.
@danboid Thanks for you detailed write up on setting up FOG!
I just tried to edit the first post but I was denied. Could we ditch this rule please, at least for this post?
I didn’t know the forum has such a rule. @Tom-Elliott Do you know if it’s possible to allow editing own posts for users as well?
Here is another comment: We don’t suggest running the installer via sudo directly because the environment variables is different on some Linux systems (and can cause issues!) compared to switching over to the root user via sudo -i or sudo su -.
@lebrun78 I don’t use the FOG Client so I can’t really speak to its activation of the target computer. But I believe if its enabled in the fog management web ui and you have entered either a OEM key or VLK key in the host configuration for that computer the FOG Client will try to activate it. I believe this is outside of any sysprep process.
I can tell you how I use MDT, sysprep and FOG.
I do use MDT to build my golden image each time using the lite touch process. At the end of imaging I run through a quick quality check to ensure everything is setup as it should be then I run a batch file that MDT drops in a certain directory that calls sysprep and points to a custom unattend.xml file. Sysprep then powers off the computer. I capture it with FOG. Then deploy it. I have a post install script update the unattend.xml file on the target computer with the computer’s name, target OU, timezone, KMS Key, and a few other things. When the computer boots and runs WinSetup/OOBE the target computer connects itself to AD and in the proper OU from the unattend.xml file. At the end of OOBE WinSetup calls the setupcomplete.cmd and runs a command cscript c:\Windows\System32\slmgr.vbs /ato that activates windows.
Hi @george1421 and @Sebastian-Roth , thank you very much for your assistance on this issue. Sorry for delay in replying here as I just completed the testing on my side. Yes changing Kernal Ramdisk size to 275000 worked and I was able to capture the image fine. The image is working perfectly okay now. Many thank and much appreciated, you guys are amazing and very helpful.