Updated: July 10, 2020 (October 19, 2009)

  Analyst Report Archived

Introduction

My Atlas / Analyst Reports

617 wordsTime to read: 4 min
Rob Horwitz by
Rob Horwitz

Rob Horwitz analyzes and writes about Microsoft licensing programs and product licensing rules. He also trains organizations on best Microsoft... more

Microsoft’s only server OS, Windows Server, delivers directory services, administration tools, and many other capabilities for building and maintaining a network infrastructure. It is also the OS platform for which all Microsoft server-based applications are built. The most recent version, Windows Server 2008 R2, shipped in Oct. 2009 and made very few changes to the product’s licensing. (See the sidebar “Recent Windows Server Licensing and Packaging Changes“.)

Licensing Windows Server for use within an organization is generally straightforward if hardware virtualization is used sparingly—a Standard or Enterprise edition server license is needed for each physical server machine, and one Windows Server Client Access License (CAL) must be purchased for each user or device within the organization. However, accommodating scenarios involving nonemployees, using the two Windows Server features that are licensed separately (Remote Desktop Services, formerly called Terminal Services, and Rights Management Services), or making heavy use of virtualization are major factors that can complicate Windows Server licensing considerably.

Atlas Members have full access

Get access to this and thousands of other unbiased analyses, roadmaps, decision kits, infographics, reference guides, and more, all included with membership. Comprehensive access to the most in-depth and unbiased expertise for Microsoft enterprise decision-making is waiting.

Membership Options

Already have an account? Login Now

Not a member but want to see the full content? Contact us.