Sam HenrySenior Manager, WW Sales EnablementMicrosoft Developer Tools

Customer BriefingHow to Count Deploymentsand License Assignments

AgendaDiscussion Points Decision Points• Why MSDN?• Benefits that drive your ROI• Additional cloud capacity• How to stay on top of MSDN

subscription management?• Your next steps and checklist

• Bulk registrations assistance?• Other stakeholders to include?

MSDN Administration

Enterprise Enrollment Contacts

Primary Notices Contact

Online Administrator

Subscriptions Managers (Teams)

Software Advisor (Reseller)

1. Understand benefits and limitations of MSDN subscriptions

2. Assign MSDN subscriptions to specific, named individuals

3. Accurately inventory your non-production environment

4. Track user assignment changes and acquire additional licenses on schedule.

Four ResponsibilitiesWho is responsible for MSDN?

MSDN Administrators play an important role in the management of your company’s licensing and you should be prepared to participate in and provide data inputs for monthly assignment changes, incremental license purchases, and annual True Ups

Governing DocumentsResponsibilities, Best PracticesScenarios and QuestionsContractual Terms

Developer Tools (User License)“You must assign each license to a single user”

Step #1:

‘Anyone interacting’

Per the Product Use Rights document, MSDN software may not be used in a Production environment.

To understand what the customer may fairly claim is a Dev/Test environment, you must first rule it out as a Production environment.

“A production environment is defined as an environment that is accessed by end users of an application (such as an Internet Web site) and that is used for more than Acceptance Testing of that application or Feedback. Some scenarios that constitute production environments include:

• Environments that connect to a production database• Environments that support disaster-recovery or backup for a production

environment• Environments that are used for production at least some of the time,

such a server that is rotated into production during peak periods of activity”Source: Visual Studio 2013 and MSDN Licensing Whitepaper – November

2013 (pg 12)

Definition of Production Environment:

If you are unsure whether a physical server or operating system environment should be considered Production, apply the following test:

Can you take this environment, and any data that it is consuming, offline permanently without impacting end users?

If the answer is “no”, you should treat the machine in question as Production.

Two Options for DevTest EnvironmentsDev and test environments change a lot. And software asset management for these environments can be challenging.

MSDN subscriptions provide an extremely flexible, cost-effective way to equip your teams and license your dev and test infrastructure.

Typical Stakeholders

Typical Environment

1. developers and testers

2. IT operations

3. business analysts and product owners

DEV & TEST SERVERS

TEST LABS

Team Productivity

Shared Environments

LOAD AGENTS

How to count (Part 1)

All Machines

DevTest Infrastructure

DevTest Users

To differentiate between production and dev/test software, you must first develop a comprehensive understanding of all installed Microsoft software. Using Software Asset Management tools and techniques, customers may ‘back out’ production machines to identify the remaining as dev/test.

Team Description Contact #

Software Engineering TeamsTargeting Microsoft or other platforms like Java

Business Teams‘Product Owners’ and business analysts

Project Management TeamsCentral PMO and software project managers

Quality TeamsCentral QA team and manual testers

IT Operations TeamsPre-production and lab infrastructure managers

Anyone who ‘interacts with software’

Exception for end users

Team Description Contact #

End User Acceptance TestersInvolved at end of project to review and approve

Production Machines

DevTest Machines

Identify DevTest machines by eliminating production ones from your complete inventory.

Identify and categorize users who interact DevTest machines directly or indirectly

User Credits

Competency ProductSilver Competency Gold Competency

Core Added

Total Core Added

Total

Application Development

Visual Studio Premium

5 5 10 10 25 35

Application Lifecycle Management

Visual Studio Premium

5 - 5 10 - 10

Visual Studio Ultimate

- 1 1 - 5 5All licenses provided by MPN partners must be certified by:

• Declaration of MSDN Ownership by each partner provided to Microsoft

You may use these licenses for:

• Development of internal systems to support your business.

• Development of commercial ‘packaged’ applications to sell to customers.

These licenses do not cover revenue-generating activities, such as:

• Developing custom solutions for a customer.

• Integration or customization of a packaged solution for a customer.

As part of your partnership with Microsoft, partners receive a number of free Microsoft Visual Studio licenses for internal use to help you grow and run your business. The exact benefits vary based on your MPN partnership level and competencies.

Microsoft Partner Network

Offshore Development Centers

ODC StaffProvided by Customers

Provided by System Integrator

All license provided by customers must be certified by:

• Declaration of MSDN Ownership by each ODC customer provided to Microsoft

Exchange Server

SharePoint Server

SQL Server 1

SQL Server 2

Windows Server

Technical PM

IT Pro

Tester (Non-coding)

Developer 2

Developer 1 Exchange Server

SharePoint Server

SQL Server 1

SQL Server 2

Windows Server

Technical PMUnlicensed

IT ProUnlicensed

Tester (Non-coding)Visual Studio Professionalwith MSDN

Developer 2Visual Studio Professionalwith MSDN

Developer 1Visual Studio Premiumwith MSDN

Exchange Server

SharePoint Server

SQL Server 1

SQL Server 2

Windows Server

Technical PMUnlicensed

IT ProUnlicensed

Tester (Non-coding)Visual Studio Professionalwith MSDN

Developer 2Visual Studio Professionalwith MSDN

Developer 1Visual Studio Premiumwith MSDN

Exchange Server

SharePoint Server

SQL Server 1

SQL Server 2

Windows Server

Visual Studio Premiumwith MSDN

MSDN Platforms

MSDN Platforms

MSDN Platforms

Step #2:

‘High water mark’

Purchasing MSDN subscriptions

Using Visual Studio and/or MSDN software incurs a purchase obligation and includesInstalling

Configuring

Running

Viewing

Otherwise interacting with

Assigning MSDN and/or Visual Studio with MSDN subscription licenses to users is a right customers do not have without making a purchase and indicates strong evidence of software usage

Reconciling software usage with corresponding purchases must be done annually for EA at True Up and monthly for Select

Understanding, monitoring and accurately communicating your company’s usage when assigning subscription licenses and/or distributing Visual Studio and/or MSDN software to users is the responsibility of the MSDN Administrator

Know the key issues related to MSDN licensing and usage

Customer purchases MSDN subscriptions on EA

MSDN Administrator assigns purchased subscriptions to users

Customer’s dev team increases in size

MSDN Administrator assigns additional subscriptions to new users

Customer’s dev team decreases in size, Admin deletes subscriptions

Customer purchases over-assigned subscriptions at True Up based on high water mark of usage

Managing MSDN subscriptions

Contractual Requirement to Assign

“You must assign each license to a

single user”

“Your company's obligation to purchase MSDN subscriptions takes effect immediately at two different times.  First, when you assign MSDN subscriptions to users your obligation to purchase takes effect immediately at the time of assignment, regardless of whether that user later activates and/or uses that subscription.  Second, when users interact with MSDN software your obligation to purchase takes effect immediately at the time of interaction, regardless of whether that user has been assigned an MSDN subscription (or has a subscription level of non- specific in VLSC).  Your complete purchase obligation is determined by the high watermark of usage, which is determined by the higher of daily user assignments and/or users interacting with MSDN software.”- MSDN Administrator’s Guide

High Water Mark Definition

Ma

y,

20

12

Jun

e,

20

12

July

, 2

01

2

Au

gu

st,

20

12

Se

pte

mb

er,

20

12

Oc

tob

er,

20

12

No

ve

mb

er,

20

12

De

ce

mb

er,

20

12

Jan

ua

ry

, 2

01

3

Fe

bru

ary

, 2

01

3

Ma

rc

h,

20

13

Ap

ril

, 2

01

3

2 7 5 2 7 6 2 7 7 2 7 8 2 7 9 2 8 0 2 8 1 2 8 2 2 8 3 2 8 4 2 8 5 2 8 6

4046 45

49 4955

59

6771

8681

34

49 4953 56 57 60

65 65 64 66 65

19

MSDN Subscription Assignments and reductions by Month

Visual Studio Premium with MSDN Visual Studio Professional with MSDN

Visual Studio Ultimate with MSDN

Months

Nu

mb

er

of

MS

DN

Su

bsc

rip

tion

Ass

ign

men

ts

High Water Mark of Assignments

“when you assign MSDN subscriptions to users your obligation to purchase takes effect immediately at the time of assignment”

Step #3:

Accelerator Template

DevTest Environment Assessment

GlobalMAPS

Accelerator

Template

You

Microsoft

Reseller

GlobalMAPS

Accelerator Template

DevTest Machine

s

DevTest Users

User Assignm

ents

Partner Declarati

ons ODCDeclarati

ons

Where Data Comes From Where It Goes

1. Automated tools like MAPS

2. Microsoft Volume Licensing Services Center

3. Manual inputs from end users

1. Software Asset Management

2. Annual True Ups

Sample Outcome

MSDN Subscription Levels

Current License Assessment

High Water Mark Owned Licenses GAP

VLSC (High)

MAPS (Usage) MLS User

Declarations Diff

VS Ultimate 190 205 200 2 -3VS Premium 110 100 100 2 -8VS Professional 45 62 50 5 -7VS Test Pro 30 45 50 0 0MSDN Platforms 50 0 50 0 0MSDN OS 5 0 5 0 0Total 430 412 455 9 -18

Thank you!

How to count

All Machines

DevTest Infrastructure

User CreditsDevTest Users

Begin with assumption that all infrastructure is production. Impossible to differentiate MSDN software from VL software.

Team Description #

Software Engineering TeamsTargeting Microsoft or other platforms like Java

Business Teams‘Product Owners’ and business analysts

Project Management TeamsCentral PMO and software project managers

Quality TeamsCentral QA team and manual testers

IT Operations TeamsPre-production and lab infrastructure managers

Anyone who ‘interacts with software’

Exception for end usersTeam Description #

End User Acceptance TestersInvolved at end of project to review and approve

Team Description #

Partner Type #1Microsoft Certified Partners (ALM Gold or Silver)

Partner Type #2Staff Augmentation Contractors

Microsoft Certified Partners

Team Description #

Customer Type #1Full IT BPO outsourcing

Business Teams #2Offshore Development Center

Project Management TeamsCentral PMO and software project managers

Customers of Outsourcers

Production Machines

DevTest Machines

Anyone who ‘interacts with software’

NEXT STEPS: Your Checklist1. Review the docs. Be sure to read the PUR, MSDN Administrators Guide, and

Visual Studio and MSDN Licensing Whitepaper.

2. Develop your schedule. Review your Microsoft Volume Licensing terms so you can be prepared to provide data inputs for license assignment changes, monthly Select or Open orders, incremental license purchases, and annual Enterprise Agreement True Ups.

3. Define your process. A clear process for adding, removing, and managing user changes over time is important.

4. Build your team. Identify internal contacts and external partners who can help you keep track of environment changes and users who “interact with MSDN software.”

5. Automate usage inventory. Automated tools like System Center or MAP can help you identify your dev and test environment—desktops, servers, and users.

6. Automate user assignment tracking. The Volume Licensing Service Center is a good place to keep track of your “high water mark” of MSDN assignments.

7. Get help. Contact your MSDN Administration Services representative for help!

Three Steps to Counting

1. Current Footprint• MSDN High Water Mark of Assignments• Inventory users of DevTest infrastructure

2. Owned Licenses• Microsoft License Statement (MLS) • Declaration of MSDN Ownership from Microsoft Partners

3. Gap Comparison• Annually for Microsoft Enterprise Enrollments• Monthly for Select and Open Enrollments

Timeline Estimate for First TimersKickoff and notification

Run the MAPS Toolkit MAPS Accelerator Template

MSDN Subscription

Levels

Current License Assessment

High Water Mark Owned Licenses GAP

VLSC (High)

MAPS (Usage) MLS 3rd

Party Diff

VS Ultimate 190 205 200 2 -3

VS Premium 110 100 100 2 -8

VS Professional 45 62 50 5 -7

VS Test Pro 30 45 50 0 0

MSDN Platforms 50 0 50 0 0

MSDN OS 5 0 5 0 0

Total 430 412 455 9 -18

License GAP Assessment

T-3