Mine is a little thicker, I have integrated the FOG service to turn it on and start it (Doesn’t do so well in my VM to have it on). As you can see I am using a typical naming that FOG will rename before adding it to the domain. There are two accounts that are setup also. Copying the default admin accounts allow for easier user setup in the long run also.

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <WindowsFeatures>
                <ShowMediaCenter>false</ShowMediaCenter>
                <ShowWindowsMail>false</ShowWindowsMail>
            </WindowsFeatures>
            <BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
            <ComputerName>CIN-RENAME</ComputerName>
            <CopyProfile>true</CopyProfile>
            <ProductKey>tisk-tisk</ProductKey>
            <RegisteredOrganization>Sheakley Group</RegisteredOrganization>
            <RegisteredOwner>Sheakley Group</RegisteredOwner>
            <TimeZone>Eastern Standard Time</TimeZone>
        </component>
        <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Enable Administrator Account</Description>
                    <Order>1</Order>
                    <Path>net user administrator /active:yes</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
        <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <BlockPopups>no</BlockPopups>
            <CompanyName>Sheakley Group</CompanyName>
            <Home_Page>http://intranet/SheakleyIntranet/</Home_Page>
            <DisableFirstRunWizard>true</DisableFirstRunWizard>
        </component>
        <component name="Networking-MPSSVC-Svc" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
            <PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
            <PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <NetworkLocation>Work</NetworkLocation>
                <ProtectYourPC>1</ProtectYourPC>
                <SkipMachineOOBE>true</SkipMachineOOBE>
                <SkipUserOOBE>true</SkipUserOOBE>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
            </OOBE>
            <UserAccounts>
                <AdministratorPassword>
                    <Value>Look-Away</Value>
                    <PlainText>false</PlainText>
                </AdministratorPassword>
            </UserAccounts>
            <RegisteredOrganization>Sheakley Group</RegisteredOrganization>
            <RegisteredOwner>Sheakley</RegisteredOwner>
            <TimeZone>Eastern Standard Time</TimeZone>
            <AutoLogon>
                <Password>
                    <Value>Look-Away</Value>
                    <PlainText>false</PlainText>
                </Password>
                <Enabled>true</Enabled>
                <LogonCount>3</LogonCount>
                <Username>Administrator</Username>
            </AutoLogon>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>del /Q /F c:\windows\system32\sysprep\unattend.xml</CommandLine>
                    <Order>1</Order>
                    <Description>Deletes unattend.xml</Description>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>del /Q /F c:\windows\Panther\unattend.xml</CommandLine>
                    <Description>Deletes unattend.xml</Description>
                    <Order>2</Order>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>sc config FOGService start= auto</CommandLine>
                    <Description>Changes FOG server to Automatic</Description>
                    <Order>3</Order>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>net start FOGService</CommandLine>
                    <Description>Starts FOG service </Description>
                    <Order>4</Order>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
            </FirstLogonCommands>
        </component>
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <InputLocale>en-US</InputLocale>
            <SystemLocale>en-US</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UserLocale>en-US</UserLocale>
        </component>
    </settings>
    <settings pass="generalize">
        <component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <SkipRearm>1</SkipRearm>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:e:/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>```

I have been testing quietly for some time now and the NIC to get is the StarTech USB21000S2 . Every machine I have thrown at it seem to either PXE boot just fine or UEFI boot. I haven’t gone as far as to test the FOG client yet to see all machines are working but for most it seems to work.

IT seems the SMSC - LAN7500 is about as generic as you can get and it widely used compared to all others. Hell it is even supported under Novell.

I move the machine over to another hosts in a new blade-center (Was in a crappy Dell 1U server host before) Problem ceased to exist. I also upgraded to the SVN latest and it seems to be working pretty good;

@george1421 I most definitely will.

@george1421 said in Coexistence of UEFI and Legacy - Troubleshooting help:

@psycholiquid This is a bit off topic, but I see in your snapshot of “Here is a screenshot of my setup” you are using the ipxe7156.efi. I just saw a pull request on git hub that the “7156” flavor of kernels were being removed from the FOG distribution because the latest ipxe.efi version (in 1.5.0 branch) is now working with the surface pros.

1. Just be aware that this kernel is being removed from the package and you will need to update your dhcp setup.
2. You probabaly should confirm that the latest version of ipxe.efi (pulled from the working branch) does what YOU need it to because ipxe7156.efi was left in the distribution to address an issue with the surface pros and not VMWare.

I’m not saying its a problem. I’m only trying to raise awareness that there was a change and based on your configuration you may have issues.

I know I was part of the testing process for the whole thing.

Who has two thumbs and cant read when tired?

This guy!

@george1421 If this does work FOG needs to start selling USB flashdrive and USB to Ethernet packages for support money LOL.

OK huge update.

I worked today to learn MDT (Not that bad at all) and got it all setup and the image done. With @george1421 and @Wayne-Workman I got the dual EFI and BIOS booting going, I was able to capture and deploy windows 10 Enterprise. This is setup correctly for EFI and boots no problems. I am going to build off of this now and see where I can get it. Hopefully I can document, I always say I am going to but never do because work gets the better of me.

So this is exactly what I did:

Setup VM with EFI firmware
Loaded windows and it picked up on the EFI drive and partitioned it as a GTP drive with the EFI partition.
Started the MDT sysprep and shut it down.
Changed the firmware over to BIOS on teh VM.
Captured the image
Set PC to deploy and ran it (The screen was stuck on init.xz but it was imaging)
IT rebooted after imaging and I have a Windows 10 Screen and it is Enterprise.

I looked around and didnt find the answer so I did teh troubleshooting myself. Figured I would post it here for the Wiki if you guys wanted to add it:

Using VMXNET3 ethernet adapter (Also works with E1000 and others)

Wireshark results from BOOTP filtering:

Vendor Class Setup:

Scope Policy Setup:

OK ok ok , I am an idiot… (go ahead take the stab)

So i forgot I have load balanced / failover DHCP in my environment. SO even if the fog server is set to one DHCP server it will still be pushed to the other in case of high utilization… (damn it me!!!)

So I was able to get it working more granular down to the UNDI. With what @george1421 said this could be a problem later but I am thinking it will be fine for now as the versions will probably only go up from here for change dramatically. So here is the setup for clairity.

DHCP (Windows Server 2012 R2) 'Failover is on your to configure"

Set Vendor Class for hardware. (You can get this from Wireshark easily if you run it on the DHCP server and set ip.src == IP of client PC)

Cant really copy and paste but here you go anyway: PXEClient:Arch:00007:UNDI:003016

Then goto Policies for either your whole server or for your scope depending on how your network is setup:

Make a new Policy, name it and description.

Add Condition:

Set Options:

Now if you refresh your Scope Options you will see the new options:

I have tested and this works specifically for the Surface Pro 4s with the dock. I am not sure about the dongle yet because I don’t have one.But I will see about getting one.

@JJ-Fullmer Yeah I started a new post with what I did, I had to piece together some stuff to get the whole shebang to work.

@psycholiquid I was able to resolve the refinduefi issue with the HP ProDesk 400s by pulling the old refind.conf file from the backup fog server and reverting refind.efi to version 0.11.0

Toss me in the group of people with HP ProDesk 400s All of mine are acting this way now.

Ok replaced the refind.efi with the latest 0.11.3 and made a change to the conf file and it is all owrking now.

Good job on fixing the dock issue with Surfaces, I can now image without using a seperate dongle.

So here is the steps I used to fix the issue:

1. upgraded to 1.5.4
2. Replaced bzimage and init.xz using kernel 4.15.2 and init.xz form my old version of FOG (@Sebastian-Roth custom)
3. Replaced refind.efi with verion 0.11.3 and edited out the scanfor line of the conf.

This seemed to get everything straight. So I think we are good.

@sebastian-roth But I am using kernel 15.12 and it seems to be working all but the refind UEFI

@Sebastian-Roth I recovered both, figured the init.xz is only the virtual HDD right and the bzimage is the actually loading OS.

@Sebastian-Roth yeah I got it working after updating the firmware to the latest version, it will boot and image but the refind-EFI is giving me troubles now. trying to find a way around it, GRUB doesn’t seem to work nor Does exit.

Ill post up the configuration and firmware versions once completed so everyone will know how to do it

I have tried updating the Surface firmware but so far no dice. Trying another update this morning

@sebastian-roth I was able to recover but it crashed on Fatal Error kernel to old

Resolved by dropping the kernel back down to 4.12.3.

This allows the Surface to make it past the init.xz… ok

Now stuck on Fatal kernel to old.

Will play with them more to see what I can get.