Hi,
I want to add that I have done some changes in the reports, imaging log report too, to make pre-filters and not shows all the registries.

For example, in the imaging log report you can do a a prefilter by image name, user name or hostname. In this way, the result is more small and you don’t need erase registries in the database.

The new version of the reports are available in the “working” branch

@6rilT Just creating the rule isn’t enough. You need to assign the rule to a role. Users and rules are associated roles.

Name them with the number they require in the group.

Eg 01-snapin, 02-snapin, 03-snapin

@deckerta As well you might want to check out this wiki article: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

It’s all not a click by click thing but I’d say you can learn a lot of things if you are keen to. We’ll definitely help you. Just ask specific questions, post error messages and we sure will be able to guide you the way.

@lepage said in Is it possible using fog to restore only part sda2 ?:

I am not sure if you can see it … but from the filesystem when I do ls d1p* I see
d1p1.img d1p2.img d1p3.img

Absolutely. I know exactly where you are coming from. Yes it would be possible to implement. But can you see it from my perspective as well? Why implement it to enumerate the image files if it holds the truth only in case the image is still captured? Don’t get me wrong. I am not saying it wouldn’t be nice but as of now we have so many other things to fix in FOG and not many people helping that I can’t see us doing this. Sorry!

If you have time and knowledge you are most welcome to add the feature and send a pull request on github. 🙂

@george1421 Mixing up TFTP and HTTP URL here? Might be confusing.

@GrandIQ said:

... http://${fog-ip}/fog/images/...

Please make sure those URLs really work! Simply open them in your web browser and see if it would start the download. I fear it doesn’t because we have some URL rewriting in FOG active for the API backend to work. You probably need to move your images to a different folder further up, like /var/www/html/images/win7/... (URLs: http://${fog-ip}/images/win7/...).

@Fernando-Gietz I like that idea. Even if it is still error prone, it’s make things simpler overall. That could open snapinpack for tarballs too I would suppose.

Short answer: Maybe

Longer answer:
I don’t have the ability to confirm at the moment. But I can tell you that fog does record imaging registered hosts in a mysql table called imaginglog. The part I’m not sure of is if the log only uses an image id to refer to the host being imaged (logical link to the host table) or it saves the actual host name into this table.

The other thing I would have to check is if a host is deleted, is it a soft delete (only marking the host deleted) or does it remove the record. If its a soft delete it would then be possible to create a mysql query to report imaging even if the host record was not visible in the webgui.

The issue is if the host records are removed from the host table and the imaging log only references the host id field, there is no way to tell when a host was imaged since the pointer to the host table would not link to a valid host (since it was removed from the database)

@keith75140 Unfinished images are in /images/dev/... (folder names are client MAC addresses without colons).

@Titione Well then I would go and check for Bad sectors on that disk.

@george1421 what version of MDT are you running btw? I’m on 8450.

@Sebastian-Roth I can assist with the isc-dhcp configuration. I have a box here at home with two NICs I can test on, and I have a couple of spare routers and other spare computers laying around. My availability will be limited Friday through mid next week though, I’m heading out of town to visit the folks.

I went through exactly this problem on my network, I use a Cisco Catalyst 2960 X, which solved it was to configure spanning-tree on all ports, and configure portfast on all but the trunk port (since we use more than one DHCP here). Good Luck!

@strangerthandreams Sorry for the very long delay. I sort of lost track of your post.

I just tried to replicate the issue but for me adding an additional MAC with a leading number does work properly (tried different ones). So possibly this is somehow caused by the browser you use? I used Firefox and Chrome on Debian Linux to test. Which browser/OS do you use? Tried different browsers?

@sudburr that’s where i was confused. I was thinking it would boot uefi no problem, but for whatever reason you needed it to legacy boot for imaging.

@Quazz
I thinks that I fixed the issue somewhere along the way and kept on having a different issue on my debug VM, then when I went to check out that issue, I recognized the fact that I already solved it somewhere… The Physical devices also deploy without issue now;

I’ll still need to confirm that the exact issue is solved, so i’ll be creating a few images and see if they restore out of the box.

Thanks again for the quick support, I’ll mark this thread as solved

edit;
(…if I knew how… )

good job! you are the best.

it seems to work with my VM. I will try with the Opliplex 5260 very soon. I’m not on the same working place today.

thanks
Pierre

@jahilton2002 Partclone is the default for FOG 1.2.0 and later. Partimage is left in the configuration for legacy images so they will deploy correctly with newer releases of FOG.

The next question you might ask is zstd or gzip compression. By default gzip is selected since it has been part of fog imaging for many years. The new compression technology is zstd. zstd is known for having a fast decompression speed as compared to gzip. zstd also creates smaller image files on the fog server. The only down side(s) to fog using zstd:

zstd is a newer compression format than traditional gzip compression. It takes longer to compress the image with zstd than with gzip, but decompression times more than make up for the slower compression times (consider you typically capture once and deploy many times).

So what should you pick? partclone with zstd with compression ratio 11.

Also there are 2 bugs in FOG 1.5.4 that have been patched in the 1.5.5 beta release that have not been back ported to 1.5.4.

Roll the FOS kernels back to 4.15.2 (done in fog setup->kernels). Download both the 64 bit (bzImage) and 32 bit (bzImage32) x86 images. This will fix the 3-5 delay (in some cases) creating the partition table (this issue is being actively worked on by the developers) If you run into an imaging issue with out of memory condition (under rare circumstances) there is another fix that I can tell you about if you run into it.

@Sebastian-Roth
ok I’ll try this as soon as I have a moment.
Don’t remember if i have use –force-https , but sure manually configured https in my virtualhost

@george1421 Thank you!
As a precaution I have created all my images outside A.D

SOLVED