@Thiago I think that’s what I needed to know.

If you need the directory listing, you might be better creating an index.php file that will generate the list of files for you.

You can even make them links so you could test downloads.

The idea is we use an API now and if the index file doesn’t exist (which it’s attempting to locate) it will attempt to redirect through the API. I just needed clarity on whether there was an actual issue of which you just let us know there wasn’t. It was just your “testing” that was failing (which is helpful, but not requried).

@Wayne-Workman Both on the same switch, tested with another computers (it’s a lab with 20) and always the second returns No session found with that name.
If i do multicast via groups, it works with no problems.
I can use it creating a multicast group and join all the computers that i need to deploy.
Just curious to see if any other has the same problem… 🙂

For further clarification to future readers of this thread, the specific commands to allow the necessary ports for Multicast can be found in the CentOS 7 wiki article, linked below.
https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

@Quazz
Now it works with 7zip too.
Definitely something went wrong at last time.

@Thiago I’ve been working on the SnapinPacks wiki article, it may interest you seeing that you have 30-some-odd things that need deployed. Perhaps you can contribute your notes if you give SnapinPacks a shot?
https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks

@Tom-Elliott
My image was created with trunk version and what you said about d1 files work for me. Thanks a lot to all!

@GoodGuyQ While this issue has been fixed back then I think it never really got tested by the users (who are a hell lot better at finding the odd bits and pieces that we developers just don’t think about)!! Would be awesome if you can give it a try and let us know. Be aware that things might go wrong. So always keep a full image at hand.

That said you could also do things like skipping only one partition out of three (and still do the MBR) by renaming the image files on your FOG server. Try renaming /image/<image-name>/d1p2.img for example to skip_d1p2.img and it should be skipped while deploying. At least it worked in older revisions. Let’s hope I didn’t break that when working out the single partition cloning stuff.

Looking forward to hear if it is working for you!

@Tom-Elliott It’s working now!!
The upload process took “horrible” 15 minutes, and i was forced to drink a coffee…(everything is a reason for a coffee 🙂 )
After uploaded a new image, d1.mbr was created.
The image was sucessfully created and deployed.
Thanks again.

@Thiago It’s all good. Don’t feel like you did anything wrong. It’s why we asked the questions we did, and now we know why the problem occurred, and it made me ensure the code base was good to go too.

@george1421
we have a few images. my script mount directly (i.e. mount /dev/sda2 /windows)
The problem is: now, our server will be used by another department with other config (i only know that they have 4 parts, using mbr) and sometimes the image name can change, disk layout too.
I like your idea and wanna let things more generalized as possible.
in any case, this is temporary until standardize all
Thanks a lot

@EAHarvey lol. He’s been a user here for two years.

3006 should’ve fixed this, but better to use 3009 as I found a few other issues.

Rebuilding web side of services to be a cross-plataform is a great idea.
About the time-frame, this should not be a problem.
““this will be done when it is done”” 🙂
Thanks

SOLVED!

This is a O.S. issue.

Changing advanced plan settings for Energy Options, solved the problem.