@george1421 Hey, I just wanted to let you know that your FOS just saved me from going POSTAL.

I have successfully managed to upload and download an image; UEFI BIOS on the Zenbook still doesn’t recognize the USB-to-Ethernet adapter, but as soon as it boots into the FOS it recognizes it and works like a charm.

Cannot thank you enough for making this extremely simple and straightforward, even with the hiccup of the USB-to-Ethernet MAC being bound to one machine-- that’s not your fault, that’s just a hurdle that’ll come to pass by the sound of where the FOG Project is going-- even with that, really simple and straightforward.

Putting your FOS tutorial as a link for this topic: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image

@george1421
Yeah, I am bad at that.

So, we had an issue when we ordered SL3s - we couldn’t Capture an image from them, we would get an error on Capture about BitLocker needing to be disabled.

SL3s didn’t have a TPM setting in BIOS that you would normally turn off (They have Secure Boot), like you would do for a normal UEFI setup on say a Dell E6410 - so I searched around and came across that.

The two CMD commands:

powercfg -h off
shutdown /s /t 0

I’ve been using those for years now, because of the Sticky-bit issue and the Hibernation reason is lost to time - maybe it also had something to do with Sticky-bit, but I dont’ recall.

The two new commands for Powershell:

Disable-TpmAutoProvisoning
Clear-Tpm

This is all entirely for the purpose of disabling TPM like how you would in BIOS.
I don’t think doing the same thing on a Dell E6410 running Windows 10 would work - I would assume you would still need to disable TPM in the BIOS, but I have not tested that.

So if you had a device, like a Surface Laptop 3, that had the issue where TPM isn’t in the BIOS then hopefully clearing the TPM settings in Windows itself before Capturing the image fixes the issue - as it did for me.

So, problem: Cannot Capture an Image from an SL3: No TPM in the BIOS; keeps getting BitLocker error.
Solution: Disabling TPM in Windows via Powershell worked to Capture the image; no BitLocker error.

Hopefully that is a less confusing explanation of the post.

@tom-elliott
Normally I always disable TPM and Secure Boot before Imaging a machine - whether Capture or Deploy.

The fact that TPM wasn’t in the BIOS got me started on this, and disabling TPM worked like normal when the PS commands were run.

The issue with that command - I just ran it on the machine I Deployed to. BitLocker was never enabled - I get this error:

ERROR: An error occurred (code 0x80310008):
BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker.

Looked at BitLocker through Control Panel? Turned off.
Right-clicked the <C: > drive in “This PC”? Asks if you want to Enable it.

That’s why I was looking for TPM and not BitLocker.

EDIT:
I know I said “machine I Deployed to”. I didn’t have BitLocker enabled on the machine I Captured - my fix was disabling TPM.

@george1421
Yeah, I am bad at that.

So, we had an issue when we ordered SL3s - we couldn’t Capture an image from them, we would get an error on Capture about BitLocker needing to be disabled.

SL3s didn’t have a TPM setting in BIOS that you would normally turn off (They have Secure Boot), like you would do for a normal UEFI setup on say a Dell E6410 - so I searched around and came across that.

The two CMD commands:

powercfg -h off
shutdown /s /t 0

I’ve been using those for years now, because of the Sticky-bit issue and the Hibernation reason is lost to time - maybe it also had something to do with Sticky-bit, but I dont’ recall.

The two new commands for Powershell:

Disable-TpmAutoProvisoning
Clear-Tpm

This is all entirely for the purpose of disabling TPM like how you would in BIOS.
I don’t think doing the same thing on a Dell E6410 running Windows 10 would work - I would assume you would still need to disable TPM in the BIOS, but I have not tested that.

So if you had a device, like a Surface Laptop 3, that had the issue where TPM isn’t in the BIOS then hopefully clearing the TPM settings in Windows itself before Capturing the image fixes the issue - as it did for me.

So, problem: Cannot Capture an Image from an SL3: No TPM in the BIOS; keeps getting BitLocker error.
Solution: Disabling TPM in Windows via Powershell worked to Capture the image; no BitLocker error.

Hopefully that is a less confusing explanation of the post.

Apparently Microsoft has disabled TPM from their newer hardware since January 30, 2020 - as per this response: https://answers.microsoft.com/en-us/surface/forum/surflaptop3-surfsec/surface-laptop-3-no-tpm-settings-in-eufi/20c5a568-606e-40cf-a136-efd4e08dc35b

We haven’t had a problem with previous devices (SP4 and SL2 works fine) - it just so happens that we bought SL3s recently, and this was the immediate problem.

I was about to ask if anyone had an issue with this, but now I’m just throwing this up here for the sake of knowledge.

Apparently the work around for this is to perform everything you normally would
(I recommend disabling TPM from Powershell because you don’t have to reboot the machine to clear the TPM settings):

CMD > powercfg -h off             # Disable Hibernation
PS  > Disable-TpmAutoProvisioning # New (Doesn't need restart)
PS  > Clear-Tpm                   # New (Doesn't need restart)
CMD > shutdown /s /t 0            # Shutdown Computer to prevent Sticky-bit

Clearing TPM and disabling Secure Boot in the BIOS for UEFI still works like a charm.

Microsoft TPM PS Commands: https://docs.microsoft.com/en-us/powershell/module/trustedplatformmodule/?view=win10-ps

Anyways, hope you all are having a good one.

EDIT:
To clear up confusion, because the post may be hard to read. This is in referrence to Microsoft removing TPM from their BIOS. This is a work around that worked for me on a Surface Laptop 3 by disabling TPM while inside the Windows OS.

I have Windows 10 machines; I have several, ranging from standard Dell desktops and laptops to Surface Pro and Surface Laptops. Any way you cut it, I make an image and put Microsoft Office 2016 on it, but after downloading it to another machine it winds up as a Microsoft Office 365 install.

Does anyone know why this is, if there is something that I can delete to prevent this, or if I should just push out an installer through snap-ins, or just install Office 2016 after imaging.

@george1421 said in Microsoft Surface Go - USB-C to Ethernet Adapter Compatibility:

Just be aware I only gave you the 64 bit kernel. So the step you did above will break a 32 bit computer.

Gotcha.

If everything works OK with bzImage4186 you can leave it in the bzImage place. The only thing that is different is I added the microsoft nic. With the next release of the official FOG kernel they will add in the new Microsoft NIC.

I’ll leave it under bzImage4186 until the next release. We don’t have any other machine right now that uses a USB-C NIC Adapter, so it should be fine.

Sorry, I just now got around the checking it.

It works, but there’s a few extra steps I had to do to get it working.

# Move it up to the server
scp C:\bzImage4186 root@127.0.0.1:/var/www/html/fog/service/ipxe/bzImage4186
# Log onto the server, and make it usable
...
cd /var/www/html/fog/service/ipxe/
chmod +x bzImage4186
# Backup the old kernel files
mv bzImage bzImage.bak
mv bzImage32 bzImage.bak
# Move bzImage4186 to a usable state so I can boot up the device
mv bzImage4186 bzImage
# This is just so I had bases covered
cp bzImage bzImage32
# Boot the device, register it in FOG, overwrite the kernel host arguments like you said
# then move everything back to the way it was
rm bzImage32
mv bzImage bzImage4186
mv bzImage.bak bzImage
mv bzImage32.bak bzImage32

This is just the recorded steps I took, but I can image it now, so thanks for the quick-fix @george1421!

@george1421 said in Microsoft Surface Go - USB-C to Ethernet Adapter Compatibility:

So this needs to be added and FOS recompiled.

I may be mistaken by what you are saying here, but I am not using FOS-- this is straight network connection.

Here’s the picture:

I can’t get a picture right now, but there are only two under what @Sebastian-Roth asked for:

Surface Ethernet Adapter Properties
Hardware Ids
USB/VID_045E&PID_0927&REV_3100
USB/VID_045E&PID_0927

I have a Microsoft Surface Go, and I was wondering if there was compatibility for it in the works; the only reason why I am asking is due to the code block down below.

I have tried:

• Kernel - 4.18.3 TomElliott 64
• Kernel - 4.18.3 TomElliott arm
• Kernel - 4.18.3 TomElliott arm64
• Boot Method - ipxe.efi

Should I try messing with the different boot files (i.e. undionly.kpxe), or is there someway that I can help a kernel update (based on the code block), or is there something in the works and it would be better if I just wait a few days/weeks?

I only have about two of these things (right now, at least), so building up two from scratch versus getting an image for one right now isn’t a complete hassle.

The Model is: JWL-00001 [3.0 USB-C to Ethernet Adapter]

db_root: cannot open: /etc/target
Starting logging: OK
Populating /dev using udev: udevd[2831]: error creating epoll fd: Function not implemented
done
Initializing random number generator... done.
No network interfaces found, your kernel is most probably missing the correct driver!
Please check your network setup and try again!
...
Verifying network interface configuration.......failed
No network interfaces found (verifyNetworkConnection)
...

@george1421 Hey, I just wanted to let you know that your FOS just saved me from going POSTAL.

I have successfully managed to upload and download an image; UEFI BIOS on the Zenbook still doesn’t recognize the USB-to-Ethernet adapter, but as soon as it boots into the FOS it recognizes it and works like a charm.

Cannot thank you enough for making this extremely simple and straightforward, even with the hiccup of the USB-to-Ethernet MAC being bound to one machine-- that’s not your fault, that’s just a hurdle that’ll come to pass by the sound of where the FOG Project is going-- even with that, really simple and straightforward.

Putting your FOS tutorial as a link for this topic: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image