This article describes how to determine the channel that your copy of Microsoft Windows Server 2003 was obtained through. This article also describes the characteristics that distinguish the product when it is obtained through these different channels. The channels include the following:

•	Retail
•	Evaluation
•	Volume licensing programs
•	OEM
•	Checked build

Back to the top

Channels

The following list describes the five channels:

Retail

Software that is obtained as a retail product typically includes a CD that comes in a shrink-wrapped box. This form of media is purchased from a retail store or other software retailer. It includes a copy of the software that includes all the features the product is supposed to have.

Evaluation

Evaluation software typically is only available as a download. Evaluation software contains a mechanism that counts down to an expiration date after you install the software. After the evaluation copy expires, the operating system restarts every hour with a warning. Or, the operating system does not let you log on. The symptom depends on the expiration timer that was triggered. There are two expiration triggers, and both timers can be triggered at the same time. Evaluation copies of server software have a time limit of 180 days.

Volume licensing programs

Volume licensing programs at Microsoft include the Select Licensing program, the Enterprise Agreement Licensing program, the Open License program, and the Service Provider Licensing Agreement (SPLA) program. Volume licenses are not available for operating systems. Volume licenses are only available for software upgrades.

OEM

An OEM is a vendor that supplies computer hardware. An OEM can provide versions of Windows Server 2003 that are customized to its customers. Software that is obtained through an OEM is typically preinstalled on the computer, but it may also be provided on a CD that accompanies the hardware.

Checked build

Software that is obtained as a checked build contains debug binaries. Debug binaries are different from production binaries because they contain additional information that helps you troubleshoot a server installation. Checked-build software is delivered through development channels like the Microsoft Developer Network (MSDN).

Back to the top

Determining the channel

To determine the channel that your software was obtained through, use the winver command. Or, view the volume label.

Use the winver command

You can type the winver command at the command prompt to determine the channel that your copy of Windows Server 2003 was obtained through. The information that this command provides describes the version of Windows Server 2003 that is running. If the copy of Windows is an evaluation copy, the winver command provides detailed information about the evaluation period.

View the volume label

You can use volume labels to determine the channel that your copy of Windows Server 2003 was obtained through. To view a volume label, follow these steps:

1.	Insert the CD into the CD drive. Note Close the Windows Server 2003 Setup program if it starts.
2.	Right-click Start, and then click Explore.
3.	Right-click the drive that contains the Windows Server 2003 CD, and then click Properties.
4.	The volume label is displayed on the General tab.

The following table lists Windows Server 2003 media volume labels.

Product	Volume Label
R2 Datacenter x86	BX2DVOL_EN
Datacenter IA-64	AX2DiVOL_EN
R2 Datacenter x64	BX2DxVOL_EN
Enterprise Edition 32-bit retail	NRMEFPP_EN
Enterprise Edition 32-bit volume licensing	NRMEVOL_EN
Enterprise Edition 32-bit OEM	NRMEOEM_EN
Enterprise Edition 32-bit evaluation	NRMEEVL_EN
Enterprise Edition 32-bit checked build	NRMECHK_EN
Datacenter Edition 32-bit retail	NRMDFPP_EN
Datacenter Edition 32-bit OEM	NRMDOEM_EN
Standard Edition 32-bit retail	NRMSFPP_EN
Standard Edition 32-bit volume licensing	NRMSVOL_EN
Standard Edition 32-bit  OEM	NRMSOEM_EN
Standard Edition 32-bit evaluation	NRMSEVL_EN
Web Edition 32-bit retail	NRMWFPP_EN
Web Edition 32-bit volume licensing	NRMWVOL_EN
Web Edition 32-bit OEM	NRMWOEM_EN
Web Edition 32-bit evaluation	NRMWEVL_EN
Enterprise Edition 64-bit retail	NRMEIFPP_EN
Enterprise Edition 64-bit volume licensing	NRMEIVOL_EN
Enterprise Edition 64-bit OEM	NRMEIOEM_EN
Enterprise Edition 64-bit evaluation	NRMEIEVL_EN
Enterprise Edition 64-bit checked Build	NRMEICHK_EN
Datacenter Edition 64-bit retail	NRMDIFPP_EN
Datacenter Edition 64-bit OEM	NRMDIOEM_EN

Back to the top

Help files

The Help files that come with software from an OEM may be different than the Help files that come with software that you obtain through another channel. Help files can direct you to Microsoft or to the OEM for support. The Help files from the OEM are customized by the OEM according to the OPK Users Guide before the OEM provides the software to its customers.

Back to the top

Windows Product Activation

Windows Product Activation (WPA) is implemented in all 32-bit versions of Windows Server 2003 products. WPA does not apply to 64-bit versions. WPA requires every computer that is running Windows Server 2003 to activate the product. If you are using software and Product Keys that were obtained through a volume licensing program, you can bypass WPA.

Back to the top

Product IDs

All Windows Server 2003 products require the end user to type a Product Key during installation. A unique Product ID (PID) is generated when you run the Windows Server 2003 Setup program. After the Product Key is validated in the Setup program, the Setup program builds the 20-digit PID. The PID is assigned to the computer. A PID contains the following information:

•	The first five characters of the PID indicate the Microsoft Product Code (MPC).
•	The three characters after the MPC indicate the channel ID.

The following table lists the English MPC codes for Windows Server 2003.

Product and Channel	WPA	MPC	Expiration date
R2 Datacenter x86	No	69754	No
Datacenter IA-64	No	69769	No
R2 Datacenter x64	No	76871	No
Enterprise Edition 32-bit retail	Yes	69713	No
Enterprise Edition 32-bit volume licensing	No	69713	No
Enterprise Edition 32-bit OEM	Yes (see note)	69713	No
Enterprise Edition 32-bit evaluation	Yes	69763	Yes
Enterprise Edition 32-bit checked build	Yes	69713	No
Datacenter Edition 32-bit retail	Yes	69754	No
Datacenter Edition 32-bit OEM	Yes	69754	No
Standard Edition 32-bit retail	Yes	69712	No
Standard Edition 32-bit volume licensing	No	69712	No
Standard Edition 32-bit  OEM	Yes (see note)	69712	No
Standard Edition 32-bit evaluation	Yes	69763	Yes
Web Edition 32-bit retail	Yes	69753	No
Web Edition 32-bit volume licensing	No	69753	No
Web Edition 32-bit OEM	Yes (see note)	69753	No
Web Edition 32-bit evaluation	Yes	69763	Yes
Enterprise Edition 64-bit retail	No	69770	No
Enterprise Edition 64-bit volume licensing	No	69770	No
Enterprise Edition 64-bit OEM	No	69770	No
Enterprise Edition 64-bit evaluation	No	69763	No
Enterprise Edition 64-bit checked build	No	69770	No
Datacenter Edition 64-bit retail	No	69769	No
Datacenter Edition 64-bit OEM	No	69769	No

Note There are two types of OEM vendors. Royalty OEM vendors can distribute Windows products by using System-Locked Preinstallation (SLP) Product Keys so that end users can bypass product activations. All other OEM vendors distribute Windows products by using the standard Product Keys that require the user to activate the Windows products.

The following table lists the channel ID values for Windows Server 2003.

Channel	Channel ID
Volume licensing	640
OEM	OEM
Other channels	000

To view the PID of a computer that is running, follow these steps:

1.	Right-click My Computer, and then click Properties.
2.	On the General tab, the PID appears in the Registered to box.

Microsoft Product Code

The MPC is an important part of a PID. When customers contact Microsoft, the Microsoft Product Support team uses the MPC value in the PID to identify the product. The Microsoft Product Support team also uses the MPC value in the PID to determine whether the customer qualifies for product support.

Setupp.ini

The Setupp.ini file is located on the installation CD in the I386 folder for 32-bit versions. The Setupp.ini file is located in the Ia64 folder for 64-bit versions. The Setupp.ini file is located on the installation CD in the AMD64 folder for x64 versions. The Setupp.ini file contains important information that is used by the Windows Server 2003 Setup program to generate a PID for the computer. You can use Notepad to view the contents of the Setupp.ini file. The MPC is made up of the first five digits of the PID, and the PID-Channel ID is made up of the last three digits of the PID.

Back to the top

For more information, visit the following Microsoft Web site:

Back to the top