Best posts made by Wayne Workman

@LPetelik said in Images are not deleting:

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.

That’s by design. Image Management’s ‘List All’ area is the only area in FOG where the image data is purposely not deleted. Why? It’s just potentially too destructive to have such a feature delete image data too, I.E. to just select all and click delete… and poof, all images gone.

If you want to delete the image definition and the data too, you must go into the image’s definition by clicking on it’s name, and then deleting it in there, there’s a spot on the left for it labeled as “Delete”.

@TomBagley You could ask him to modify it to support fog. We have very detailed guides in the wiki. Please pass these two links to your network manager:

https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG

https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@tywyn the largest difference is that SYSTEM is not allowed (by design) any interaction with the user or userspace at all. This probably also means the user’s account too. This is Microsoft’s design, not ours - and they went that route for security reasons.

When developing snapins, if your snapin will work manually but not as a fog snapin (and you’re sure you deployed the snapin correctly), you can normally assume the problem is because of the above.

Try what @Avaryan posted.

I would also of course buy one. I’d want the new official FOG logo to be somewhere on it though. Or even the fog cloud from the top left of the fog web interface (one without the version in it).

Also, the link to the purchase should probably be made prominent on the forums & wiki.

@Tom-Elliott can you point out what minimal stuff there is? I’d like to learn about it and improve documentation.

I think this isn’t the right forums for this problem. This is not a FOG related problem. If I were you, I’d probably throw the hard disk into the trashcan and get a new one.

@Roger-Saffle Documentation is one way. Helping others in the forums is another. I spend about 15 minutes in the mornings and 5 or 10 minutes at lunch during weekdays reviewing new posts to see what I know enough about to help with. Others could do the same. Of course I put a lot more time in during evenings and weekends.

@Junkhacker This looks promising… and it’s open source.

Regshot is an open-source (LGPL) registry compare utility that allows you to quickly take a snapshot of your registry and then compare it with a second one - done after doing system changes or installing a new software product.
https://sourceforge.net/projects/regshot/

@sebastian-roth said in Windows 7 Image:

You’re saying Ghost can do BitLocked partitions in resizeable mode?

It can’t. Since Ghost is a file-level cloning solution (as opposed to an imaging solution), I question if it can handle bitlocker at all.

This is what Joe is talking about. Took me a while to figure it out when I started having FOG based scripts start accessing network resources. So these pictures should help you not waste hours on it.

@phil_guy It’s not a linux or fog question. When the computer turns on, you usually hit F2 to enter the BIOS. On some HPs, it’s the Esc key, for Lenovos it’s usually the Enter key. Then just compare each item line for line on both the golden machine and target machine.

@imagingmaster21 said in Image Not Capturing:

It says not enough disk space, but there is definately enough space.

Please look at the output of this command on your fog server: df -h Look for partitions with 99% or 100% used.

@x23piracy https://wiki.fogproject.org/wiki/index.php?title=Testimonials

@GoodGuyQ Looks like your images aren’t completing the FTP move at the end of the image capture. Can you try out the FTP testing part in this article? https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

@imagingmaster21 If one can capture but not another, it’s definitely something about the system not working. What sort of disk does it have in it? What is the NIC model? Is it BIOS or UEFI?

This isn’t done yet but it will likely help you:
https://wiki.fogproject.org/wiki/index.php?title=Surface_Pro

There must have been a windows update that changed this.

Early Hostname Changer was working perfectly fine before.

We need to really figure out what’s going on. I’ll see if I can replicate tonight.

I had that problem once. You just have to modify your DHCP settings on your dhcp server to not have the WDS stuff in it. When you need it, you can put it back.

For future readers: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@yochaigal Can you check for a firmware update for this troublesome target host?