Only used to be if the following situation applies:
"Note In WSUS 3.0, the client changes its SusClientID if the hardware configuration changes. For Windows Vista, for Windows Server 2008, and for later versions, Sysprep is changed to reset the SusClientID. Therefore, this problem affects only virtual machines that run pre-Windows Vista operating systems, or that were not created by using Sysprep."
So for systems that are hosted in VMware or HyperV this can still be a big problem, especially with pre-Vista/2008 sysprep. Your suggestion does not help him diagnose the issue to see if it is something as simple as a failure in GPO settings.
