@Quazz said in Surface Book won't boot the kernel:
Aside from has_usb_nic=1 , try using the kernel command iommu=soft as well.
@Quazz has_usb_nic=1 did the job, excellent man 
Surface Book is now working with FOG… Applause.
Please mark as solved, thanks.
Regards X23
@george1421 said in Windows 10 1703 Image with strange issue:
@x23piracy Must have been Tom’s magic pixies that he packed into FOG 1.4.2
I don’t think so 
Today i deployed a mix of different machines and the strange shit is back.
The case is the first user i log on (domain user) has a working office registration and a starting internet explorer, but each other user i logon to that computer has the issue again.
What the hell could this be?
Every new user will be created from the default user, i always use copy profile in unattended.xml so what should cause an issue like that with the problems i talk about only with every user that logs in after the initial one? This is so strange…
Regards X23
@george1421 said in Surface Book won't boot the kernel:
So the question to you is, did a previous version of the kernel work on this surface pro, or is it a new surface pro?
No, this is my first Surface Book i ever tried with FOG, Surface 3/4 Pro are working with ipxe7154.efi
Since this system isn’t registered, you can either manually register and schedule a debug deploy or temporarily add the
I tried to use the MS Surface 3 Pro USB NIC, it’s MAC was already registered to a different system were i used that usb nic for imaging so i just tried to boot to FOS with that registration to another host but it still cannot boot to FOS.
Anyone here who is working with Surface Books?
I don’t think that the Dock’s internals are different to the Surface 4 Pro Docks, they look pretty the same, i cannot swear it’s the same hw inside but i would bet. And i could succesfully a Surface 4 Pro with that Dock.
@Quazz said in Surface Book won't boot the kernel:
edit: Also, if it’s possible to turn of xHCI in BIOS, try that as well.
I can try this tomorrow.
@Tom-Elliott said in Surface Book won't boot the kernel:
Host Kernel is not IPXE Booting.
What else can be done with that option?
@george1421 said in Surface Book won't boot the kernel:
Once there we might issue a
lsusbto see if that external dock is detected.
Boot to shell, then firing a lsusb? Ok, i will do this tomorrow too.
Regards X23
@Quazz Hi, i just change my boot file for uefi from ipxe7154 to ipxe.efi but it’s the same it cannot load the nic to get a network connection. Is one of the available kernels known to work with surface book and its dock?
Regards X23
Hi,
for testing i used the older surface pro 3 usb nic from ms that one was allready registered to another host.
For testing i’ve edited that known hosts kernel to ipxe.efi:
but when i try to boot the surface book it gets ipxe7154.efi instead of ipxe.efi, why?
Hi,
today i got a Surface Book, my default Kernel ist ipxe7154 but it won’t boot up with that kernel.
Since the Surface Book isn’t registered i cannot switch to another kernel within the host definition.
Before i change my DHCP Boot Option temporary, is someone here who can tell me which kernel works?
Is there one?
I am using the original ms dock:
Regards X23
@Tom-Elliott said in Certificate expired FOG Website:
I’ve modified the cron to run every 5 days so this should no longer happen.
with letsencrypt i let the cron job run every 2 months (certs are valid for 90 days).
i would leave the cert server contacts as small as possible, for what should 5 days good for?
Sure, the best way in my mind would be 24 hours before it expires…
Regards X23
Hi,
the cert has been renewed today, maybe a little to late?
Regards X23
Hi,
it’s working again. It wasn’t working with Firefox on PC and with Firefox and Safari on my iPhone.
I used my work computer with edge where i could say hey edge give a f*** on that expired cert.
Hi,
today i receive Cert Errors from Firefox both under Windows and on my iPhone, is it really expired?
Regards X23
@chief i never had this issue but i dont use enterprise of win 10. please show us a screener of the error msg please
@Fernando-Gietz said in Please enter the TFTP issues with Cisco WS-C2960X-48TS-L:
My problems is that the NOC doesn’t want to change the options in the DHCP
did they told you the reason? if the needed dhcp options are not in use why the hell they say no?
Btw. you are facing a problem when a company gets to big and the IT is not sitting completely in one big office.
Corporations / Concerns groups are bad 
Regards X23
Hi,
i would not say that is not possible but it’s a way to much work.
Try to install on a different machine if you need old and new twice for a time.
Regards X23
Hi,
use USB NIC with PXE Support or use @george1421 's FOS USB Stick Image to boot via USB if you find no USB NIC that support PXE.
Regards X23
@x23piracy said in Could not open inode XXXXXX through the library...":
Hi,
before you sysprep try to run chkdsk, if chkdsk was ok run sysprep but don’t use option /reboot or /shutdown just use /quit, then manually shutdown your machine with shutdown -s -t 0 -f, then try to image.
Regards X23
That has worked for the guy here: https://forums.fogproject.org/post/97015
Look for setupact.log and setuperr.log files under the following paths:
C:\Windows\Panther
C:\Windows\Panther\UnattendGC
C:\Windows\System32\sysprep\Panther
Additional log from this post: https://forums.fogproject.org/post/96860
But now, i know all sysprep logs … :
cbs.log
setup.etl
session.xml
setupact.log in Windows folder
setupact.log in Windows\Panther folder
setupact.log in Windows\Panther\unattendGC folder
setupapt.dev in Windows\inf
setupapt.offline in Windows\inf
setuperr in Windows\Panther …
Sysprep places the date and time the image was prepared for duplication in the key HKEY_LOCAL_MACHINE\System\Setup\CloneTag.
Look in the HKEY_LOCAL_MACHINE\System\Setup registry key for a cmdline that reads Setup -newsetup -mini. This places GUI-mode Setup in the Mini-wizard phase.
Check for an HKEY_LOCAL_MACHINE\System\SetupOemDuplicatorString value. This is added using an answer file (Sysprep.inf) for the Mini-Setup Wizard.
Check for the existence of Setupcl.exe. This is the file that changes the Security IDs (SIDs) on the system. Look in the %SystemRoot%\System32 folder for this file.
Hi,
has anyone the knowledge how microsoft may detect a reimaged oem version?
Registry entries, files on filesystem (logs etc.) or other hidden places?
Regards X23
Hi,
before you sysprep try to run chkdsk, if chkdsk was ok run sysprep but don’t use option /reboot or /shutdown just use /quit, then manually shutdown your machine with shutdown -s -t 0 -f, then try to image.
Regards X23
Hi,
before you sysprep try to run chkdsk, if chkdsk was ok run sysprep but don’t use option /reboot or /shutdown just use /quit, then manually shutdown your machine with shutdown -s -t 0 -f, then try to image.
Regards X23
