Topics created by Joe Gill

@Joe-Gill glad you found a quick fix. I’ll keep this ticket open though, as it points to a deeper issue in the client: PrinterManager has a thread safety issue.

@sebastian-roth

I ended up switching from the dev-branch to the working branch and re-ran the installer. Everything worked fine.

Tested and updated this morning. Works fine. Thank you guys.

@joe-gill well done.

Added in working.

@Sebastian-Roth
@Tom-Elliott

I just updated to RC4… I’ll keep you all posted! Thanks!

@Tom-Elliott

Updated to Working branch and everything looks good! I’ll report back on the other issues I reported earlier. Thank you!! 🙂

@Tom-Elliott

It’s funny, I noticed it a bit later after I posted this. 🙂 It’s looking good though!

@Tom-Elliott

No problem. Yes it does prompt to update. Thanks!!

@Tom-Elliott

So I figured out where I’m seeing this…

I created a new test group… Added members to the group… Removed members from the group. Everything works there.

When I go into an existing group… (One created in older versions of FOG…) It does not delete the members from the group.

Hope that helps!

@Wayne-Workman

So after much frustration, here is what I came up with!!

Set FOG to Only Assigned Printers…
Delete all current printers…
Set FOG to FOG Managed Printers…
Re-Add Printers…
Reboot PC.
Voila! The new driver is added and you’re good to go!!!

So FOG CAN do it. 🙂

For the amount of headache I just spent on trying to figure out GPO to enable scripting. Testing script and getting everything to work… The above is much simpler…

For what it’s worth… I did find a link to your script. You had given it to me once before also. LOL!

https://forums.fogproject.org/topic/8406/fog-client-printer-not-displaying

Thanks!

I don’t know that I consider this a bug as it doesn’t break functionality. I suppose, by technical senses, it IS a bug.

Either way, fixed in working branch now.

If you must see this, please run:

wget -O /var/www/fog/management/default/fog.css https://raw.githubusercontent.com/FOGProject/fogproject/406c89e5522ae0e2f7398432dd4f3186fb13c982/packages/web/management/css/default/fog.css

@Tom-Elliott

Yes sir! Things are working well! I’ve multicasted several machines this afternoon without a hitch. Yay! Thanks!!

@Tom-Elliott
Thanks Tom! I’ll check that out. That sounds like it could be the issue!

I’m rebuilding the FOG Server today! 🙂
Everything is set to go. I backed up all of my images locally. We migrated to a new physical server. So this is a brand new install. I’m going with Debian.

@Sebastian-Roth

Thanks for helping me on this one!!

I finally got it!!! I made those adjustments… BOOM! It worked! 🙂

@Tom-Elliott

The resolution here was the following…

My image WAS corrupt. It DID image just fine with UniCast. I remade my image and all is happy. I also made an adjustment to the resize option on my image. I set it to be resizeable.

I’m all going good now. All is happy. 🙂

Just in time for my server upgrade!! I’ll be installing Debian here in the next couple days…

Cheers!!!

Joe Gill
Townsend K-12 Schools

This sort of exists already, but in reverse. you can set the primary groups of images individually, and select many groups.

@Joe-Gill said in Chromebooks Refreshing Protocol:

Yes we do Enterprise enrollment via Google Admin.

Can you “Power Wash” them remotely?

Thanks!

Device management --> Chrome --> Device Settings --> User Data
alt text

This pretty much takes everything off of them as soon as the user signs out.

@Joe-Gill said in PXE Boot Problems:

I can boot the same machine type from another segment of our network fine as well.

For the first picture: So why should it be an iPXE issue then? This sounds really weird. Is this issue reproducible?

For the second picture: I suppose this model does not properly PXE boot in a different network segment, right? As George said, try different iPXE binaries (find them /tftpboot on your server) to see if one of them works…