@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 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.

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

UEFI BIOS on the Zenbook still doesn’t recognize the USB-to-Ethernet adapter,

FWIW: To get this to work, you need network adapters supported by your hardwares UEFI firmware. Think of uefi as a very limited operating system. If it doesn’t have the drivers built in, then it can’t initialize the device. So if you want to pxe boot on that zenbook you need to contact the manufacturer to find out what usb network adapters are supported by the firmware … or … just boot fos from the usb stick and move on to the next problem.

@ttrammell
It looks like something similar when I had changed the IP and didn’t finish configuring everything. I had left out checking and configuring the Storage group/nodes.
If you have changed your IP(or maybe even Server name) try following these instructions:
https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address
The key part I missed(becasue I didn’t really use storage nodes) was:

Update the IP address for the storage node on the FOG system where you changed the IP address - Web Interface -> Storage Management
Make sure you actually click the node and check the IP setting.

that line in the bandwith.php file points to a location in /sys/class/net/<net_adapter_name>/operstate

I’m not sure if CentOS is diferent but my adapter name is eth0 so look for that in place of adapter name.
Im not sure if you can simply recreate it it if it doesn’t exist. It simply appears to display whether or not your adapter is up or not.

I also found this article but refers more to the fog client install.
https://forums.fogproject.org/topic/5926/change-fog-server-name

Hope that helps,
Jason

@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.

Alright, I’ll look into that.

Thanks, guys!

@alwos Two comments.

Please open your own thread because your problem may not be the same. If you are more happy, use your native language to explain the problem because your post is not understandable.

@Wayne-Workman said in Rudimentary Shell Script - SVN Update for CentOS 6.7:

The best suggestion still stands though - move to CentOS 7. There’s no reason not to, it’s a free and open OS.

I would be totally for it, although this server does nothing but sit there and run fog – which is what a server is supposed to do, now that I think about it.

That main reason is redoing the hardware RAID and making sure that is all set right as rain, and that all of our images make the transfer. It’s one of those too much to do in too little of a time frame – I mean this server has been here about 4 years before I got this position and it was still running FOG .29 (While the most updated version was 1.2.0).

More or less, I am stuck with it for the time being.

In place upgrade probably should not mess anything up, but the should is what I am skeptical about.

Can you show us the logs verbatim then? You’re not seeing the exact same error if it’s not saying ‘ftp_login incorrect’