Posts made by astrugatch

@sebastian-roth

Thanks. I’ll roll up a VM after lunch and give this a look.

This is great to hear. And yes I do have a virtualization platform where I can test a new build. Can I just:

git clone https://github.com/fogproject/fogproject.git trunk/; git checkout unique-identifier; cd unique-identifier/bin/

sudo ./installfog.sh

@george1421

Hi, Sorry if I wasn’t clear. I’m currently on the dev-branch and running 1.5.0RC10 but I see in GitHub a branch for a unique identifier (ie NOT the ethernet MAC). The goal is to enroll our incoming devices but be able to simply use a handful of ethernet adapters instead of maintaining a list of adapters that are paired with computers for MAC address identification.

Just wanted to see if the unique identifier branch is in a place that is ready for testing. I would like to try it / move to it before our next batch of devices come in. Maintaining pairings of USB adapters to computers is a huge pain when they’re not always being used by the end user.

@tom-elliott This is the part I didn’t know when I restarted. Im back on 1.5 and good now.

I deleted trunk again. Downloaded the git from scratch again and got the RC this time. I’m just not sure what happened the last time. I was already on DEV-branch. Whatever. I’m where I need to be now.

It installed 1.4.4 and I got the old UI. But after doing that and switching branches again (weird as I was already on dev-branch) I’m getting the 1.5.0 RC10 installer again. No idea what happened.

I’ve already tried this. I was already on the dev-branch which is why I’m confused.

I was already on the dev-branch. I was on RC9, thats why I’m confused. Heck I even deleted trunk and re downloaded:

git clone https://github.com/fogproject/fogproject.git fog_1.5.0/

and I’m still getting a 1.4.4 installer

I put this in linux problems too but I’m not sure if this is a better spot

Went to update to the latest version of FOG and did a git pull and it seems to have installed 1.4.4 instead of the new RC. Did I miss a change in the update process?

Went to update to the latest version of FOG and did a git pull and it seems to have installed 1.4.4 instead of the new RC. Did I miss a change in the update process?

@george1421 but like I said I don’t really need both. Just UEFI. The handful of clients we have already images can be set back to EFI boot unless it’s easier to do both.

@george1421 Windows Server 2012 R2

I am trying to make changes for our DHCP server so we can start booting machines via UEFI instead of enabling legacy boot for each machine we want to add to FOG. I se some resources like the BIOS and UEFI Co-Existing wiki and the Filename information wiki, but I but the BIOS instructions seem to start in the middle of the process assuming you know what file to put in option 67. We currently have undionly.kpxe as option 67 and it is working for legacy booting. Should this be changed to make UEFI devices work? I’m not concerned with breaking legacy boot as all the devices we currently have support UEFI and are only legacy booting because I didn’t have time to investigate this before deploying the machines. I would like to get this sorted before our next big batch of machines comes in.

Got it working. This can be marked as solved.

@sebastian-roth

Didn’t refresh the page before I posted that. I see it now. Thanks!

OK. Now I have it installed. I don’t see where I make the template groups and hosts or define groups or hosts as templates and make those associations.

I am looking to add the persistent groups plugin to my install of 1.5. I have found some forum posts about persistent groups but can’t find instructions on how to install it.