Best posts made by LPetelik

This is solved from a FOG point of view.

The problem was that a user replicated several large images overnight and Hyper-V expanded the VM, choking the main servers.

Thank you for all of your help @Sebastian-Roth!

SORT OF SOLVED

She is using Chrome, cleaned the history, cookies, app data. I was able to delete so I asked her to show me her steps.

I had her log into FOG management using my machine to delete an image. She was going into an image edit panel, unprotecting it, updating then back at the list of all images, checking the box to the right of the name and clicking to delete the image at the bottom of the screen, authenticating at the prompt, etc and finding it was only deleting the name of the image, not the file on the server.

I was going into the edit of the image, unprotecting the image, updating then clicking delete from the Image menu. It then shows a checkbox to delete the data. I had her do it that way and it worked as expected. The image name and the data deleted.

This is specific to the background image to the boot menu and the banner.
Please see: https://forums.fogproject.org/topic/6935/lenovo-7303

Thank you!

@xx23piracy Good catch!

I reviewed them and yes, they are laptops. I tracked one down and yes, it is adding MAC addresses that it previously didn’t have a record for. It just worried me because the hosts already existed and have been there for a while then it all the sudden started adding all these extra addresses.

So…resolved it looks like. Thanks!

@Tom-Elliott said in Organizations Using FOG:

Organization Name: Ferguson-Florissant School District
Location (Optional) Admin Offices are in Florissant, MO
Approximate Number of systems: 2021 clients for Elementary, Middle and Aux Sites running on 1 master with 15 aux nodes. Plus about 1800 clients at 3 High Schools running on separate masters.
How long: about 9 months.

It would be great to be able to tell when a task was set while looking at the Task Management tab. I deal with several users on different nodes that don’t always go back and clear out failed/aborted tasks. I’d like to be able to confidently clear them and not be concerned that I’m clearing a newly created task instead.

Are all of your nodes on the same FOG versions? From what I understand SQL gets a bit fussy if they aren’t.

Our district had an issue that caused us to need to roll back some to previous VM snapshots. Some of the nodes went to considerably older versions. As I updated the master, the management became terribly slow. We removed the bad nodes to later rebuild and started updating the rest. While it’s not back to normal, it is better.

With that said, following for more solutions.

@wayne-workman Thanks. I changed it to 15 minutes. I’ll see how that does.