@Tom-Elliott Cool thanks and it works nice i just need to pre-pend numbers to the front to dictate order and everything works.

@ch3i Too bad if it was sorted by name you could put numbers in front of your package names to indicate order

I would be curious how the underlying code figures out which snapin to install first ?

Is there anyway to modify the order of snapin installs? I have a couple that need to go first before others?

@Tom-Elliott Version 7007

If i save the username as test\test it works on the first pass. I am not sure if this changes anything but i was setting the user/password at the global level. and the group level I never set it at the host level. I would also get it to work once then image the system and after the image it would begin failing.

That seems to do the trick Thanks

using user@domain seems to give an error 87 which i noticed someone else was having problems with earlier.

The instructions i read online Had the username in the domain\userformat so i thought that was required

I am noticing a behavior in the current trunk where, when Join Active directory is used the Domain username is getting mangled.
when the domain username is entered “Domain\AdminUser” and saved after an image the name becomes “Domain\\AdminUser” and fails to join the domain with an error code 2202 which is “The specified username is invalid.” after a few more images it then becomes “Domain\\\\AdminUser” and just continues growing. When you first save the Credentials the first time the join works but after that it fails. because of the mangled username.
The OS I am Trying to Join is Windows 10