Every beta tester gets its own unique ID key to activate the beta... but this all can be turned off by editing the registry
Microsoft has ratcheted up the security in the latest build of the Windows XP, which went up on Microsoft's FTP servers last night, and on the 'unofficial' FTP servers shortly afterwards. But it's a virtual ratchet, largely - according to the build 2428 release notes that escaped along with (of course) the code, each technical beta tester is being assigned a unique installation product key in order to unlock the build.
But then the notes go on to tell us that the build has a registry key that can be used to disable the product activation in this build. So although you've got a unique key that can be tracked back to you (possibly...), you don't actually need to use it anyway. Previous leaked builds have been accompanied by various patches and workarounds that deal with the product activation technology, but with 2428 Microsoft is saving these, er, misguided enthusiasts the effort by putting the workaround in the release notes.
So what's the use? Well they say it is for "getting them used to the idea of protection, in preparation for the actuality" ... So who will know what protection will be made in future releases.
They will not use the registry key trick in the future, microsoft says. But i doubt something like that will be shut down completely, because OEM resellers always get an universal key to install the product.
We will see. ISO images of this beta are already all over the web.
Source: The Register
