KACE Product Support

It may be that you're deploying x64 Win7 and the version of WSNAME built into the naming rule is incompatible/unsupported on that architecture.
Try downloading the latest WSNAME from:http://mystuff.clarke.co.nz/MyStuff/wsname.asp
and uploading it to a new "Application" task (as opposed to naming rule.)
Even if it's not the 64-bit issue it's likely worthwhile to try the new one anyhow.

I'll try that in the morning. I was using a variant of a batch file that copied a source folder over and used it to name the machine and add it to the domain, that I found here on the forums. I just edited it to only do the naming part. However we have been finding that it has been working after we stripped everything out of the scripted install. It works great until I add a script I made using powershell to add it to the domain, even though there are 2 reboots between the naming script and the one to add it to the domain. Not sure why adding that 2 reboots later would cause it not to name the machine. I don't know why I never thought of adding it as an application task, since it is an exe file. I already downloaded the newest version. I'll try it tomorrow, and let you know how it goes.