Thursday, November 18, 2004

Generic Product Keys

Deploying Windows XP Using Windows Product Activation

All of the examples provided above used a beta key for illustration purposes. The product keys listed in this section can be used with any of the answer files and scripted examples. They are blocked at the Microsoft clearinghouse and therefore cannot be used to activate any systems. They provide a number of days (assume 14 days) for you to complete the activation process.

It is absolutely essential that you use the correct type of key, which is a function of the platform type and the media. Choose the key and corresponding sequence number for your scripts from the following table:

Generic Product Keys

Applicability
Product Key
Sequence Number

Whistler Tech Beta Program
(All Platforms)
PXRQ3-7VPMV-CQWXR-8Y4KX-RD786
010053298

Windows XP
Home Edition
Full product
JKTVX-HCRXC-J2YC9-MX3K4-G9X26
005037750

Windows XP
Home Edition
Upgrade
C84VB-JYVFD-P7HF4-6KKRJ-7M6XH
010000182

Windows XP Professional
Full product
DR8GV-C8V6J-BYXHG-7PYJR-DB66Y
005072760

Windows XP Professional
Upgrade
FKTW8-Q7MJ7-JK6GW-9J9RV-HC3C2
010000212

Windows XP
Home Edition
System Builder (Full)
KGVXT-F9HVW-XGW9X-QVYVX-HQ9RD
120000613

Windows XP Professional
System Builder (Full)
TTGHK-3RC33-BT9DR-3BVYV-BTQ98
120000607


Original Link : http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/wpadepl.mspx
Unlocking WinXP's setupp.ini

WinXP's setupp.ini controls how the CD acts. IE is it an OEM version or retail? First, find your setupp.ini file in the i386 directory on your WinXP CD. Open it up, it'll look something like this:

ExtraData=707A667567736F696F697911AE7E05
Pid=55034000

The Pid value is what we're interested in. What's there now looks like a standard default. There are special numbers that determine if it's a retail, oem, or volume license edition. First, we break down that number into two parts. The first five digits determines how the CD will behave, ie is it a retail cd that lets you clean install or upgrade, or an oem cd that only lets you perform a clean install? The last three digits determines what CD key it will accept. You are able to mix and match these values. For example you could make a WinXP cd that acted like a retail cd, yet accepted OEM keys.

Now, for the actual values. Remember the first and last values are interchangable, but usually you'd keep them as a pair:

Retail = 51882 335
Volume License = 51883 270
OEM = 82503 OEM
So if you wanted a retail CD that took retail keys, the last line of your setupp.ini file would read:

Pid=51882335

And if you wanted a retail CD that took OEM keys, you'd use:

Pid=51882OEM

Note that this does NOT get rid of WinXP's activation. Changing the Pid to a Volume License will not bypass activation. You must have a volume license (corporate) key to do so.

Just some random screenshots:
Here we have an OEM version of WinXP letting us know we can't upgrade:















Remove Saved Passwords

Windows XP offers the ability to save passwords for web sites and network resources. This can be very convenient as opposed to remembering and entering the username and password each time you need access, but it poses a security risk because anyone who has physical access to your computer would also be able to log into those sites using your saved credentials. While biometrics and other user authentication methods have become more widely used and accepted in recent years, the prevailing method of user athentication remains the username and password. Users have passwords to access their computer, shared network resources, web sites, business applications and other resources.
Different sites and applications have different policies regarding how to create the passwords and standard security practices suggest that users should use a different and unique password for each login. For many users it becomes unruly to recall the various usernames and passwords and they may write them down on a notepad in their desk drawer or put it on a sticky note on their monitor so they can remember them all. Of course, anyone else can also come along and read the passwords as well.
Windows XP offers users the ability to retain passwords so that the authentication information required to login is automatically pre-populated when the different sites or resources are accessed rather than the user having to enter them each time. Because this requires being logged into the computer in the first place it provides some convenience for the user while remaining more secure than writing everything on a sticky note on the monitor. Unfortunately, it is still counter-productive from a security perspective because anyone who sits down at the computer while it is logged in or gains access to your computer user account will subsequently be able to access all of the various sites and resources as if they were the user because of the cached login credentials.
Windows XP does not offer a very easy way to review or remove the saved passwords though. If you follow the steps below though you can access a graphical interface to add, remove or edit the saved passwords on a given system.

1. Click Start and select Run
2. In the Open field type "rundll32.exe keymgr.dll, KRShowKeyMgr"
3. Once the Stored Usernames and Passwords interface opens you can select any of the entries and select Properties to view the existing information
4. To remove a saved password you can select one of the entries and select Remove. A confirmation screen will appear. Click on OK and the account will be removed
5. You can add additional saved passwords as well by clicking on the Add button and entering the appropriate information
6. Repeat the steps above as needed to add, remove or edit saved passwords
7. When you are done using the interface click the Close button

Tony Bradley is a consultant and writer with a focus on network security, antivirus and incident response. He is the About.com Guide for Internet / Network Security (http://netsecurity.about.com), providing a broad range of information security tips, advice, reviews and information. Tony also contributes frequently to other industry publications. For a complete list of his freelance contributions you can visit Essential Computer Security (http://www.tonybradley.com).