Snap Deploy 5 Domain Join issue

I am posting this because we spent about a week with a support ticket open and the solution was so simple it left me shaking my head.

Setup: One AD Domain controller (Windows Server 2012R2), 20 domain PCs (windows 7), all identical hardware, being used by the general public in a public library setting. Induvial machine settings used to put the same name on the same machine each time.

Problem: Machines being imaged with the master image are coming up imaged with the correct name on the PC side, but are joining the domain on the servers AD side as the name of the machine the master image was taken from. So..... if the master was taken from PUB1, and deployed to PUB2.... PUB2 comes up as PUB2 and appears to be joined to the domaon correctly, but shows that it joined the domain as PUB1. This was repeated many many MANY times in testing trying to find the issue. It did not matter if the master image was taken with the machine joined to the domain or not.

Solution: Because we were using the individual machine settings to override the PC name, it was left BLANK in the template at some point. Putting a name in the template PUB{1} resolved the issue instantly upon the next test of the imaging. Once it was added, the PUB1 image was applied to PUB2 correctly and PUB2 joined the domain as PUB2. 

Special thanks to Andrey, the Expert Level Support Engineer who helped me figure this out inside 25 mins! 

Thanx

Chris