Microsoft Assessment and Planning Toolkit

Software Usage Tracker User Guide

Version 5.5

Published: January, 2011

For the latest information, please see
http://go.microsoft.com/fwlink/?LinkId=106437

Copyright © 2011 Microsoft Corporation. All rights reserved. Complying with the applicable copyright laws is your responsibility. By using or providing feedback on this documentation, you agree to the license agreement below.

If you are using this documentation solely for non-commercial purposes internally within YOUR company or organization, then this documentation is licensed to you under the Creative Commons Attribution-NonCommercial License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc/2.5/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA.

This documentation is provided to you for informational purposes only, and is provided to you entirely "AS IS". Your use of the documentation cannot be understood as substituting for customized service and information that might be developed by Microsoft Corporation for a particular user based upon that user's particular environment. To the extent permitted by law, MICROSOFT MAKES NO WARRANTY OF ANY KIND, DISCLAIMS ALL EXPRESS, IMPLIED AND STATUTORY WARRANTIES, AND ASSUMES NO LIABILITY TO YOU FOR ANY DAMAGES OF ANY TYPE IN CONNECTION WITH THESE MATERIALS OR ANY INTELLECTUAL PROPERTY IN THEM.

Microsoft may have patents, patent applications, trademarks, or other intellectual property rights covering subject matter within this documentation. Except as provided in a separate agreement from Microsoft, your use of this document does not give you any license to these patents, trademarks or other intellectual property.

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious.

Microsoft, Active Directory, Excel, SharePoint, Windows, Windows Server and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries and regions.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

You have no obligation to give Microsoft any suggestions, comments or other feedback ("Feedback") relating to the documentation. However, if you do provide any Feedback to Microsoft then you provide to Microsoft, without charge, the right to use, share and commercialize your Feedback in any way and for any purpose. You also give to third parties, without charge, any patent rights needed for their products, technologies and services to use or interface with any specific parts of a Microsoft software or service that includes the Feedback. You will not give Feedback that is subject to a license that requires Microsoft to license its software or documentation to third parties because we include your Feedback in them.

Contents

Overview

The Software Usage Tracker feature in the Microsoft® Assessment and Planning (MAP) Toolkit helps gather data on users and devices that access Microsoft core server products in your environment. This data can significantly simplify the inventory process for client access license (CAL) reporting.

This document provides instructions on how to use the Usage Tracker. For more information about which Microsoft server product versions Usage Tracker reports on, see Appendix A, “Supported Server Products.”

Reporting Limitations

The information in the Software Usage Tracker reports that the MAP Toolkit generates are subject to many limitations. The information these reports contain does not constitute legal, accounting, or other professional advice. These reports are for informational purposes only and should not be used as the sole source of information for determining software license usage compliance.

Software Usage Tracker reports should be used as a baseline for CAL usage analysis rather than as an authoritative summary of software usage. Due to the wide variety of ways that software can be deployed and inventoried in your environment, the Software Usage Tracker cannot always produce accurate counts of server software and access to that software. For more information about scenarios that could lead to inaccurate reporting, see Appendix B, “Examples of Limiting Scenarios.”

Prepare Your Environment

The process that you will follow to prepare your environment to use the Usage Tracker depends on what server product you want to track. The following steps will help you:

• Meet MAP Toolkit prerequisites

• Configure log files

Meet MAP Toolkit Prerequisites

The Software Usage Tracker feature uses Windows Management Instrumentation (WMI) and the Remote Registry Service to discover and inventory some Microsoft server products. Ensure you configure them as described in the “Preparing Your Environment” section of the Microsoft Assessment and Planning Toolkit: Getting Started Guide.

Configure Log Files

The Usage Tracker gathers information about users and devices that access your servers. For some server products, it analyzes log files and system information to provide data that you can use to track usage of server software. To prepare to use Usage Tracker, you must first configure your computers to generate log files that contain the data necessary for usage tracking analyses. You will require log files for the following products:

• Windows Server®

• Microsoft SQL Server® 2008

• Microsoft Office SharePoint® Server

• Microsoft Office SharePoint Portal Server 2003

Windows Server Usage

To capture logon information the Audit Logon policy needs to be set to “Success,” which is the default for all Windows Server operating systems since Windows Server 2003. You can also set this configuration manually in the Group Policy Management Console (GPMC) or automatically using the Auditpol.exe command-line tool.

For more information about these Group Policy settings, see the following resources:

• For Windows Server 2008, see Microsoft Knowledge Base article 921469 at http://support.microsoft.com/kb/921469.

• For Windows Server 2003, see Define or modify auditing policy settings for an event category at http://technet.microsoft.com/en-us/library/cc787268(WS.10).aspxhttp://technet.microsoft.com/en-us/library/cc787268(WS.10).aspx#BKMK_1..

SQL Server Usage

SQL Server 2008 Enterprise and Datacenter Editions introduced audit event configuration for Windows security logging, which enabled SQL Server 2008 to log logon events to the Windows Security log. The MAP Toolkit can parse these logs to track usage for SQL Server 2008 Enterprise and Datacenter Editions.

To enable SQL Server 2008 to log audit events to the Windows security log

• On each SQL Server 2008 instance for which you need to track usage, run the following SQL command.

/* Turn LOGIN logging on */

USE MASTER

GO

/* Note: the name 'Server_Audit' is your choice */

CREATE SERVER AUDIT [Server_Audit]

TO SECURITY_LOG WITH ( QUEUE_DELAY = 1000, ON_FAILURE = CONTINUE);

ALTER SERVER AUDIT [Server_Audit]

WITH (STATE = ON);

USE MASTER

GO

/* Note: the name 'login_audit' is your choice */

CREATE SERVER AUDIT SPECIFICATION [login_audit]

FOR SERVER AUDIT Server_Audit

ADD (SUCCESSFUL_LOGIN_GROUP) WITH (STATE = ON);

Configure the Audit Object Access Setting

The Audit object access setting must be configured to capture the events. The best way to do this varies depending on your operating system. To write to the Windows Security log, the account that the SQL Server service is running under must have the Generate Security Audits permission to write to the Windows Security log. By default, the LOCAL SERVICE and the NETWORK SERVICE accounts have this permission. This step is not required if SQL Server is running under one of those accounts. You must have Administrator privileges on the computer to configure these settings.

To use Auditpol.exe to configure the Audit object access setting for Windows Vista® or Windows Server 2008 or later

1. Open a command prompt with administrative permissions.

1. On the Start menu, point to All Programs, point to Accessories, right-click Command Prompt, and then click Run as administrator.

2. If the User Account Control dialog box opens, click Continue.

2. Run the following statement to enable auditing from SQL Server.

auditpol /set /subcategory:"application generated" /success:enable /failure:enable

3. Close the command prompt window.

This setting takes effect immediately.

To use Secpol.msc to configure the Audit object access setting for Windows® operating systems earlier than Windows Vista or Windows Server 2008

1. On the Start menu, click Run.

4. Type secpol.msc and then click OK. If the User Access Control dialog box appears, click Continue.

5. In the Local Security Policy tool, expand Security Settings, expand Local Policies, and then click Audit Policy.

6. In the results pane, double-click Audit object access.

7. On the Local Security Setting tab, in the Audit these attempts area, select both Success and Failure.

8. Click OK.

9. Close the Security Policy tool.

This setting takes effect immediately.

To use Secpol.msc to grant the Generate Security Audits permission to an account

1. On the Start menu, click Run.

10. Type secpol.msc and then click OK. If the User Access Control dialog box appears, click Continue.

11. In the Local Security Policy tool, expand Security Settings, expand Local Policies, and then click User Rights Assignment.

12. In the results pane, double-click Generate security audits.

13. On the Local Security Setting tab, click Add User or Group.

14. In the Select Users, Computers, or Groups dialog box, either type the name of the user account, such as domain1\user1 and then click OK, or click Advanced and search for the account.

15. Click OK.

16. Close the Security Policy tool.

This setting takes effect when SQL Server is restarted.

To stop monitoring SQL Server 2008 logon events to the Windows Security log

• If you want to stop monitoring logon events for SQL Server 2008, on each SQL Server 2008 instance for which you want to stop monitoring events, run the following SQL command.

/* Turn LOGIN logging off */

use MASTER

GO

ALTER SERVER AUDIT SPECIFICATION [login_audit] WITH (STATE = OFF);

DROP SERVER AUDIT SPECIFICATION [login_audit];

ALTER SERVER AUDIT [Server_Audit] WITH (STATE = OFF);

DROP SERVER AUDIT [Server_Audit];

Note   For more information about how to configure these security settings, see How to: Write Server Audit Events to the Security Log at http://msdn.microsoft.com/en-us/library/cc645889.aspx.

Microsoft Office SharePoint Server Usage

To capture access information for supported versions of Microsoft Office SharePoint Server or Microsoft Office SharePoint Portal Server 2003, configure the generation of Internet Information Services (IIS) logs on the servers for which you plan to monitor client access.

Note   For a list of supported versions, see Appendix A, “Supported Server Products.”

You must configure IIS logging in the W3C log file format (called "W3C Extended" on some operating systems) with the following fields included:

• date

• time

• s-sitename

• s-computername

• s-ip

• s-port

• cs-uri-stem

• cs-uri-query

• cs-username

• c-ip

• sc-status

SharePoint or IIS administrators might use W3C logging for other reasons. If these administrators require additional fields to be logged, they can add those fields to the configuration. However, administrators should not remove any of the fields that the Usage Tracker requires.

For information about enabling W3C logging in IIS, see:

• Configuring Logging in IIS 7 on Microsoft TechNet at http://technet.microsoft.com/en-us/library/cc732079(WS.10).aspx.

• How to enable logging in Internet Information Services (IIS) at http://support.microsoft.com/kb/313437.

Inventory Your Computers

The first step toward using Usage Tracker in your environment is to inventory your computers. This process involves setting up the Inventory and Assessment Wizard to use slightly different criteria than for other scenarios that MAP supports.

Note   As a best practice, inventory your environment every 90 days unless you experience significant seasonal shifts, in which case consider an assessment at the end of your busy season.

Specify Credentials

The process of identifying server roles and tracking usage in your environment requires different types of collector technology, depending on the software usage you choose to report on. Each technology requires its own credentials.

Note   For more information about how to specify credentials, see the “Discovery Methods” section in MAP Help.

These technologies are:

• Windows Management Instrumentation (WMI). Product information is found in WMI on discovered computers. The Inventory and Assessment Wizard uses this information to locate the servers that have the software you chose to track.

• System Center Configuration Manager. MAP can discover and collect hardware, software, and usage details from System Center Configuration Manager. If you want to use this method, you need to provide credentials for the SMS Provider of the Configuration Manager server you want to use for discovery. MAP collects information about all the clients managed by any Configuration Manager site known by the Configuration Manager server for which credentials are provided. To learn more about the required permissions for accessing the SMS Provider, see About the SMS Admins Group on Microsoft TechNet.

• SQL Server. In addition to WMI, MAP collects certain information directly from each SQL Server instance. If you need to collect usage information from SQL Server, you need to provide credentials to SQL Servers running on your network.

• Active Directory® Domain Services (AD DS). Microsoft Exchange mailbox and server configuration information is located in AD DS. The MAP Toolkit requires credentials that have access to read the Active Directory schema from the root forest of your environment.

Step 1: Determine Which Credentials You Require

To determine which credentials are required for your scenario, consult the following table. This table lists the inventory scenario and collector technologies that MAP requires to inventory each server product for software usage tracking. You can use a table like this to organize the information that you will need for the Inventory and Assessment Wizard.

When the account for the credentials is a domain account, include the domain name. For example, Domain\AccountName or AccountName@Domain.

Table 1. Credentials Required for Inventory

Server Product	Inventory Scenario	Collector Technology	Credentials
Windows Server	Windows-based computers	WMI	Account: Password:
System Center Configuration Manager	Windows-based computers	SMS Provider	Account: Password:
				WMI	Account: Password:
Office SharePoint Server	Windows-based computers	WMI	Account: Password:
Office SharePoint Portal Server 2003	Windows-based computers	WMI	Account: Password:
Exchange Server	Exchange Server	Active Directory	Account: Password:
				WMI	Account: Password:
		Microsoft SQL Server	SQL Server	WMI	Account: Password:
				Windows Authentication	Account: Password:
				SQL Server Authentication	Account: Password:

Note   To assess Exchange Server usage, the MAP Toolkit collects information about active mailboxes in Active Directory Domain Services (AD DS). The credentials that you provide should have the required privileges to enumerate mailboxes, groups, and users in AD DS.

To assess Configuration Manager agent count, the MAP Toolkit collects information from the Configuration Manager servers. The credentials that you provide should have adequate privileges to collect data from the Configuration Manager server you supply.

Step 2: Configure Credentials

In the Inventory and Assessment Wizard, on the Inventory Scenarios page, choose the scenario for the Microsoft server products for which you want to track software usage.

Figure 1. Inventory Scenarios page

Step 3: Choose Discovery Method

There are six discovery method options. Configuration Manager requires that the System Center Configuration Manager discovery method be used to report correctly on Configuration Manager and Microsoft Systems Management Server servers and agents. This guide describes how to use the Active Directory Domain Services and the System Center Configuration Manager methods.

On the Discovery Methods page, select the Use Active Directory Domain Services and Use System Center Configuration Manager options.

Figure 2. Discovery Methods page

Step 4: Specify Credentials

On the Active Directory Credentials page, in the appropriate text boxes, enter the domain, domain account, and password that the MAP Toolkit can use to connect to Active Directory, and then click Next.

Figure 3. Active Directory Credentials page

On the SCCM Server and Credentials page, in the appropriate text boxes, enter the name of the Configuration Manager primary site server at the top of the System Center Configuration Manager hiearchy against which you want to track usage. The primary site entered and all of its child sites will be included in Configuration Manager software usage reports. Enter the credentials required to access the Configuration Manager WMI provider on the site server you provided. Click Next.

Figure 4. SCCM Server and Credentials page

Step 5: Determine Which Method to Use to Provide Credentials

The next step in the process is to choose which method to use for providing credentials. If you choose to use the All Computers Credentials option, you will define a set of credentials that the MAP Toolkit will use to access the computers you plan to inventory.

Note   You can also opt to Enter Computers Manually or Import Computers from File. For more information about these options, see the “Discovery Methods” section in MAP Help.

Figure 5. The All Computers Credentials page before you create accounts

On the All Computers Credentials page, click Create to create the accounts that the Inventory and Assessment Wizard uses to complete the inventory process for the collector technologies (WMI, SQL Server, and so on) that you need to use, as specified earlier.

Figure 6. The Account Entry dialog box

In the Account Entry dialog box, in the Credential section, fill in the appropriate boxes to create a new account. In the Technology section, select the check boxes that correspond to the technologies to which this account applies, and then click Save to save this account or click Save and New if you need to create additional accounts.

Figure 7. The All Computers Credentials page displaying created accounts

Step 6: Sequence Credentials

After you have created the accounts that you plan to use, you can sequence the list of credentials for each collector technology. For each technology, the Inventory and Assessment Wizard will try the credentials in the order in which they appear in the list.

To sequence credentials, in the left column, click Credentials Order.

Figure 8. Credentials Order page

Step 7: Summary Review

The Summary Review page verifies that all selected scenarios have credentials listed for the appropriate collector technologies. It also verifies that at least one discovery method was chosen for identifying computers. Review the summary to ensure that you have entered all of your settings correctly, and then click Finish to start the inventory.

Note   Any verification that fails is listed as an error at the top of the review pane under the Errors node. You must resolve any errors before you can run the inventory.

Parse Logs

Note   You only need to parse logs for the software listed in the “Configure Log Files” section of this guide. If you are tracking usage on server software that does not require log files, you can skip this section and move on to the “Analyze the Results” section.

For accurate analysis of software usage in your environment, you will need to ensure that your computers have generated logs for the appropriate time period. We recommend that you have 90 days of log files generated prior to proceeding.

After you confirm that your logs have been accumulated for the appropriate amount of time, and you have finished the inventory process, you are ready to parse the logs and analyze software usage. To proceed, copy all relevant Windows and IIS logs from your servers, and store them in a location that is accessible by the computer that is running the MAP Toolkit (and by the logged on user).

Important   Before you parse the log files, ensure that you inventory the servers that created the log files you want to parse. You must connect the MAP Toolkit to the appropriate MAP database (the database that contains the inventory data of the servers from which the logs came.) This is necessary because, for proper data processing, the data from parsing the logs must be mapped to the inventoried servers. Only parse log files for supported software versions and editions. See Appendix A, “Supported Server Products,” in this document for a complete list of supported software.

To parse logs

1. In the MAP Toolkit, click the Software Usage Tracker wunderbar, and then, in the navigation pane, click Log Parsing Overview.

Figure 9. Log Parsing Overview

1. In the results pane, click Configure Log Parser.

The Specify Log File Paths dialog box opens.

2. Click the Add button.

The Browse for Folder dialog box opens.

3. Choose the directory on the local computer where the files are located. If the files are in a shared network directory, in the Folder box, type the shared path, for example \\server_name\logs\. The MAP Toolkit does not perform a recursive folder search, so you must list the full directory structure name for each location of log files you want parsed.

4. After you add all the directories where the log files reside to the Specify Log File Paths dialog box, click Save.

The Log Parsing Overview page opens.

5. Click Parse Logs.

A Status dialog box opens to show the progress of the log parsing process.

6. In the navigation pane, expand the Log Parsing Overview node and then click Log Files to monitor the results of the files as they are being parsed. The information shown is static. To refresh the pane and view the most current status, click Log Files again.

Figure 10. The Log Files pane

The Log Files pane shows data about the logs being parsed, including:

• Processed. The number of log files that have been parsed.

• Unprocessed. The number of log files that have yet to be parsed.

• Errored. The number of log files that could not be parsed completely due to errors in the format of the log file. Some events in an Errored log file may be parsed if the row that has the event is in the correct format. The Log File Details worksheet in the generated report states which log files had errors. Use this report to troubleshoot why the log could not be parsed correctly.

• Total. The total number of log files that the Log Parser attempted to parse. This value should be equal to the total number of log files in the directories you configured for the Log Parser.

• Computer System Name. The name of the server that logged the event. You can also choose to group the displayed information by Log File Name.

• Log File Name. The name of the log file being parsed.

• Events. The number of events contained in the log file.

• Start Date. The date of the first logged event.

• End Date. The date of the last logged event.

7. In the navigation pane, click Instance Summary to view a summary of the parsed data held in the current MAP database.

Figure 11. Instance Summary pane

The Instance Summary pane shows data that came from the parsed log files, including:

• Software Instance. The name of the server software that was inventoried.

• Computer System Name. The name of the computer hosting the server software. You can also choose to group the displayed information by Software Instance.

• Start Date. Event time stamp for the first event recorded in the log.

• End Date. Event time stamp for the last event recorded in the log.

• User Count. The total number of users associated with an authorized logon.

• Device Count. The total number of devices associated with an authorized logon.

Analyze the Results

The MAP Toolkit generates a series of server inventory and software usage tracking reports that you can use to significantly simplify the “true-up” process for software asset management. You can also gather this data multiple times, to analyze usage trends and plan future growth and acquisition of the necessary licenses.

Note   If you choose to gather this data multiple times, use a new MAP database each time. Information about computers that were successfully inventoried previously but have since changed would not be updated if you use an old database.

Each of these reports allows you to quickly filter results to find detailed information about each Microsoft core server product discovered during the inventory process, and authenticated access to each product. You can use these reports to help determine your server license and CAL needs for the server products.

To analyze the results, you need to:

• Review the software usage summary

• Interpret reports

• Use report data

Review Software Usage Summary

The Software Usage Summary pane provides an overview of the server and usage data collected for each server product you inventoried. In general, summary reports list the version of the product found, the total number of users, and the total number of devices that connected during a given range of time. Client access is divided into two categories: users and devices. When applicable, the type of access is divided into total and enterprise.

Figure 12. Software Usage Summary

Configure the Date Range

You can set a date range for the period of usage data you want to view. The date range that you set affects all reports under the Software Usage Summary node. For example, if you set the date range while viewing the Windows Server report pane and then traverse to the Office SharePoint Server report pane, the date range remains the same. If you want to report on data over a different period of time than you set for Windows Server usage, you will need to reconfigure the date range.

You can configure the date range while viewing any of the panes under the Software Usage Summary node.

To configure the date range

1. In the Actions pane, click the Configure Date Range task.

The Configure Date Range dialog box appears.

Figure 13. Configure Date Range dialog box

17. Click the Range drop-down list to select a given range or click Custom to set your own dates, and then click Save.

You have the option to select:

• Custom. The date range that you set must be within the span of time for which events exist in parsed logs. Therefore, it must begin no earlier than the first recorded date for an event, and end no later than the last recorded date for an event. In addition, the end date cannot be after the current date.

• Earliest to date. This option sets the date range from the earliest recorded client access date to the current date for inventoried server products. If you are viewing a combination of server products, the earliest date of any one of the combined products is used.

Note   For server products that use parsed log files, this date is the earliest date found among all log files parsed. For server products that use MAP inventory data, this date is the date of the inventory.

• Past 7 days. The past seven days including the current date.

• Past 30 days. The past 30 days including the current date.

• Past 60 days. The past 60 days including the current date.

• Past 90 days. The past 90 days including the current date.

The date range that you configure is used for all software usage reports generated and will show at the top of each report pane you view.

Note   The format for the start and end dates in the Log Files and Instance Summary panes is as follows: yyyy-mm-dd  hh:mm:ss UTC

For example, 2010-03-09  12:45:21 would be March 9th in the year 2010 at 12:45 and 21 seconds P.M. Coordinated Universal Time (UTC).

Distinct Usage of Combined Products Summary

This section compiles the count of users and devices that access at least one of the server products in the compiled list. This count is useful for special packaged CALs, such as Microsoft Core CALs, that only require one CAL per user or device to access multiple server products. A user or device that accesses more than one server product counts as one distinct usage for all products; not as one usage for each product. For example, if you select the check boxes for Windows Server, Office SharePoint Server, and Office SharePoint Server Enterprise Servers, a user who logs on to Windows Server and an enterprise SharePoint server counts as one distinct usage.

Figure 14. Combined Product Distinct Usage summary

To configure the Combined Products Distinct Usage summary

1. In the Actions pane, click the Configure Combined Products task.

The Configure Combined Products dialog box appears.

Figure 15. The Configure Combined Products dialog box

8. Select the check boxes for the products you want to combine for reporting, and then click Save.

On the Software Usage Summary pane, the list of products you chose to report on will be listed above the table that summarizes distinct usage of combined products.

Interpret Reports

You can use Software Usage reports to help verify compliance and analyze current licensing needs. Summary reports provide a count of users or devices for all servers of a given type for the date range that you configure. Detailed reports provide information about specific users or devices and the servers they accessed. You can use these reports to analyze software usage to determine whether device CALs or user CALs would more effectively meet your needs.

Software Usage reports should be used as a baseline for CAL usage analysis rather than as an authoritative summary of software usage. Additionally, the number of servers from which software usage is reported might differ from the number of servers inventoried if the security event logs for all servers are not configured to log success logon events.

Generate Reports

At any time while viewing reports in the Software Usage Summary pane or in a specific server product pane, you can generate a report. To create a report, in the Actions pane, click the Generate Report task.

If you click the Generate Report task while viewing the Software Usage Summary pane, the tool will generate a report for each server product. The Combined Products Distinct Usage summary data is not generated as a report.

To generate a report on only one product, in the navigation pane, browse to the node for the product for which you want to generate a report, and then, in the Actions pane, click Generate Report.

Note   To ensure you have the most accurate information, run an inventory just prior to parsing log files and generating reports.

Summary Results

To view a summary of the data before generating a full software usage report, expand the Software Usage Summary node in the navigation pane, and then click the name of a server product. The results pane displays an overview of the usage data for each server product version and edition.

Detailed Reports

For each server product for which you configured usage tracking, there will be a detailed report. The detailed reports, which are generated as Excel® workbooks, have inventory and usage data detailed for each server on which the product is installed. You can use the detailed report to filter for the information required for determining license usage for server product and client access.

Each detailed report has several worksheets. The following sections describe the information listed in each worksheet.

Server Summary Worksheet

This sheet lists each version of the product that was discovered and the total number of users and devices that accessed each version. Use this worksheet if you need to know about license and client access data on a per product version basis.

Farm and Server Summary Worksheet

This sheet lists each server that was found to have a supported version of Office SharePoint Server installed. This information is detected via WMI inventory. The Log File Availability column indicates whether any IIS log files were found to contain information about this server. The Sites Found in Parsed Logs column indicates whether any IIS log files were found to contain one or more accesses to sites on this particular server. When a row lists Success for WMI Status and No for Log File Availability, Office SharePoint Server was discovered on the server, but no IIS log file for usage data was parsed for that server. If a row lists Yes for Log File Availability and No for Sites Found in Parsed Logs, one or more log files were parsed for this server, but no accesses were recorded by Software Usage Tracker.

Server Details Worksheet

This worksheet lists information for each server on which the product was found during inventory. It can include such information as: installed server product, product roles configured for each server, services that the product installed, the operating system on which the product is installed, whether it is a physical computer or virtual machine, and computer hardware information, such as the number of CPUs. If you feel the Server Summary page does not give you the data you require to determine server and CAL counts, you can filter on the data in the Server Details and Client Access Details worksheets to find the information you need for your environment.

Client Access Summary Worksheet

This worksheet lists the name of each computer found to have the software product installed. For each server, the data shows the number of unique users and devices that accessed it, for the range of time you configured. Additional information for each computer may be provided for specific server products.

Client Access Details Worksheet

This worksheet lists all unique connections that accessed each server, as found in the log files. For each unique connection, the worksheet indicates the date of the most recent access to the server. A unique connection is a distinct combination of computer name, user name, and name or IP address of the device that accessed the software. This data is very detailed and can take up numerous rows in the worksheet. This is the data used to determine the total number of client and device connections to each server for a specific software product. You may need to use this data to analyze findings in summary data. You can also use the detail data to determine if anomalies you find are due to missing usage data.

Mailbox Details Worksheet

This worksheet lists all unique mailboxes and the name of the Exchange Server on which the mailbox resides. For each unique mailbox, the worksheet lists the email address associated with the mailbox, the user name of the mailbox owner and what, if any, enterprise features are assigned to the mailbox. This data is very detailed and can take up numerous rows in the worksheet. This is the data used to determine the total number of user mailboxes and enterprise user mailboxes as shown on the Overview and Server Summary worksheets. You may need to use this data to analyze findings in summary data. You can also use the detail data to determine if anomalies you find are due to missing mailbox data.

Log File Details Worksheet

Usage data for some software products is extracted from log files. For these products, the accuracy of user and device access information given in the report is based on the log files that were parsed. Use this worksheet to determine whether the correct log files were parsed and if there were any issues parsing any log files.

Note   You may find additional product-specific worksheets in some of the Usage Tracker reports. The Exchange Server Report has a mailbox worksheet that provides details about various mailboxes. The System Center Configuration Manager report does not have a Log File Details worksheet because log files are not used to track Configuration Manager servers or clients.

Use Report Data

You can use the reports that the Software Usage Tracker generates to learn a lot about software usage in your environment. Microsoft offers a series of white papers to help customers better understand product licensing and to provide guidance to simplify compliance with software licensing. You can use the information from Usage Tracker along with the guidance in these white papers to get a fairly complete view of your client access license needs. Refer to the “Additional Tools, Products and Services” section of the appropriate white paper to learn how to use the usage reports for license and CAL analysis. You can download the white papers from the About Licensing site at http://go.microsoft.com/fwlink/?LinkId=191544

For More Information

For more information about the Software Usage Tracker feature of the MAP Toolkit, refer to the sources listed below.

MAP Toolkit Help

For more information about the Software Usage Tracker, see MAP Help.

Frequently Asked Questions

For answers to frequently asked questions about the Software Usage Tracker feature of the MAP Toolkit, see the MAP Toolkit Frequently Asked Questions at http://go.microsoft.com/fwlink/?LinkId=157860.

Obtain Product Support

Support for the MAP Toolkit is provided through Microsoft Product Support Services (PSS). Premier customers should contact Premier Support for assistance. Support offerings and regional contact information for support can be found on the Microsoft Support site at http://go.microsoft.com/fwlink/?LinkId=155704.

Appendix A: Supported Server Products

The following products are supported by the Software Usage Tracker feature:

Windows Server

• Windows Server 2008 R2

• Windows Server 2008

• Windows Server 2003 R2

• Windows Server 2003

• Windows Server 2000

Microsoft SQL Server

• SQL Server 2008 R2

• SQL Server 2008

Microsoft Office SharePoint Server

• Office SharePoint Server 2010

• Office SharePoint Server 2007

• Office SharePoint Portal Server 2003

Microsoft Exchange Server

• Exchange Server 2010

• Exchange Server 2007

• Exchange Server 2003

System Center Configuration Manager

• Configuration Manager 2007 R2

• Configuration Manager 2007

• Systems Management Server 2003 R2

• Systems Management Server 2003

Additional Information

All editions of the listed server products that require a server license are reported in the Software Usage Tracker report for that server product.

SQL Server 2008 Enterprise and Datacenter editions are the only SQL Server editions that MAP Toolkit will report usage on. All other editions will be reported on for server license information.

Appendix B: Examples of Limiting Scenarios

There are a variety of reasons why the information that the Software Usage Tracker gathers could be inaccurate. This appendix describes some of those reasons.

The discovery methods you choose in the Inventory and Assessment Wizard are not able to find all computers in your environment. For example, if you choose the IP Address Range method and the IP addresses for some servers are outside of the configured range, those servers would not be inventoried.

One or more servers did not accept the credentials provided to log on to WMI. If no configured credentials are accepted by the remote server, the inventory for installed server software cannot occur and no server products will be associated with the computer name.

One or more servers were not turned on during discovery or inventory. If a discovery method is chosen that requires MAP to browse for computers on a network, those computers that are turned off will not be discovered and placed in the MAP database. Also, even if a server that is turned off is discovered, such as in Active Directory Domain Services (AD DS), MAP would still not be able connect to the server to complete the inventory process.

Missing log files. Missing log files for Windows Server, SQL Server, and Office SharePoint Server can cause the count of users and devices that access those servers to be incorrect.

Incorrectly configured log files. Windows event and IIS log files that are not configured to the specifications described in this guide will prevent the correct usage count to be parsed from these logs.

Computers aren't connected to the network. The inventory process determines which computers have a System Center Configuration Manager agent running on them. If the inventory occurs when one of these computers is not connected to the network, such as when a mobile computer is used outside of the network, agents running on these computers will not be counted.

Appendix C: Manually Determine Office SharePoint Server Edition

This appendix describes how to use manual methods to determine which edition of Office SharePoint Server you are running.

Microsoft Office SharePoint Portal Server 2003

Office SharePoint Portal Server 2003 did not license in the same way as newer versions so the concept of “Standard” and “Enterprise” is not relevant. Depending on the context, the Usage Tracker reports accesses to this version as Standard or Not Applicable (N/A).

Microsoft Office SharePoint Server 2007

To view your current license type for Microsoft Office SharePoint Server 2007

1. On the Central Administration home page, click the Operations tab.

18. In the Upgrade and Migration section, click the Enable Enterprise Features link.

If your farm is Enterprise, the Enterprise option is selected, with the controls dimmed to indicate that they are unavailable.

Figure 16. Enterprise Feature Set Selected

Otherwise, the Standard option is selected and the controls will be active to allow you to upgrade to Enterprise.

MAP inventory looks at a registry key on the system to determine whether a server running Office SharePoint Server 2007 is Enterprise or Standard. The registry location for Office SharePoint Server 2007 is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ Office Server\12.0. The key named OfficeServerPremium will have the value 1 for an Enterprise server, and 0 for a Standard server.

Microsoft Office SharePoint Server 2010

To view your current license type for Microsoft Office SharePoint Server 2010

1. On the Central Administration home page, click the Operations tab.

19. In the Upgrade and Migration section, click the Convert farm license type link.

If your farm is Enterprise, the Current License section will indicate SharePoint Server with Enterprise Client Access License.

Figure 17. Current License Set as Enterprise Client Access

If your farm is Standard, the Current License section will indicate SharePoint Server with Standard Client Access License and controls will be active to allow you to upgrade to Office SharePoint Server with an Enterprise Access License.

MAP inventory looks at a registry key on the system to determine whether a server running Office SharePoint Server 2010 is Enterprise or Standard. The registry location for Office SharePoint Server 2010 is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ Shared Tools\Web Server Extensions\14.0\WSS\InstalledProducts. Within this location, there will be keys named with GUIDs. The following values for the key named with the GUID {90140000-110D-0000-1000-0000000FF1CE} indicate license type:

• 88BED06D-8C6B-4E62-AB01-546D6005FE97 = Enterprise trial

• D5595F62-449B-4061-B0B2-0CBAD410BB51 = Enterprise licensed

• B2C0B444-3914-4ACB-A0B8-7CF50A8F7AA0 = Standard trial

• 3FDFBCC8-B3E4-4482-91FA-122C6432805C = Standard licensed

iv MSDN 2.0

Template User Instructions iii

microsoft.com/solutionaccelerators

microsoft.com/solutionaccelerators

Guide Title iii

iv Guide Title

Software Usage Tracker User Guide 17

microsoft.com/solutionaccelerators

24 Microsoft Assessment and Planning Toolkit

Software Usage Tracker User Guide 25

---