Speaking to a friend today who Deals with M$ has informed me of some news that i think you guys should know. the KeyGen floating around that everyone and there mother must have by now, will in fact not work with the corp edition. It will however work on the Reg Pro and Home edition, at least for now. Reason it will not work for the Corp is cause of the fact that M$ Does leep track of all the VLK's it issues. And when the RTM Sp1 comes out it will deny you access to windows update..and might even lock your computer out forcing a reinstall..however M$ will likly not inculde the latter jus incase it wacks a legit comp...so to tell you the truth if your comp is working fine, sp1 is totally uneccessary. M$ lkeeps track of the VLK's it issues to its mass customers, and if you update to sp1 and your generated copy does not match there internal Database..well then you out in the cold without a coat.

The reason SP1 works now with the generated keys is due in part to the fact that it is still a beta, and has only some of the security features implemented..but not all of them. when the final release comes out it will be a diffrent animal than what you see today. M$ closely monitors all forums and records any keys posted (generated ones) and uses our own forums against us, and as guinea pigs. Eventually it is said that they will monitor home and reg pro keys, but for now its logistcally impossible.

People who use exsisting corp keys live another day simply because M$ will not go to their mass customers and tell them or issue them a new key..it would cost M$ too much $ in manhours it would have to pay its mass customers to change there keys in their exsisting systems (surely you dont think the customer will pay for M$'s dream of a secure WPA) at least not yet.

There is already talk that Longhorn will not incorporate the debackle known as WPA. M$ will eventually downplay WPA cause its a fight that cannot be won...my long time saying of "if it can be written, it can be cracked" comes to mind...ever since win 3.1 to now, History and the future is in the techies favor..M$ will have to rethink its strategy, the more limitations it places on a user and or the price increases just breeds and dares pp to crack them...and with linux fast approaching M$ should choose its battles wisely..

Food for thought The internet plays a great role in M$ troubles , cause back in the early 90's the internet was not what it is today, meaning if you were a techie and cracked windows or pirated it, it was kept relatively to your circle, now the internet has made the world a lot smaller and a lot more complicated for M$...maybe this is why thier focus is the internet now....Think about it

However the keygen is not the once thought of silver lining for all the techies.

There's no way they can keep track of every key sitting on shelves or unactivated copies around the world, and there's no way they can ban a whole list of possible "generated keys" from a key gen using a randomization setup that can output virtually unlimited results.

Besides, there'll be a cracked SP1 release (with all cdkeys unbanned) a week before M$ even release thier official version.

General keys and VLK keys are 2 diffrent things. a general key can be generated, a VLK (volume license key) is for multiple installs, therefore are accounted for. This only applies to pp with Corp editions

well here I am responding to your thread using a corporate version of xp pro and a generated key with sp1 installed and all the windows updates installed......I guess I'm dreaming..........

Take the time and READ my post correctly, i stated that it (generated keys) works on the BETA which is out now...i was referring to the Final release of sp1...never hurts to read.

I want to try more Keys I generated. I did the xpfix with kegen and changing the OOBETImer in the registry as the NFO said.

Now that sp1 beat is installed i woudl like to try to deactivate registration and try another key i have generated.

is ther any easy way of doing this? More than one wayof doing this?

THanks

Does anyone know of a way to change a corp version into thinking it's a regular install? I know that you can tell Windows that it's not activated through a quick bit of reg hacking, but presumably the regular Pro keys will not be accepted by the Corp version. Any way to switch to the regular Pro without a reinstall?

Cheers,

AJC

I know the FCKGW key will be affected. However, if we have another corp key that is being used by a coproration, how can MS just shut that one off. Won't that affect the actual corporation that's using the key and tries to update all their computers?

thats the thing the ones in exsistence today are fine, M$ will not ask their exsisting customers to redo the key on all their systems, would cost them too much money. Its the generated ones that might pose the problem being that it would not match their encrypted database that is to be implemented in the final release....but there is no reason to worry, my post was souly to give a heads up, and be informed rather than act like a deer in headlights come final release time.

Just remember my saying..."If it can be written, i can be cracked"

Well if you chose to archive your files when you were downloading SP1, you should just be able to unistall sp1 beta and do the fix all over again.
Though i wouldnt recommend unistalling sp1 cause a s we all know M$ never makes anything that completely unistalls...lol

I tried to just change the value in the OOBETimer to any value than what was already there then ran the "%systemroot%\system32\oobe\msoobe.exe /a" again and I was able to enter a new key I genrated but none of the Corp keys woulr work. Not even ones I generated after the SP1 was installed I generated more keys with the keygen and none of the corp keys would work. Not one.

Now this is ironic . I decied to try PRO keys. I was susspecting that the Service pack may have done something to the Corp Devils own copy and made it back somehow to Pro. I think it did or something similiar.

I was able to generate Pro keys and it accepted the pRO kEY i GENERATED. oNLY PROBLEM IS IT WANTED ME TO ACTIVATE WINDOWS THOUGH.

I did not do this of course.


Now this is really werid, After I re-booted something happened. SOmewhere along the way the original key "key I entered before the SP1 update" was back. And I did not have to activate windows.

So changing the value in the OOBETImer after the XPFIX and install of SP1beta for some reason it will not allow you to change the Corp key. And if you do it puts back the one that was there.

That probably becuase you dont have the corp pro edition, you have the regular pro edition, and thus will not accept VLK's. Also another clue that u do not have the corp is that the corp pro does not include activation.

Sorry if I forgot to mention that. No its defintely something happening after a SP1 beat install. It time bombs or does somethign to Corp edition. Devils Own copy I think!!!

Devilsown is the CORP EDITION!!

True Devilsown is the Corp, but then why are u getting the activation screen, corps dont have activation