@wayne-workman

Perfect. I already made the script, just didn’t know if it would add the machines to my list or just install the software and then not communicate with the server. Thanks!

Hi,

I have to reimage a lab that I previously thought would be retired in a month (budget got cut). These machines were originally prepared before we were using FOG so they aren’t part of my inventory. If I push the FOG client to them with the MSI via a group policy script will they show up in my pending approval list? I would rather not have to enroll them individually when they’re already out and being used.

@tom-elliott Is this rolled into the master branch now or should i move over to the working branch?

@tom-elliott

Excellent. Glad I’m not just crazy.

Running 1.5.2

I’m reimaging a machine that has already been imaged via FOG in the past. After imaging completes I typically ‘select all’ on the Host Modules Settings page and then all my settings get applied (base image has the client installed). For some reason now when I go to select the module settings it looks like its applied when I hit update but when I refresh the page none of the settings take and are all unchecked again.

Any help would be appreciated.

I’ve just updated to RC12 (didn’t know it was out when I posted) and that is working correctly. So, I guess, Solved?

I am running 1.5.0 RC-11. I have good product keys for both windows 7 and windows 10 enterprise. I have entered them into the host information for my clients but they don’t seem to be applied to the machines after they are imaged. Other FOG functions work like bind to AD and a batch file snapin but this doesn’t seem to work. It had been working correctly in previous releases

Just realized I don’t have any spare machines that use the USB adapter on hand to test. Guess I’m gonna put a pause on this until the next batch of machines come in.

My afternoon was a littler busier than I planned but I have got the unique identifier branch up on a new VM. Any known issues I should be on the lookout for? Gonna try it out with some of our recently retired devices so I don’t mess with my production machines.

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