@Brenth453

I’m currently running on Ubuntu 18.04, you can also check @Wayne-Workman 's fog build site to see what at least is installing correctly. (I don’t have the link handy but I’m sure he can give it to you)

@fry_p

All the pieces are free. You can use NGINX or apache2 as a load balancer (there are other free purpose specific options as well), the fog front end is obviously already free, as is MySQL / mariaDB as well as memcached. JAMF isn’t free I’m just using their configuration as an example of how this would be done. They operate in much the same way FOG does with clients checking into a frontend that’s backed by a DB.

@fry_p

Might be a good idea to look at how JAMF does this. Its a similar setup with a HTTP loadbalancer -> multiple front ends (Tomcat in their case) -> a single SQL DB + a memcache server

@george1421

It can boot iso images. So I guess this would be a pretty good route to take. Is there a guide for making a bootable usb/cd in the wiki?

@Sebastian-Roth

How do I see my current kernel version?

bzImage Version: 4.19.48
bzImage32 Version: 4.19.48

I know this is going to be a long shot but has anyone PXE booted successfully in XCP-ng using EFI boot? I get the FOS menu to come up but after I select any option i get the init loading then a black screen. Monitoring in Xcp center shows nothing is happening (no processing or network traffic).

EDIT

As a note booting with BIOS enabled in Xen works fine but I am trying to use it to create base images for EFI machines that will be running in EFI. I used to do this in VirtualBox by switching back and forth between EFI and BIOS when capturing images, but I would like to do this work off my laptop and central so I don’t have to be tied to a location to do the work.

@rathan While you can. You shouldn’t. Apple has made imaging a dead workflow through a number of things, the most important being the T2 chip preventing netboot/external boot. MDM and DEP is the appropriate way to now provision MacOS devices. Erasing would be done via CMD+R in recovery or by pushing an erase and install from your MDM.

@Sebastian-Roth I make all my EFI images in virtual box. My workflow has me enable efi. Do the base install and when I go to pxe I switch off efi and do my capture. The os is still an efi os and won’t boot in vbox until you reenable efi. Has worked fine for me with images going back to windows 7 all the way up to our current testing of 1903

@Sebastian-Roth
Works fine for me on all the flavors of 10 we use. LTSB LTSC and 1703 1803

@merrittw

What tools are you using to manage your linux infrastructure.

I know Ubuntu is the bane of FOG devs but we use it in our environment because i can push updates regularly to all our hosts with Landscape.

@Tom-Elliott

I guess I just see this as a UI quirk. I’ve found typically with radio buttons that are linked its one or the other and not removeable, and for a situation like this would just have a none option rather than be removed.

In the Snapins pane the selection for “reboot after” and “shutdown after” are radio buttons, which make it seem as though it’s an either/or choice, but you can click on one and it gets unselected. Could these be switched to checkboxes?

@Sebastian-Roth

Of course I go back to take a picture to share and it works 100% right away no error… Not sure what happened.

Got it to happen again. And after this I couldn’t even see the nic in the PXE menu. Starting to think this is a machine / usb adapter issue not a FOG issue. Here’s the screenshot anyway:

Need to use a USBC network adapter to do an image for a new machine. On startup to PXE I start to get USB errors asking if the cable is bad, then tells me that it’s likely missing the driver for the nic.
I can update my kernel but I want to make sure I’m picking the correct one.
Also my PXE was built for HTTPS so I don’t know if I would need to run the builder again or if the kernel is updated separately.

Thanks!

@Sebastian-Roth

After resetting encryption data all the modules seem to work except for User Tracker

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 9/17/2019 3:06 PM Client-Info Client Version: 0.11.16
 9/17/2019 3:06 PM Client-Info Client OS:      Windows
 9/17/2019 3:06 PM Client-Info Server Version: 1.5.7
 9/17/2019 3:06 PM Middleware::Response Success
------------------------------------------------------------------------------

 9/17/2019 3:06 PM Service Sleeping for 142 seconds
 9/17/2019 3:09 PM Middleware::Communication URL: https://fog.spfk12.org/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 9/17/2019 3:09 PM Middleware::Response Success
 9/17/2019 3:09 PM Middleware::Communication URL: https://fog.spfk12.org/fog/management/index.php?sub=requestClientInfo&mac=1C:4D:70:E4:56:98|1C:4D:70:E4:56:97|1C:4D:70:E4:56:9B||00:00:00:00:00:00:00:E0&newService&json
 9/17/2019 3:09 PM Middleware::Response Success
 9/17/2019 3:09 PM Middleware::Communication URL: https://fog.spfk12.org/fog/service/getversion.php?clientver&newService&json
 9/17/2019 3:09 PM Middleware::Communication URL: https://fog.spfk12.org/fog/service/getversion.php?newService&json

 9/17/2019 3:09 PM Service Creating user agent cache
 9/17/2019 3:09 PM Middleware::Response Module is disabled globally on the FOG server
 9/17/2019 3:09 PM Middleware::Response Module is disabled globally on the FOG server
 9/17/2019 3:09 PM Middleware::Response Module is disabled globally on the FOG server

Everything I see in the GUI says that it is enabled, Service settings on the client have it enabled, on the group it is a member of it is enabled, under service configuration its enabled, and under fog settings it is enabled

EDIT

Disregard all of that. The logins show up despite this output.

@Quazz

They’re not static so finding the IP would be a pain. I’m going to reset encryption data and see how that goes.

@Sebastian-Roth

Got into one of the shares and see this:

 9/17/2019 11:22 AM Client-Info Client Version: 0.11.16
 9/17/2019 11:22 AM Client-Info Client OS:      Windows
 9/17/2019 11:22 AM Client-Info Server Version: 1.5.7
 9/17/2019 11:22 AM Middleware::Response ERROR: Unable to get subsection
 9/17/2019 11:22 AM Middleware::Response ERROR: Object reference not set to an instance of an object.
 9/17/2019 11:22 AM Service Sleeping for 151 seconds

@Sebastian-Roth

Not sure why I am seeing this,

fogadmin@fogimaging:/var/log/apache2$ ls
access.log        access.log.2.gz  access.log.9.gz  error.log.14.gz  error.log.8.gz                 other_vhosts_access.log.13.gz  other_vhosts_access.log.7.gz
access.log.1      access.log.3.gz  error.log        error.log.2.gz   error.log.9.gz                 other_vhosts_access.log.14.gz  other_vhosts_access.log.8.gz
access.log.10.gz  access.log.4.gz  error.log.1      error.log.3.gz   other_vhosts_access.log        other_vhosts_access.log.2.gz   other_vhosts_access.log.9.gz
access.log.11.gz  access.log.5.gz  error.log.10.gz  error.log.4.gz   other_vhosts_access.log.1      other_vhosts_access.log.3.gz
access.log.12.gz  access.log.6.gz  error.log.11.gz  error.log.5.gz   other_vhosts_access.log.10.gz  other_vhosts_access.log.4.gz
access.log.13.gz  access.log.7.gz  error.log.12.gz  error.log.6.gz   other_vhosts_access.log.11.gz  other_vhosts_access.log.5.gz
access.log.14.gz  access.log.8.gz  error.log.13.gz  error.log.7.gz   other_vhosts_access.log.12.gz  other_vhosts_access.log.6.gz
fogadmin@fogimaging:/var/log/apache2$ sudo grep "x.x.x.x" access_log | tail
grep: access_log: No such file or directory

Is there a way to see the last time one of my enrolled computers communicated with FOG? I have some machines that seem. have stopped communicating and I don’t have a good way of confirming if that’s true or not short of sending a snapin and waiting to see if succeeds.

@Pikmin

Just as a question what installer did you use for 18.04.3

When installing Ubuntu Server make sure to use the ISO that ends in “18.04.3-server-amd64” NOT the ISO that they automatically offer up which ends in “18.04.3-live-server-amd64” That ISO doesn’t contain some of the standard repos.
Here’s the link if anyone needs it:

http://cdimage.ubuntu.com/releases/18.04.3/release/ubuntu-18.04.3-server-amd64.iso
You CAN use the live iso but then you need to make sure to add universe & multiverse