This is the menu change I made:
Posts
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
@Tom-Elliott OK Params set this is the result.
I tried using just the USB NIC but it will just loop boot on it. I am having to use the SP4 docking station in order to get to the FOG menu. So basically the USB NIC is the secondary NIC.
Why cant they ever make this a bit easier.
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
@Tom-Elliott OK I’ll give that a try.
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
@Sebastian-Roth I’m still not sure what you guys mean by that, were am I adding this?
“Try adding ‘has_usb_nic=1’ as Tom suggested.”
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
Sorry @Sebastian-Roth I wasn’t quite understanding what you were saying, you are right at the last step it does look like it isn’t going anywhere.
Also a heads up in the latest trunk my users were being ask to enter TFTP address when booting to netwokr after they rebooted, so I had to roll it back until that is resolved.
This was on the undionly.kpxe boot file.
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
@Sebastian-Roth I have two NICs in the device at the time of testing (1 is the docking station and 1 is the USB dongle. They are both working one is not network connected.
After I get past that it does bring up the FOG menu so it is talking to the server and getting an address. What I am having a problem with it would seem is the error while trying to register. I am attempting now to just put in the MAC manually and upload an image to see what it does.
I have looked at the partitions and there are 4 on a surface 1 is the EFI partition, one is the boot partition, the last two are OS and Restore (So basically the restore partition in case something goes wrong you can put it back to factory. I am of the opinion to keep all 4 so when it comes time there is no need to reimage we can just restore and boom.
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
As a test I did try making a Windows 10 bootable USB drive and it is working so I know EFI is working from all the ports be it docking for on-board.
Now to figure out a way to get the FOG bzimage on there to talk to the server? I am not sure what I am thinking here, a little over my head.!!!

-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
@Tom-Elliott said:
isdebug=yes
How do I do that?
I have a snapshot of the FOG server so we cant mess it up. We can test whatever we need
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
Probably need to add I am using the ipxe.efi form the server to boot.
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
@Tom-Elliott Sorry had to hit publish, got pulled into a meeting
Users are the worst.
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
OK I updated the trunk to the latest and got a bit farther. Let me explain the procedure I am using for now to at least get somewhere today:
I have the surface pro 4 setup to boot from network without IPV6. I have also turned off secure boot in order to get it to download the NBP file. Once it goes through the motions I get errors right after Starting host registration.
So upgrading the trunk allowed it to see the drive which is better. but it cant seem to register it. If we can get past that part and I can take a restore image of it I cant start testing deploying one. Then I just need to figure out how to get it to PXE boot to the network card or docking station it has. but lets work on this first part. I am uploading a video for the process in motion.
-
Surface 4 Network boot and Imageposted in Hardware Compatibility
OK I have finally gotten a Surface 4 Pro to boot to FOG. however when trying to register the device I get a cannot find HDD. I have seen this on a few machines now if they are using the flash card for the HDD> what would I need to provide to get this working, I am sure it is a unknown device problem.
-
RE: Boot Dell XPS 12 to USB to Network cardposted in Hardware Compatibility
Moving to new post. This has gotten a little to unruly
-
RE: Windows 10 unattend.xml (sysprep answer file) challengeposted in Windows Problems
@MRCUR Yeah I figured why add another file when I can just do it all in one motion.
-
RE: Windows 10 unattend.xml (sysprep answer file) challengeposted in Windows Problems
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>``` -
RE: Windows 10 unattend.xml (sysprep answer file) challengeposted in Windows Problems
@Wayne-Workman You want the Unattend? I can send it minus the key if you want.
-
RE: Windows 10 unattend.xml (sysprep answer file) challengeposted in Windows Problems
I can confirm the Unattended I had for my Windows 7 is working great in 10 Enterprise also.
-
RE: Recommended USB to Ethernet adapterposted in General
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.
-
RE: Boot Dell XPS 12 to USB to Network cardposted in Hardware Compatibility
@george1421 Roger that, I’ll give a try after my meeting
-
RE: Boot Dell XPS 12 to USB to Network cardposted in Hardware Compatibility
@george1421 Where do I find the FOSL file. I am using the file from the site you had on the other post to create the efi file.