@jmason I can’t give you a reference on this but it’s actually a likely cause (one that I have not though of before, grrrhhh) that disk enumeration can put your two disks in reverse order. This is known in Linux and usually circumnavigated through persistent block device naming.

Try deploying a couple of times in a row always using the debug mode and run lsblk before starting the task. See if it’s exactly how we imagine it to be (changing disk order).

@xburnerx00 Just got an idea. What size is that ZIP file? Possibly it’s “too big” for the server to handle in a certain amount of time and so it quits the connection. Have you tried a normal snapin (not pack) with let’s ay a one mega byte small executable to deploy to a client via snapin? See if that works.

@Gdelcimp Maybe I get this wrong but it sounds as if you start a normal group deploy instead of a group multicast deploy. I can imagine all of your computers doing single cast anyway. Do you see those 10-12 that start early go pretty much in sync? I mean do they all proceed in very much the same speed and on the same sector/byte count?

Make sure you use this icon (or it’s equivalent in the Basic Tasks) to start a multicast session:

If you are absolutely sure you created a multicast task then you might wanna take a look at the log file. Run tail -f /opt/fog/log/multicast.log in a command sehll on your FOG server before you schedule the session and then keep an eye on the log…

@jmason Well seems clear enough to me, is the source disk larger than the destination disk?

@Gdelcimp Have you ever tried to create a new group, add those hosts you want to image to that group and schedule a multicast deploy task for that group? Do you see the same thing happening when using a group multicast?

@xburnerx00 Hmm, the logs show some interesting things but from what I see I don’t thinks this will lead us to what is causing this.

First let’s try to tackle this from a different angle. Can you please create another snapin but use a simple one this time - not snapin pack. Just to see if that makes a difference. I kind of doubt it, but let’s see.

As well please try following the log files while the client is trying to pull the snapin, just to see if you get any messages in the logs while this is happening. For that have your client ready and use the command to watch the log files on your FOG server: tail -f /var/log/httpd/error_log /var/log/php-fpm/*.log (now hit ENTER a couple of times so you see when new lines of logging come in and schedule a snapin task for the client - check the client logs as well so you know when it happens)

@martial First let me give you a more general answer to your request. FOG came to life when every machine still had an internal ethernet adapter - I know this sounds a bit like dinosaurs roaring but hey - so the MAC address was used as unique identifier of machines.Over the years more and more devices without ethernet came out and we had a first go at switching to a different unique identifier that would be machine specific but not (only) using its MAC address. You can find discussions on this topic in the forums. The end of the story as of now is that we were running into major issues with the other unique identifier and decided to stay with the MAC address for now. It’s a huge change within FOG and we don’t seem to have enough time to go ahead with this change - development, testing, user support… It’s all a big story.

Ok, enough of that, back to the point. Re-using the same ethernet adapter (MAC address) is essentially breaking FOGs logic of identifying machines. I am not sure but I think most people using FOG this way don’t use the fog-client and therefore don’t run into the same issue as you are. Imaging usually works just fine.

I am not saying that AD join is impossible but I have not looked into it myself to have a solution for you at hand. There might be other tools around that can be used to make Windows join a Domain on first boot or something like that.

now I have problems with the security token and repeated mac address

You might also want to take a look at the database entries to see why you seem to have duplicate MAC entries in there. As well please share the full client log so we can have a look. Possibly it’s something else causing the problem.

@jmason How did you schedule the task? Just go to the host’s settings in the web UI, click Basic Tasks, deploy and just before you create the task, tick the checkbox for debug. This way it very similar to a non-debug deploy but the difference is that you have to start manually (by running the very simple command fog - should work if you schedule the task as described!) and you are asked to step through the whole process instead of it going without interaction. Give it a try.

If you have scheduled the task as described already, then I am wondering if you do PXE boot the laptop or USB boot?!

@Taspharel Have you searched the forums for “rcu_sched” yet?

@totoro Sounds like you have a rough DHCP server somewhere in your network! Read about this topic on the web and try to find it.

Yes it’s true, but the message is the same,

I am fairly sure the IP address is also different!!! Next time post your own picture!