FYI Purge didn’t work for me. just reporting back. Don’t want to hijack the thread so I’m just going to watch and see what we find out.
Posts
-
RE: Issues after upgrading to 16.04
-
RE: Issues after upgrading to 16.04
I’m trying the purge now. I will report back.
-
So this /IMAGES/DEV folder?
So is this something that can be cleared out? Mines approx 400 gigs in it. I would like to empty this out and get this back if possible.
-
RE: Bootable USB drive to re-image a machine
Roger that. Kinda of what I was thinking.
-
Bootable USB drive to re-image a machine
So basically I want to create a external drive that a client could plug into the machine. Boot to it and it would deploy a FOG image. For example, lets say I have a client on a Vessel and they have messed up the system beyond repair. Anything could have happend. I want them to be able to plug in this drive, reboot the machine and boot to it, and it re-image the machine with the original image. Is this something that FOG can do?
Thanks in advance!!
-
RE: Updating Image and then capture
@Sebastian-Roth Interesting. The name through the web interface is Acer_DualBoot_Final but it says the location is /images/Acer.
-
RE: Updating Image and then capture
Let me say that i did make a new Image name (AcerDualBootFinalB) and recaptured that one and it was right. Seems to be in the overwriting maybe?
-
Updating Image and then capture
So this is what I am seeing. I have my dualboot laptop that I fully update(Windows, program updates etc). I then recapture the image to the original name that is assigned to the existing image. For example my image name is AcerDualBootFinal. So when i recapture the image I just capture it to that name in the hopes that FOG will overwrite with the new data.
The issue I am seeing is that when I deploy said image to another machine, only the first partition has the updates, the second Is the same as it was prior to the update.
This is a single disk/ multi partition image due to the dual boot nature of the image. Compression is set at 2. I am running FOG 7881.
Anybody seen this before?
-
RE: New machines not finding PXE info
My bad. I see it’s pulling an address.
-
RE: New machines not finding PXE info
@EAHarvey My server will sometimes do this and not give address.
-
RE: New machines not finding PXE info
Reboot your server or restart your DHCP service.
-
RE: Since the latest update, FOG seems to not be renaming.
@Tom-Elliott ok roger that. Thanks so much.
-
RE: Since the latest update, FOG seems to not be renaming.
So I have updated this morning and it seems to be renaming correctly. What exactly was the issue?
-
RE: Since the latest update, FOG seems to not be renaming.
@x23piracy 7597. Let me update and see what happens. I’ve not updated since we started this.
-
RE: Since the latest update, FOG seems to not be renaming.
Still did not change.