assessing system center configuration manager licensing

8/11/2019 Assessing System Center Configuration Manager Licensing

1/22

LICENSING MANAGEMENT SERIES

A Guide to Assessing Microsoft System Center

Configuration Manager LicensingMay 2011


2/22

This document gives customers of MicrosoftSystems Management Server 2003, Systems Management

Server 2003 R2, Microsoft System Center Configuration Manager 2007, and System Center Configuration

Manager 2007 R2 an overview of licensing requirements and guidance on how to assess the licenses

needed. (For those licensed under any other version of System Center Configuration Management

Server, refer to the appropriate Product Use Rights [PUR] document or Microsoft End User License

Agreement [EULA] for guidance.)

The Software Usage Tracker, a tool in the Microsoft Assessment and Planning (MAP) Toolkit, collects and

reports server and agent use of common deployment scenarios for System Center Configuration

Management products. The data from this tool along with the step-by-step instructions on the pages that

follow, can help you calculate the number and type of server licenses and server and client Management

Licenses (MLs) that you need.

Terms of Use

This document is for informational purposes only and is subject to change. It cannot be considered a source of definitiveMicrosoft licensing guidance.

This document does not supersede the use rights to any product defined in your Microsoft agreement. Nor does it supersede

anything in the Volume Licensing Agreement, Product Use Rights, Product List, OEM EULA, or any other terms of use for

products. Product licensing, program licensing, and business rules are subject to change.


3/22

Contents

System Center Configuration Manager Licensing Requirements ................................................ 1

Server License ................................................................................................................................................ 1

Server and Client Management Licenses ....................................................................................................... 2

Server MLs .................................................................................................................................................. 3

Client MLs ................................................................................................................................................... 4

Additional ML requirements ........................................................................................................................ 5

How to Assess Your Licensing Requirements ............................................................................... 6

1 Set Up Your MAP Scan .............................................................................................................................. 6

Guidelines to ensure a more accurate usage count ................................................................................... 7

2

Generate Relevant Reports ........................................................................................................................ 7

3 Count and Assign Your Server Licenses .................................................................................................. 10

Calculate the number of server licenses required ..................................................................................... 10

Determine physical servers to assign licenses to ..................................................................................... 11

4

Count and Assign Your MLs ..................................................................................................................... 13

Calculate the number of server and client MLs required .......................................................................... 13

Determine physical servers to assign server and client MLs to ................................................................ 14

Make manual adjustments ........................................................................................................................ 16

Optimize ML requirements ........................................................................................................................ 16

References and Resources ............................................................................................................. 18

References .................................................................................................................................................... 18

License Management Series ......................................................................................................................... 19


4/22

1

System Center Configuration Manager

Licensing Requirements

System Center Configuration Management products are licensed through Microsoft Volume Licensing,

the Microsoft Services Provider License Agreement (SPLA), original equipment manufacturers (OEMs),

and, in Japan, the retail/full-package product (FPP). This paper focuses on Configuration Manager

licenses available through Volume Licensing, including Open License, Select License, Select

Plus, Enterprise Agreement (EA), Enterprise Subscription Agreement (EAS), and Open ValueSubscription (OVS).

Note:Customers who provide configuration management as a hosted service to other end customers

must license Configuration Manager through SPLA. For details, seeLicensing Options for Services

Providers.1

Accessing System Center Configuration Manager functionality requires two types of licenses:

Server License

Server and Client Management Licenses

Server License

System Center Configuration Manager servers are licensed per server (or per instance). A server license

entitles you to run one instance of the server software on a given server. A running instance is defined as

loading server software into memory and executing one or more of its instructions.

Before you run any instance of the server software under a server license, you must assign that license to

one of your physical servers, which becomes the licensed server for that particular server license. You

can assign other server licenses to that server, but you cannot assign the same license to more than one

server. A hardware partition or blade is considered to be a separate server.

For each server license you assign, you can run at any one time one instance of the server software

in one physical or virtual operating system environment (OSE) on the licensed server.

You can reassign a server license to another physical server once every 90 days. You may reassign a

server license sooner if you retire the licensed server due to permanent hardware failure. If you

1microsoft.com/licensing/licensing-options/spla-program.aspx
http://www.microsoft.com/licensing/licensing-options/spla-program.aspxhttp://www.microsoft.com/licensing/licensing-options/spla-program.aspxhttp://www.microsoft.com/licensing/licensing-options/spla-program.aspxhttp://www.microsoft.com/licensing/licensing-options/spla-program.aspxhttp://www.microsoft.com/licensing/licensing-options/spla-program.aspxhttp://www.microsoft.com/licensing/licensing-options/spla-program.aspxhttp://www.microsoft.com/licensing/licensing-options/spla-program.aspxhttp://www.microsoft.com/licensing/licensing-options/spla-program.aspx


5/22

System Center Configuration Manager Licensing Requirements 2

reassign a license, the server to which you reassign the license becomes the new licensed server for

that license.

On the other hand, as often as you want you can move a virtual instance of the server software to

another server that is properly licensed to support it. To track this, Microsoft recommends that you

keep a current record of all assigned servers, their license type, Software Assurance coverage, and

the date they were assigned or reassigned.

Note:For information on licensing and virtualization, refer toLicensing Microsoft Server Products in

Virtual Environments.2

Configuration Manager requires Microsoft SQL Servertechnology for its proper functioning.

Configuration Manager is available in two editionswith and without SQL Server. If you license

Configuration Manager:

With SQL Server, the SQL Server functionality provided is limited to the support of Configuration

Manager.

Without SQL Server, you can license SQL Server separately on a per processor basis, or by using a

server license and Client Access Licenses (CALs).

Note:Get more information onSQL Server licensing.3

Server and Client Management Licenses

In addition to the server license, you must have the appropriate number of server and client Management

Licenses (MLs) to directly or indirectly manage server and client OSEs with the following exceptions. You

do not need a ML to manage OSEs:

Running instances of the server software on your licensed servers.

In which no instances of software are running.

On any devices functioning only as network infrastructure devices (OSI layer 3 or below).

On any devices for which you are exclusively performing out-of-band management. This consists of

interaction through a network connection with a hardware management controller to monitor or

manage the status of hardware such as system temperature, fan speed, power on/off, system reset,

and CPU availability.

MLs are required for any other case of direct or indirect management of an OSE. To manage an OSE

means to solicit or receive data about, configure, or give instructions to the hardware or softwareassociated with the OSE, other than to discover the presence of a device. Monitoring use of CPU, RAM,

NIC, and storage components is considered indirect management of the OSE and requires an ML.

2microsoft.com/downloads/details.aspx?FamilyID=9ef7fc47-c531-40f1-a4e9-9859e593a1f1

3microsoft.com/sqlserver/2008/en/us/licensing.aspx
http://www.microsoft.com/downloads/details.aspx?FamilyID=9ef7fc47-c531-40f1-a4e9-9859e593a1f1http://www.microsoft.com/downloads/details.aspx?FamilyID=9ef7fc47-c531-40f1-a4e9-9859e593a1f1http://www.microsoft.com/sqlserver/2008/en/us/licensing.aspxhttp://www.microsoft.com/downloads/details.aspx?FamilyID=9ef7fc47-c531-40f1-a4e9-9859e593a1f1http://www.microsoft.com/downloads/details.aspx?FamilyID=9ef7fc47-c531-40f1-a4e9-9859e593a1f1http://www.microsoft.com/downloads/details.aspx?FamilyID=9ef7fc47-c531-40f1-a4e9-9859e593a1f1http://www.microsoft.com/sqlserver/2008/en/us/licensing.aspxhttp://www.microsoft.com/sqlserver/2008/en/us/licensing.aspxhttp://www.microsoft.com/sqlserver/2008/en/us/licensing.aspxhttp://www.microsoft.com/sqlserver/2008/en/us/licensing.aspxhttp://www.microsoft.com/downloads/details.aspx?FamilyID=9ef7fc47-c531-40f1-a4e9-9859e593a1f1http://www.microsoft.com/sqlserver/2008/en/us/licensing.aspxhttp://www.microsoft.com/downloads/details.aspx?FamilyID=9ef7fc47-c531-40f1-a4e9-9859e593a1f1http://www.microsoft.com/downloads/details.aspx?FamilyID=9ef7fc47-c531-40f1-a4e9-9859e593a1f1


6/22


Server MLs

Managed OSEs running server operating system software require server MLs, which are licensed per

OSE and must be assigned to the device on which your managed server OSE runs. A hardware partition

or blade is considered to be a separate device.

If you manage a virtual OSE on the licensed device and use the physical OSE solely to run hardware

virtualization software, provide hardware virtualization services, or run software to manage and

service OSEs on that device, then you can manage that virtual and physical OSE under a single

server ML.

At any one time, the number of server OSEs you manage on a device cannot exceed the number of

OSE server MLs assigned to that device (except in the virtualization case explained above).

Server ML editions

Configuration Manager Server ML editions adopt an inclusive model whereby all functionality provided in

the Standard Server ML is also provided as part of Enterprise Server ML. The choice between these two

editions depends on the workload you are managing.

Standard Server ML.Use the Standard Server ML to manage:

Inventory, software distribution, and patch management for any workload.

Desired Configuration Management (DCM) for basic workloads: Base operating system or system

hardware, storage/file/print (FTP, NFS, SMB, and CIFS), and networking (DHCP, DNS, WINS, and

RADIUS).

For Configuration Manager 2007 R3 only: In addition to basic workloads, DCM for security workloads,

including firewall, proxy, intrusion detection and prevention, anti-virus management, application

security gateway, content filtering, network forensics, security information management, and

vulnerability assessment.

Applications that do not require use of DCM.

Enterprise Server ML.Use the Enterprise Server ML to manage all of the standard workloads as well as

to provide DCM management for all workloads, including applications that run in the licensed OSE.

Acquiring server MLs through System Center Server Management suites

You can buy server MLs for Configuration Manager 2007 and Configuration Manager 2007 R2 as

standalone products or as part of two different server management suites, which offer different sets of use

rights compared to the standalone OSE server ML:

When acquired as part of Server Management Suite Enterprise. You can manage any number of

OSEs on a device to which a Server Management Suite Enterprise license is assigned.

Note:For Configuration Manager 2007 R3, Server Management Suite Enterprise use rights have

been revised to allow management of up to four OSEs on the device to which a Server Management

Suite Enterprise license is assigned.


7/22


When acquired as part of Server Management Suite Datacenter. You can manage any number

of OSEs on a device to which Server Management Suite Datacenter is assigned if you have the

greater of:

Two qualifying Server Management Suite Datacenter licenses; or

A number of qualifying Server Management Suite Datacenter licenses equal to the device's total

number of physical processors.

Client MLs

Managed OSEs running non-server operating system software require client MLs. (Client MLs do not

permit users to manage any OSE running a server operating system.) Depending on planned usage

scenarios, you can license Configuration Manager Client MLs in two ways:

Per OSE or per user when purchased standalone.

Per user or per device through the purchase of Microsoft Core CAL and Microsoft Enterprise

CAL suites.

OSE client MLs.You must assign these to the deviceson which your managed client OSEs run. A

hardware partition or blade is considered to be a separate device.

User client MLs.You must assign these to the usersof your managed OSEs. User client MLs permit

instances of your server software to manage the client OSEs used by each user. If you have more than

one user using an OSE, and you are not licensing by OSE or device, you must assign user client MLs to

each user. User client MLs are most cost-effective for users with multiple OSEs or devices managed by

Configuration Manager-a laptop, desktop, and smart phone, for example.

Device client MLs.You must assign these to a physical client device. A hardware partition or blade isconsidered to be a separate device. Device client MLs permit instances of the server software to manage

any number of OSEs running on the devices to which they are assigned; any user can use those

managed OSEs. Device-based MLs are a cost-effective choice when a device has more than one OSE.

Device client MLs are only available through Core CAL and Enterprise CAL suites.


8/22


Additional ML requirements

Mixing ML types.Unless your Volume Licensing Agreement specifies otherwise, you can mix OSE, user,

and device client MLs in a single environment. However, this adds complexity to license management

because you must acquire and track each client ML separately, so Microsoft generally recommends

against it.

Reassigning MLs.You may:

Permanently reassign an OSE server or client ML from one device to another, or a user client ML

from one user to another no more than once every 90 days.

Temporarily reassign an OSE server or client ML to a loaner device while the first device is out of

service, or a user client ML to a temporary worker while the primary user is absent.

Version access.Your MLs permit management by instances of earlier, but not later, versions of the

server software. If you are running instances of an earlier version of the server software under the license

terms, you can also use MLs corresponding to that version. In that case, you can use server MLs as OSE

server MLs, and client MLs as either OSE or user client MLs.

Affiliation.Your MLs are valid only for use with your servers; they do not license management of OSEs

by management server software of non-affiliated organizations. (Affiliation is defined in your Volume

Licensing Agreement).


9/22

6

How to Assess Your Licensing Requirements

Microsoft has developed a Software Usage Tracker to help you assess licensing requirements for

Systems Management Server 2003, Systems Management Server 2003 R2, System Center Configuration

Manager 2007, and System Center Configuration Manager 2007 R2. Part of the Microsoft Assessment

and Planning (MAP) Toolkit, it collects and reports server and client use of common deployments.

Note:Although MAP has not been tested and certified for use with System Center Configuration

Manager 2007 R3, you may be able to use it to assess licensing requirements.

This section includes step-by-step instructions to help you generate usage reports and explains

specifically how to use them to help determine your Configuration Manager licensing needs. To do this,

follow these four broad steps:

1.Set up your MAP scan.

2.Generate relevant reports.

3.Count and assign your server licenses.

4.Count and assign your MLs.

Completing this assessment requires network administration and licensing expertise and permissions.

If licensing compliance and network administration responsibilities belong to different people in your

organization, they need to work together to complete this assessment correctly.

Note:It is important to understand that the Software Usage Tracker provides only a software usage

report; it does not create a licensing report. And although the guidance offered in this section may be helpful,

it is not definitive. It does not replace or supersede your use rights as legally defined in your PUR document.

1 Set Up Your MAP Scan

In this first step, you tell MAP what to scan. To complete it, you need server administration expertise and

permissions.

1. Download the MAP Toolkit fromhttp://www.microsoft.com/map/.

2. To configure your MAP deployment, follow the Getting Started Guideand SoftwareUsage Tracker

Guideinstructions built into the MAP installation.

Note: Make sure you have the latest version of theMAP Toolkit.4

4http://www.microsoft.com/map
http://www.microsoft.com/map/http://www.microsoft.com/map/http://www.microsoft.com/map/http://www.microsoft.com/maphttp://www.microsoft.com/maphttp://www.microsoft.com/maphttp://www.microsoft.com/maphttp://www.microsoft.com/maphttp://www.microsoft.com/maphttp://www.microsoft.com/map/


10/22

How to Assess Your Licensing Requirements 7

Guidelines to ensure a more accurate usage count

Ensure that your configuration is complete. MAP scans usage only on servers and network segments

identified during configuration. Incomplete configuration gives you incomplete results.

Scan during a time period when your OSE is running the maximum number of servers and virtual

machines. MAP counts only servers running at the time it scans. If the number of users and devices

fluctuates seasonally, run the scan in your busiest season.

Scan servers with different license obligations separately.

Configure your network scan range to take licensing variations of products into account. Scan servers

with similar licensing together because you will apply that licensing logic to the results. Exclude

servers subject to different licensing obligations, like development or test servers licensed under the

MSDNdeveloper program. The Software Usage Tracker Guide explains how to exclude network

segments or specific devices from the scan.

Make note of network segments that you exclude due to licensing variations to ensure that you

correctly account for their licensing later. For example, ensure that you have MSDN licenses for

servers licensed under MSDN programs.

Separately scan servers and clients with OSEs that may be exempt from ML use to avoid over-

counting your ML needs. Refer back to the introduction to server and client MLs on page3 for the

most important examples.

2 Generate Relevant Reports

Before you begin, make sure to review theConfiguration Manager Licensing Requirementsoutlined in the

first half of this guide.

In this second section, you run the MAP scan and generate three reports on your servers running

Configuration Manager, and clients that are being managed in turn: Configuration Manager Summary,

Virtual Machine, and Inventory Results reports.

1. Run the MAP assessment.

2. In the Software Usage Tracker, click Software Usage Summaryto see the total number of server

instances (both physical and virtual) running each version of Configuration Manager, and server and

desktop clients managed by each version.

Note:The default date range is 90 days. To change the date range, click Configure Date Range

under Actions.


11/22


3. Under Software Usage Summary, click System Center Configuration Manager.

4. Under Actions, click Generate Reportto create the Configuration Manager report (a Microsoft

Office Excelspreadsheet) for the servers listed.

The spreadsheet breaks the list down by version number, and gives the number of Configuration

Manager server instances and server and desktop clients.


12/22


5. Click Inventory and Assessment.

6. Under Discovery and Readiness, click Virtual Machine Discoveryto get an inventory of virtual

machines and guest operating systems.

7. To generate the second report, under Actions, click Generate Reportto create the Virtual Machine

report in Excel.

The spreadsheet gives details on the physical servers running virtual machines and also the host-to-

guest relationship for the virtualized servers.


13/22


8. Under Inventory and Assessment, click Inventory Summary Resultsto see the summary

information on computers and operating systems that the MAP tool discovers.

9. To generate the third report, under Actions, click Generate Reportto create the third Excel report,

Inventory Results.

The spreadsheet gives details on all the physical and virtual machines that MAP inventoried.

3 Count and Assign Your Server Licenses

In this third section, you will use the reports you generated to count the management server licenses

required and determine which physical servers to assign those licenses to.

Calculate the number of server licenses required

1. In MAP, click Viewand then click Saved Reports and Proposals.

2. Open the Excel Configuration Managerreport generated in the previous section.


14/22


3. The Server Summaryworksheet lists the number of servers discovered for each version.

For each server instance shown in the report, you need a license of the same or later version.

ExampleAdd up the server licenses indicated in theTotal Servers Requiring Licensecolumn to get the number

you need. If the Server Summarygave the information shown below, you would need two server

licenses.

Server Version Total Servers Covered Total Servers Requiring License

System Center Configuration

Manager 2007

2 2

Systems Management Server 2003 2 0

Determine physical servers to assign licenses to

Configuration Management server software can play several different roles in an IT environment, but only

primary servers in the site server role require a license. You will use the Excel reports you generated in

theprevious sectionto determine which physical servers to assign server licenses to.

1. Open the Server Detailsworksheet of the Configuration Manager report, and look for every Server

Nameidentified as a site server. ()

2. Open the Virtual Machine report. In the Host and Guest Details worksheet,look for the matching

server name in the Virtual Machine FQDNcolumn. ()

3. If a matching entry exists (as in our example on page12), then it is a virtual server.

Look up the corresponding Physical Server Name (), and assign a server license to that physical

server.

4. If no matching entry exists (not illustrated in our example), then open the Inventory Resultsreport. In

the Hardware Inventory Detailsworksheet, look for the matching server name in the Computer

Namecolumn

If Machine Type is marked Physical, then it is a non-virtualized physical server. Assign a server

license to that physical server.

If Machine Typeis marked Insufficient Data, then MAP was unable to fully inventory the machine.

Before you can count the number of licenses accurately, you will need to correct the issuespreventing a full inventory, such as a lack of permissions or network connectivity issues. In this

situation, you need to correct the issues preventing inventory (or) check the physical/virtual status

in another manner (company records, by logging on, etc.). Then assign a server software license to

the appropriate physical server.

Note:The Configuration Manager 2007 R2 server license provides downgrade rights to

Configuration Manager 2007 and Systems Management Server 2003 server software. And

Configuration Manager 2007 server license provides downgrade rights to Systems Management


15/22


Server 2003. You can account for this to optimize your licensing. The Productcolumn in the Server

Details worksheet identifies a specific version of management server.

Example Excel reportsNote that these examples do not show the entire Excel reports, but only columns of interest.

Configuration Manager report: Server Details worksheet

Server Name Server Role Product Version Number

CE4P-3E32-R2-2.MAP.COM SMS Distribution Point Systems Management

Server 2003

2.50.4253.3000

CE4VM-W2K832-MP.MAP.COM SMS Component Server System Center Configuration

Manager 2007

4.00.6487.2000

CE4VM-W2K832-MP.MAP.COM SMS Management Point System Center ConfigurationManager 2007

4.00.6487.2000

CE4VM-W2K864-CS.MAP.COM SMS Site Server System Center Configuration

Manager 2007

4.00.6487.2000


Server 2003

2.50.4253.3000

Server Namefor a virtual instance is equivalent to the Virtual Machine FQDN in the Host and Guest Detai lsworksheet of

the Virtual Machinereport.

Version Numberis the unique identifier for every server version across the Systems Management Server and Configuration

Manager portfolio.

Virtual Machine report: Host and Guest Details worksheet

PhysicalServerName

PhysicalServer No. ofProcessors

VirtualMachineName

VirtualMachineStatus

Virtual Machine FQDN(Fully QualifiedDesktop Name)

Virtual MachineOperatingSystem

CE4-05H-

LEGACY.MAP.COM

2 CE4VM-W98 Unknown Insufficient Data

CE4-HVH-MISC-

03.MAP.COM

2 CE4VM-

W2K864-CS

Running CE4VM-W2K864-

CS.MAP.COM

Windows Server

2008 R2

Enterprise

CE4-HVH-MISC-

03.MAP.COM

2 CE4VM-

W2K864-CS

Running CE4VM-W2K864-

CS.MAP.COM

Windows Server

2008 R2

Enterprise

POE-HVH-

01.SEATTLE.COM

2 POE-VE-07-

IND-1

Running POE-VE-07-IND-

1.INDIA.SEATTLE.COM

Microsoft Windows

Vista Ultimate

POE-HVH-

01.SEATTLE.COM

2 POE-W7-07-

MAR-1

Running POE-W7-07-MAR-

1.MARS.SEATTLE.COM

Windows 7

Enterprise

Physical Server Name identifies the physical server on which the virtual machine is configured to run.


16/22


Virtual Machin e FQDNis equivalent to the Server Namein the Server Detailsworksheet of the Configurat ion Managerreport.

Inventory Results report: Hardware Inventory Details worksheet

ComputerName

CurrentOperatingSystem

Number ofProcessors

Numberof Cores

LogicalProcessorCount

MachineType

winsvr-19.contoso.com Microsoft Windows

Server 2008 for Itanium-

Based Systems

2 2 2 Physical

wincli-96.contoso.com Microsoft Windows

Vista Business

1 4 4 Physical

winsvr-16.contoso.com Windows Server 2008

R2 Enterprise

1 1 1 Virtual

CEA1-V-8E32-2 Windows Vista or

Windows Server 2008

Insufficient

Data

Insufficient

Data

Insufficient

Data

Insufficient

Data

Wincli-47.contoso.com Microsoft Windows XP

Professional

1 1 1 Physical

Computer Nameidentifies the physical or virtual machine nameequivalent to the Server Namefield in the Server Details

worksheet of the Configurat ion Managerreport.

4 Count and Assign Your MLs

In this final section, you will use the reports you generated insection 2to calculate the number of MLs

required and determine which physical servers to assign those licenses to.

Calculate the number of server and client MLs required

1. In MAP, click View, and then click Saved Reports and Proposals.

2. Open the Excel Configuration Managerreport generated in section 2.

3. The Overviewworksheet lists the number of server and desktop clients discovered for each version.

For each client identified, you need a ML of the same or later version.

Example

If the Overviewworksheet gave the overview information shown on the next page (we have included only

the relevant columns), you would need a total of 79 server and client MLs.

Client MLs:Zero Configuration Manager 2007 client MLs and 67 Systems Management Server 2003

client MLs; alternatively, you can use 67 Configuration Manager client MLs.

Server MLs:3 Configuration Manager 2007 server MLs and 9 Systems Management Server 2003

server MLs; alternatively, you can use 12 Configuration Manager 2007 server MLs.


17/22


Summary Item Count

Total number of System Center Configuration Manager desktop clients discovered 0

Total number of System Center Configuration Manager instances discovered 2

Total number of System Center Configuration Manager server clients discovered 3

Total number of Systems Management Server 2003 desktop clients discovered 67

Total number of Systems Management Server 2003 instances discovered 2

Total number of Systems Management Server 2003 server clients discovered 9

Determine physical servers to assign server and client MLs to

You will use the Excel reports you generated insection 2to determine which physical servers to assign

server and client MLs to.

1. In MAP, click View, and then clickSaved Reports and Proposals.

2. Open the Configuration Managerreport, and open the Agent Detailsworksheet (illustrated on the

next page). For every entry in the Agent Details worksheet follow the steps below.

This gives details on each Configuration Manager 2007 and Systems Management Server 2003

agent (server and client) that MAP discovered.

3. In the Server Detailsworksheet (illustrated on page 12), look for the matching agent version in the

Version Numbercolumn. ()

This tells you whether a Systems Management Server or Configuration Manager ML is required, at aminimum.

4. Open the Virtual Machinereport (illustrated on page12), and in the Host and Guest Details

worksheet, look for the matching Computer Namein the Virtual Machine FQDN column.

5. If a matching entry exists, then it is a virtual server.

Look up the corresponding Virtual Machine Operating Systemvalue. This tells you whether a

server or client ML is required. Look up the corresponding Physical Server Namein the VM report

and assign an appropriate ML to that physical server.

6. If no matching entry exists, then open theInventory Resultsreport. In the Hardware Inventory

Detailsworksheet, look up the Computer Name.

If the Machine Typefield is marked Physical, then it is a non-virtualized physical server. Assign

an ML to that physical server. The corresponding Current Operating Systemvalue tells you

whether a server or client ML is required.

If the Machine Typefield is marked Insufficient Data, then MAP was unable to fully inventory the

machine. Before you can count the number of licenses accurately, you will need to correct the

issues preventing a full inventory, such as a lack of permissions or network connectivity issues.

In this situation, you need to correct the issues preventing inventory (or) check the physical/virtual


18/22


status in another manner (company records, by logging on, etc.). Then assign an appropriate ML

type to the physical server determined.

7. Return to Step 3 above and repeat these steps for the next entry in the table.

Example Excel reports

Configuration Manager report: Agent Details worksheet

Computer Name Agent Version Active

CE4P-3E32-R2-2.MAP.COM 2.50.4253.3000 Yes

CE4P-3E64-R2-2.MAP.COM 2.50.4253.3000 Yes

CE4P-8E64-RTM-2.MAP.COM 2.50.4253.3000 Yes

CE4P-VE32-SP1-2.MAP.COM 2.50.4253.3000 Yes

CE4P-W7P32-2.MAP.COM 2.50.4253.3000 Yes

CE4P-XP32-SP3-2.MAP.COM 2.50.4253.3000 Yes

CE4VM-W2K832-MP.MAP.COM 4.0.6487.2000 No

Comp uter Name is the name of the physical or virtual machine that is being managed. For a virtual instance, it is equivalent

to the Virtual Machin e FQDNfield in the Host and Gu est Detailsworksheet of the Virtual Machinereport.

Agent Versionidentifies whether the agent is a Configuration Manager or Systems Management Server agent. It is

equivalent to the Version Numberin the Server Detailsworksheet of the Configurat ion Managerreport; the Product

column identifies the product name.

Configuration Manager report: Server Details worksheet

Server Name Server Role Product Version Number


Server 2003

2.50.4253.3000

CE4VM-W2K832-MP.MAP.COM SMS Component Server System Center Configuration

Manager 2007

4.00.6487.2000

CE4VM-W2K832-MP.MAP.COM SMS Management Point System Center Configuration

Manager 2007

4.00.6487.2000

CE4VM-W2K864-CS.MAP.COM SMS Site Server System Center ConfigurationManager 2007

4.00.6487.2000


Server 2003

2.50.4253.3000


19/22


20/22


For client MLs

You may have cost savings if you use Core CAL and Enterprise CAL suites, depending on the number of

client OSEs being managed on a physical server, the number of unique users accessing each managed

client OSE, and the number of managed client OSEs accessed by any given user.

Core CAL and Enterprise CAL deployments of Configuration Manager licensed per deviceallow

management of any number of client OSEs on a physical server. Moreover, any number of users can use

each one of those client OSEs. For example, as shown in the Overview worksheet on page 14, 67 Core

CAL or Enterprise CAL licenses could be used toward managing all desktop client agents (spanning

Systems Management Server and Configuration Manager) running across 67 unique devices. Device

client MLs are appropriate when more than one client OSE is on the device.

Core CAL and Enterprise CAL deployments of Configuration Manager licensed per userallow

management of any number of client OSEs that the licensed user accesses. If you have more than one

user using a client OSE, you must have a user license assigned to each user. User client MLs are

appropriate when a user has multiple client OSEs or devices with client OSEs that need to be managed

(for example, a user with a laptop, desktop, and mobile phone that Configuration Manager manages).

Note: TheMAP tool currently does not account for per-user licensing of client MLs, so if you want to

take advantage of these, you will need to assign and track these manually.


21/22

18

References and Resources

References

System Center Configuration Manager 2007 R3 product details:

microsoft.com/systemcenter/en/us/configuration-manager/cm-product-details.aspx

System Center Configuration Management scenarios:

microsoft.com/systemcenter/en/us/configuration-manager/cm-scenarios.aspx

System Center Configuration Manager 2007 R3 Pricing and Licensing:

microsoft.com/systemcenter/en/us/configuration-manager/cm-pricing-licensing.aspx

System Center Configuration Manager 2007 R3 Product Use Rights:

microsoftvolumelicensing.com/userights/ProductPage.aspx?pid=256

Licensing Microsoft Software for System Center Server Management Suite Enterprise and Server

Management Suite Datacenter:

download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-

A5B04179958B/SMSE_SMSD_Licensing.docx

Microsoft Assessment and Planning (MAP) Toolkit:microsoft.com/map

Software Asset Management (SAM):

microsoft.com/sam/en/us/default.aspx
http://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-product-details.aspxhttp://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-product-details.aspxhttp://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-scenarios.aspxhttp://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-scenarios.aspxhttp://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-pricing-licensing.aspxhttp://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-pricing-licensing.aspxhttp://www.microsoftvolumelicensing.com/userights/ProductPage.aspx?pid=256http://www.microsoftvolumelicensing.com/userights/ProductPage.aspx?pid=256http://download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/SMSE_SMSD_Licensing.docxhttp://download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/SMSE_SMSD_Licensing.docxhttp://www.microsoft.com/maphttp://www.microsoft.com/maphttp://www.microsoft.com/sam/en/us/default.aspxhttp://www.microsoft.com/sam/en/us/default.aspxhttp://www.microsoft.com/sam/en/us/default.aspxhttp://www.microsoft.com/maphttp://download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/SMSE_SMSD_Licensing.docxhttp://download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/SMSE_SMSD_Licensing.docxhttp://www.microsoftvolumelicensing.com/userights/ProductPage.aspx?pid=256http://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-pricing-licensing.aspxhttp://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-scenarios.aspxhttp://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-product-details.aspx


22/22

License Management Series

This guide is one in a series of five in-depth how-to guides that can help you generate and interpret MAP

Toolkit Software Usage Tracker reports that you can use to calculate the number of server licenses andCALs/MLs you need.

Refer to theGuidance for MAP Toolkit Software Usage Tracker4page to download the other four guides:

A Guide to Assessing Windows Server Licensing

A Guide to Assessing Exchange Server Licensing

A Guide to Assessing SharePointServer Licensing

A Guide to Assessing SQL Server Licensing

4microsoft.com/sam/en/us/briefs.aspx

2011 Microsoft Corporation. All rights reserved.

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN

THIS DOCUMENT. This information is provided to help guide your authorized use of products you license; it is not your

agreement. Your use of products licensed under your Volume Licensing agreement is governed by the terms and conditions

of that agreement. In the case of any conflict between this information and your agreement, the terms and conditions of your

agreement control. Prices for licenses acquired through Microsoft resellers are determined by the reseller.

0511
http://www.microsoft.com/sam/en/us/briefs.aspxhttp://www.microsoft.com/sam/en/us/briefs.aspxhttp://www.microsoft.com/sam/en/us/briefs.aspxhttp://www.microsoft.com/sam/en/us/briefs.aspxhttp://www.microsoft.com/sam/en/us/briefs.aspxhttp://www.microsoft.com/sam/en/us/briefs.aspxhttp://www.microsoft.com/sam/en/us/briefs.aspxhttp://www.microsoft.com/sam/en/us/briefs.aspx

assessing system center configuration manager licensing

Documents