Windows 2003 is an incremental update to the technologies introduced in Windows 2000 (see http://www.microsoft.com/windowsserver2003). Versions available include 32-bit, 64-bit and embedded. 64-bit versions do not support 16-bit applcations, real mode applications, POSIX applications or print services for Macintosh clients.

Web Edition

• specifically for web services
• stripped-down version, reduced price
• support for 2GB RAM, 2-way SMP
• unlimited anonymous web connections
• only 10 inbound SMB connections
• no internet gateway, DHCP or Fax server support
• remote desktop administration available
• can't act as a terminal server, application mode
• can't act as a domain controller
• MSDE supports up to 25 concurrent connections

Standard Edition

• Supports Directory, File, Print, Application, Multimedia and Web services for SMBs
• includes MSDE for 5 concurrent connections to databases up to 2GB
• POP3 and SMTP server support
• includes network load balancing (NLB)
• supports 4GB RAM and 4-way SMP

Enterprise Edition

• For medium to large businesses
• 8 processor support, 32GB RAM
• eight node clustering
• 64-bit version supports 64GB RAM and 8-way SMP
• provides Microsoft Metadirectory Services (MMS) which enables integration of directories, databases and files with AD
• 'Hot Add' memory support: no reboot required
• Windows System Resource Manager (WSRM) supports allocation of CPU and Memory on a per-application basis

Datacenter Edition

• only available as an OEM version as part of server hardware package
• 32-bit version supports 32-way SMP with 64GB RAM
• 64-bit version supports 64-way SMP with 512GB RAM
• 128-way SMP version supports two 64-way SMP partitions

Licensing

CAL needed before a client is legally authorised to connect to the server. CALs can be obtained in bundles, and are often included in the OS purchase. CALs and EULAs should be kept for auditting. When updating from NT4 or 2000 to 2003, update CALS are required. CAL required for any connection to a 2003 server that uses server components, including file, print and authentication. Most significant exception is unauthenticated access via the internet, eg web access to an internet site. Therefore websites running on 2003 web edition do not require CALS for the web connections. Two types of CALS: device and user. Per-Server Licensing requires a CAL for each concurrent connection on each server. With Per-Device or Per-User licensing, each user or device or device requires a CAL, but each CAL can be used to access multiple servers. A user with one PC and two laptops would require one user CAL. 30 workers sharing 10 devices would require 10 device CALS. Total number of CALs should equal total number of devices or users, or a mixture of both, that access server resources. CALs can be re-assigned, for instance to a temp replacing a user on leave or to a loan machine while the original is being repaired. Terminal services running in application mode, requires CALs also: XP Pro and 2000 Pro come with these CALs included. Licensing in Control Panel allows you to change Licensing mode, add or remove CALs and configure licensing replication. License Logging service assigns and tracks licences when server resources are accessed. To ensure compliance, licensing information is replicated to a centralised database (Site Licence Server). Use Microsoft Licensing tool, in administrative tools to view and manage licensing. Site Licensing Server is typically the first domain controller in a site: check in AD Sites and Services, Site node, Licensing, Site Settings, Properties. If you transfer the role to another server you must: stop Licence Logging service on new server, and copy:

• %systemroot%\sytem32\cpl.cfg (contains purchase history)
• %systemroot%\lls\llsuser.lls (contains user information about number of connections)
• %systemroot%\lls\llsmap.lls (contains licence group information)
• then restart the service

Use Administrative Tools, Licensing to monitor licensing information. Contains four tabs:

1. Server browser: manage servers, add/remove licences, convert licensing mode, configure replication, change replication schedule (defaults to every 24 hours). To manage per-user or per-device licences, use the Licence, New Licence menu command. New Licences are added to the pool and issued as new users connect. When pool is depleted licence violations occur
2. Purchse History, shows quantity, date, product history
3. Products View, shows cumulative information of licences purchased and allocated
4. Clients

Licence Logging service tracks licences by user name. Where multiple users share a limited number of devices, you should create a group for the users and assign the appropriate number of CALs.