Posts made by ttrammell

@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

George got me going on a working a FOS he made; will play with what he has given me, since it’s only throwing common problems at me now. Will update the post when I have more.

@george1421 said in Asus ZenBook Flip UX360U - PXE Assistance Needed:

If iPXE doesn’t support your hardware, pxe booting may be out of the question. Imaging with fog doesn’t absolutely require iPXE, it just makes imaging a bit cleaner.

I’ll have to get back with you on this one, with how I managed to get the option, but one of the above allowed me to press CTRL-B to access the PXE shell-- I just don’t know anything about how to use the shell, so I couldn’t do anything.

I’ll give all the options a go one more time and pass along some proper documentation on each attempt, because I tried them all, got flustered, and flung myself at the forum.

From a windows computer, can you get the hardware id of this network adapter?

Give me a moment; booting into the OS.

@george1421 said in Asus ZenBook Flip UX360U - PXE Assistance Needed:

@ttrammell Do you get the same error message when using the stock FOG supplied version of ipxe.efi?

I do, although I believe it adds on to it “No devices found”, or something along those lines. I will need to retry that method to be sure, but it was only a one-liner addition with that exact wording or very similar.

And just to be clear this device IS a uefi device?

As far as I am aware. I have been unable to find anywhere to enable Legacy ROM settings.

• Networking Stack: Enabled

• IPv4 PXE Support: Enabled

• IPv6 PXE Support: Disabled

• Secure Boot: Disabled

• Fast Boot: Disabled

• CSM Support: Enabled

• Launch PXE OpROM policy: Enabled

• Legacy ROM Settings: Cannot find at all.

• All I/O Security: Unlocked

@george1421 said in Asus ZenBook Flip UX360U - PXE Assistance Needed:

Lets start at the basics.
Are you able to pxe boot into the FOG iPXE menu?

I am not.

@george1421 said in Asus ZenBook Flip UX360U - PXE Assistance Needed:

Can you get it to the point where it gets an IP address but fails to download the NBF file?
What precisely doesn’t work (screen shots of the error gladly accepted).

All I am currently getting as of right now, following the iPXE create your own from source method:

Okay, I have a Asus ZenBook Flip, and have tried several times to make this machine talk to our FOG server.

I do not know if it is the USB-to-Ethernet adapter or not, which is why I am making this post.

So far, Microsoft Surfaces using the Microsoft USB-to-Ethernet adapter-- Model 1663-- have worked perfectly fine, so I figured I would try it on the Asus Zenbook. At first, I just assumed that I was doing something incorrectly and spent about the past three hours trying various different methods in an attempt to make it talk to our server:

• Following the USB Bootable Media guide: https://wiki.fogproject.org/wiki/index.php?title=USB_Bootable_Media
• Trying to make a bootable USB on ROM-o-matic: https://rom-o-matic.eu/
• Even tried “making a source file” from iPXE: http://ipxe.org/download

All of which to no avail. So, from the only other post on this forum that mentions an Asus Zenbook, they mentioned a Dell USB 3.0 (which I am going to assume is this: http://accessories.dell.com/sna/products/Cables_Hubs_Adapters/productdetail.aspx?c=ca&l=en&s=niso&cs=caniso1&sku=443-BBBD)
If it is, great; if not, can someone link me the right one.

I guess what I am trying to express is, I don’t know how to image this computer.
I don’t know if I need to be looking for UEFI firmware for the Microsoft USB-to-Ethernet adapter to make it recognize the device, and I don’t know if everything I did before is wrong.

Anyone have an idea on the right direction to be taking this?

Line 82 of bandwidth.php:
$content = file_get_contents($operstateFile);

Server

• FOG Version: 1.4.0
• OS: CentOS 7 (I finally upgraded it.)

Description

GENERAL ERRORS.

That’s my question.

I migrated data from a CentOS 6.8 FOG Server to a CentOS 7 FOG Server. It works, slightly finicky with the web-browser, but it’s working none the less.

I really don’t know if this is a FOG Problem or a General Problem, but…

This is the error logs (20, newest first) I am getting from apache error log:

[Fri May 19 10:22:12.193922 2017] [:error] [pid 849] [client a_client_ip:54077] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/commons/init.php on line 386, referer: http://fogserver_ip/fog/management/?node=report
[Fri May 19 10:17:33.958887 2017] [:error] [pid 683] [client fogserver_ip:36748] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:32.956452 2017] [:error] [pid 27991] [client fogserver_ip:36746] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:31.955974 2017] [:error] [pid 28078] [client fogserver_ip:36742] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:30.960323 2017] [:error] [pid 32556] [client fogserver_ip:36740] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:30.026246 2017] [:error] [pid 27933] [client fogserver_ip:36736] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:28.959993 2017] [:error] [pid 849] [client fogserver_ip:36732] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:27.956126 2017] [:error] [pid 28078] [client fogserver_ip:36728] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:26.955837 2017] [:error] [pid 27956] [client fogserver_ip:36726] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:25.954564 2017] [:error] [pid 27956] [client fogserver_ip:36722] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:25.028088 2017] [:error] [pid 27991] [client fogserver_ip:36720] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:23.954783 2017] [:error] [pid 27933] [client fogserver_ip:36714] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:22.961567 2017] [:error] [pid 1750] [client fogserver_ip:36712] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:21.956506 2017] [:error] [pid 1750] [client fogserver_ip:36708] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:20.957756 2017] [:error] [pid 27956] [client fogserver_ip:36704] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:20.027640 2017] [:error] [pid 1750] [client fogserver_ip:36700] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:19.076232 2017] [:error] [pid 32556] [client fogserver_ip:36696] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:17.956355 2017] [:error] [pid 1556] [client fogserver_ip:36692] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:16.954977 2017] [:error] [pid 28078] [client fogserver_ip:36690] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82
[Fri May 19 10:17:15.954731 2017] [:error] [pid 849] [client fogserver_ip:36686] PHP Warning: file_get_contents(/sys/class/net/bonding_masters/operstate): failed to open stream: No such file or directory in /var/www/html/fog/status/bandwidth.php on line 82

Apache SSL Error Logs

[Fri May 19 08:35:51.323306 2017] [ssl:warn] [pid 27656] AH01909: RSA certificate configured for testbed.my.domain:443 does NOT include an ID which matches the server name
[Fri May 19 08:35:51.279747 2017] [ssl:warn] [pid 27656] AH01909: RSA certificate configured for testbed.my.domain:443 does NOT include an ID which matches the server name
[Fri May 19 08:32:57.968283 2017] [ssl:warn] [pid 23866] AH01909: RSA certificate configured for testbed.my.domain:443 does NOT include an ID which matches the server name
[Fri May 19 08:32:57.923736 2017] [ssl:warn] [pid 23866] AH01909: RSA certificate configured for testbed.my.domain:443 does NOT include an ID which matches the server name

And I don’t know if this is really needed, but these are the PHP-FPM error logs:

[19-May-2017 10:14:51] NOTICE: systemd monitor interval set to 10000ms
[19-May-2017 10:14:51] NOTICE: ready to handle connections
[19-May-2017 10:14:51] NOTICE: fpm is running, pid 27924
[19-May-2017 10:14:45] NOTICE: exiting, bye-bye!
[19-May-2017 10:14:45] NOTICE: Terminating ...
[19-May-2017 09:45:16] NOTICE: systemd monitor interval set to 10000ms
[19-May-2017 09:45:16] NOTICE: ready to handle connections
[19-May-2017 09:45:16] NOTICE: fpm is running, pid 6133
[19-May-2017 09:45:02] NOTICE: exiting, bye-bye!
[19-May-2017 09:45:02] NOTICE: Terminating ...
[19-May-2017 09:40:39] NOTICE: systemd monitor interval set to 10000ms
[19-May-2017 09:40:39] NOTICE: ready to handle connections
[19-May-2017 09:40:39] NOTICE: fpm is running, pid 1177
[19-May-2017 09:38:05] NOTICE: exiting, bye-bye!
[19-May-2017 09:38:05] NOTICE: Terminating ...
[19-May-2017 09:27:50] NOTICE: systemd monitor interval set to 10000ms
[19-May-2017 09:27:50] NOTICE: ready to handle connections
[19-May-2017 09:27:50] NOTICE: fpm is running, pid 3398
[19-May-2017 09:27:24] NOTICE: exiting, bye-bye!
[19-May-2017 09:27:24] NOTICE: Terminating ...

First question would be:

DO I NEED TO WORRY ABOUT THIS?

If it’s a no, then I won’t bother with it.

If it’s a yes, then the second question would be: What do I do?
Because this stuff is WELL above my experience level.

@Wayne-Workman I may have miss-configured or did something incorrectly then; the very first time I tried RAW with this dual-boot system, it did not work.

Currently, the ‘Current Setup’ I stated in the last comment does in-fact work - in my scenario.

I have successfully managed to image two machines, although it takes upwards of eight hours; however, a day to image a machine beats five days of needing to rebuild the system every time something happens to it.

Side notes though:

• You need the MacOS disk, or access to the Macintosh partition to enable the bless so you can image it (as per the FOG Wiki)
• After you image it, the PXE menu shows back up; return to the main menu, refresh to populate the Macintosh Partition into the menu. Boot into the Macintosh Partition and put in the Windows CD, then run BootCamp. Do not erase the partition, just run the Windows Installer.
  • Doing this ‘unlocks’ the Windows partition, so you don’t actually have to go into the Windows Installation Disc - just let it boot past that and into Windows.
  • Configure Windows like you normally would. FOG does not change the hostname on this side of the partition, so make sure you change that when and if you are putting the computer on the domain.

Beyond that, it works. Ain’t perfect, but it is about 210% better than what I was doing before - even with the additional side stuff you have to do before and after the image hits.

So, I will call it closed.

UPDATE: I may have it working; will test on other machines (So far, it managed to install the image and have both partitions).

Current Setup is:
OS: Apple Mac OS - (8)
Image Type: Raw Image (Sector by Sector, DD, Slow)
Partition: Everything
Image Manager: Partclone Zstd

I have a few more machines to test this on before I can say, “Yes, this worked.” Will update in a few days.

@Tom-Elliott This is what I just got when I tried it again under Other/Single Disk All Paritions (Non-Resizable)/Gzip 200MB

Same error as before (Sorry, just now posting it):
Error trying to restore GPT partition tables (restorePartitionTablesAndBootLoaders)
Args Passed: /dev/sda 1 /images/MacU 99 all
CMD Tried: sgdisk -gel /images/MacU/d1.mbr /dev/sda
Exit returned code: 2

I’ll do a bit more testing.