This was an issue when I worked with WSUS a couple years ago. I know there is workaround to run a batch file to reset the IDs, but has a better solution created? Has an updated Windows Update Agent or updated Sysprep tool or anything else solved the issue? Is it only an issue with third party cloning tools like Ghost or does Microsoft's own cloning solutions such as ImageX/WDS etc. have the same issue of not stripping or resetting the WSUS client ID?
Seems like the issue should be solved at the source rather than doing workarounds as shown in the link below forever: