Securing Wireless LANs with PEAP and Passwords

Appendix C: Supported OS Versions

Updated: April 2, 2004

The following table shows the status of different Microsoft Windows operating system client and server versions. The table lists the role of the system within this solution, the different operating system versions that might be used in that role, and the support status of each operating system. The final column includes additional explanatory notes or caveats.

Table A.1: Support Status of Operating System Versions in the Solution

RoleOperating System VersionSupport StatusNotes

Wireless client

Windows XP with Service Pack 1 (Professional and Tablet Editions)

Solution Tested

Pocket PC 2003

Solution Tested

The implementation of 802.1X WLAN support may vary between Pocket PC device vendors.

Wi–Fi Protected Access (WPA) is not yet available from Microsoft although may be supported by companies other than Microsoft.

Windows 2000

Supported

Need to obtain 802.1X client from Microsoft.com.

WPA support is not available from Microsoft although may be available from companies other than Microsoft.

Microsoft Windows NT 4.0

–Windows 9x

Supported

Need to obtain 802.1X client through Premier Support.

WPA support is not available from Microsoft although may be available from companies other than Microsoft.

Other platforms

Unknown—support may be available from companies other than Microsoft.

Clients need to support 802.1X and PEAP–MS–CHAP v2.

Certification Authority

Windows Server™ 2003, Standard Edition

Solution Tested

Windows Server 2003, Enterprise Edition

Supported

Enterprise Edition is a superset of Standard Edition.

Windows 2000 Server

Supported

The certification authority (CA) features of Windows 2000 Server are very similar to that of Windows Server 2003, Standard Edition.

CAs from companies other than Microsoft

Unknown

The CA must be able to generate server certificates for Internet Authentication Service (IAS). You have to manage the enrolment and renewal manually.

RADIUS Server

Windows Server 2003, Standard Edition

Solution Tested

Standard Edition only supports up to 50 wireless access points (APs).

Windows Server 2003, Enterprise Edition

Supported

Enterprise Edition is a superset of Standard Edition, so all features required by the solution are included in both editions.

Windows 2000 Server

Supported

Windows 2000 Internet Authentication Service (IAS) may be used for wireless 802.1X with PEAP. Requires installation of Windows 2000 802.1X client on IAS server. No wizard support for wireless remote access policy configuration.

Other platforms

Not Supported

Domain controllers

Windows Server 2003

Solution Tested

Universal groups require Active Directory domain to be in Windows 2000 native mode or higher.

Windows 2000 Server

Supported

Universal groups require Active Directory domain to be in Windows 2000 native mode or higher.

Infrastructure servers, Domain Name System (DNS), and Dynamic Host Configuration Protocol (DHCP)

Windows Server 2003

Solution Tested

Windows 2000 Server

Supported

Other platforms

Unknown

DHCP, DNS, and management solutions provided by companies other than Microsoft should work with this solution as long as they fulfill the basic requirements for Windows client and Active Directory.

The support status in the table is listed as one of the following:

Solution Tested: The operating system version has been specifically tested to work as part of the solution. All product versions included in this category are also included in the next, "Supported" category.

Supported: The Microsoft Windows product group has tested this operating system version and Microsoft fully supports its use in this configuration (although you may need to provide additional configuration or customization beyond what is included in the guidance for this solution). This version has not, however, been tested as part of this solution, which may mean that the solution guide does not include full installation and configuration details for that version.

Not Supported: The operating system version will not work within the solution as described. It may be possible to configure the unsupported system to work correctly, but this is likely to involve a significant amount of effort.

Unknown: The operating system version may work in this role, there is no technical reason for it not to work. However, this is subject to your own verification and testing.

Note: In the table, there are few rows in which no operating system versions (in the Operating System Version column) are shown against roles (in the Role column); in these cases, either the operating system does not work for that role (Not Supported status) or it is not known whether it will work (Unknown status).


Top of pageTop of pagePrevious13 of 14Next
**
**