I figured it out with your help. Thank you for your help.

I am not sure why the code changed after I changed the AD username/password in fog settings, because it seems the host continued to use the original. This was seen under the host->active directory. I added all 50 computers to a group and changed the setting for the group which changed the settings for all 50 hosts. It seems like the global setting should have done this, but it didn’t.

I figured it out with your help. Thank you for your help.

I am not sure why the code changed after I changed the AD username/password in fog settings, because it seems the host continued to use the original. This was seen under the host->active directory. I added all 50 computers to a group and changed the setting for the group which changed the settings for all 50 hosts. It seems like the global setting should have done this, but it didn’t.

I checked the AD setting on the individual host in fog. Despite me changing the AD username and password in the fog settings, it did not change it on pre-existing hosts. Can i make a blanket change?

I looked at the link you gave me, but it says it is due to a disabled account. The original account that was being used was disabled, but the new account works. I have added computers to the domain using this account. Is it possible the computers are still using the old account?

I have not been able to find what this error code is referencing. I imaged about 50 computers and found none of them added to domain. The original code was 1909 which I found was due to a bad username and password for AD. After fixing the username and password, the error switched to 1331. I confirmed the new username and password works. Where can i find what this code is referencing?

@Sebastian-Roth This is exactly what it was. I feel a little embarrassed haha. Thank you for your help

so to clarify, I am imaging 6 groups of computers, with each group having about 36 computers. Each group I register to fog, then when it asks if I want to image now I select no. I then create a group in fog, move the 36 computers that were just registered to that new group, schedule the task, then turn the 36 computers on. They then go through the process of getting to the multicast group but about 10-12 of them start almost immedialy, and the rest are put in a que for singlecast.

Its interesting because the rest obviously see that they were scheduled to be imaged with the rest of the group, but somehow end up in singlecast.

@Sebastian-Roth You mean just try the same thing, but with a newly created group? I have not tried to create a new group and reimage the same computers, but each time image a group of computers I create a new group for those computers. I see the same thing happen with each group.

I am running version 1.5.5 and each time I create a multicast group and schedule a task for those computers (36+/-) fog starts to image the first dozen or so without waiting for the others. The rest end up in a que and I end up forcing them to start. They then image in singlecast. I have extended the UDPMAXWAIT to 1000 but there is no change. I can’t find anything on this issue and I am not sure what logs to look at. Any help is appresciated.