Presentation is loading. Please wait.

Presentation is loading. Please wait.

SAM for Non-production Environments Presenter Name.

Similar presentations


Presentation on theme: "SAM for Non-production Environments Presenter Name."— Presentation transcript:

1 SAM for Non-production Environments Presenter Name

2 Non-production environments Today, more and more companies develop their own custom software. As the number of employees engaged in software development increase so does the complexity of managing licensing within this environment.

3 Who benefits from a non- production SAM engagement? A non-production SAM engagement is not just for companies developing custom software. The special considerations associated with tracking and managing software that is not licensed for production use mean that this engagement could benefit all businesses running any type of non- production lab environment.

4 Complex, dynamic, ever-changing Modern non-production environments: characterized by change It can be difficult for an organization to: Understand how non-production systems are deployed, developed and tested upon, decommissioned, and rebuilt Get a clear picture of the organization’s software footprint Understand the licensing subscriptions available Understand who needs to be licensed

5 Non-production SAM engagement Understand licensing options Get a clear pictures of your organization’s software footprint Increase efficiencies Optimally manage your environment A customer focused SAM engagement will help you:

6 Non-production SAM engagement benefits Gain a better understanding of how developer tool licensing works Receive value from your licensing investments Reduce costs through operational efficiencies Incorporate standardization across management of company assets Improve internal licensing communication Establish a solid foundation for achieving future organizational objectives

7 Non-production environments SAM engagement: Step 1 Gather preliminary information about the existing environment, future goals, and security concerns Organizational Profile Licensing Considerations Development, Testing, User Acceptance Testing, Staging Infrastructure Environment People involvement Basic information about the organization People

8 Non-production environments SAM engagement: Step 2 Inventory deployed software build a detailed report on your current state The report will match installations with licenses

9 Non-production environments SAM engagement: Step 3 Report on key findings and guidance We will review with you: Non-production vs. production: Discuss differentiators between non- production and production environments and updates to product use rights (PUR). Common licensing mistakes: Review common over-licensing and under- licensing mistakes. Licensing options: Walk through challenges of managing licensing and licensing options available. Best Practices: Review best practices for navigating the non-production environments, managing software licensing subscriptions and consolidation of non- production environments. Policies and Guidelines: Based on our findings we will have a good understanding of how we can help your organization create policies for managing your non-production environments going forward.

10 Typical interview questions Do you engage in software development and testing on-site? Have you used external consultants during the current licensing agreement term? How do the developers test their software? Do they access the development environment? Are they licensed under your agreements or the 3rd party’s? If licensed by the 3rd party, can you provide documentation of this? Is this consistent across all divisions of your company? How many Microsoft platform/.NET developers? How many IT pros, Architects, PMs, Testers, Database Administrators and non-Microsoft developers access non-production servers running Microsoft software? How many of those users are interacting with non-production Lync, Exchange, SharePoint, BizTalk and Dynamics servers? Which types of roles manage testing? Who is overseeing moving software projects through the development, testing, User Acceptance Testing, staging to production cycle? How do you mange decommissioned servers?

11 Under-licensing mistakes that are commonly made Buy Cheap, Use Expensive Buy Few, Use Many Expired MSDN Unlicensed Outsourcing MPN Benefit Misuse Incorrectly Licensed Non-production Customer uses more products than they purchased and fails to order/True Up Customer without active MSDN subscription uses latest version of product Customer uses outsourced development workforce internally and neither party pays to license those users MPN partner uses MPN licensing to provide software development services and/or exceeds MPN benefit entitlement cap Customer uses MSDN software on Development/Test servers without licensing all users reaching those environments Customer uses higher product edition(s) than they purchased and fails to order/True Up

12 Over-licensing mistakes that are commonly made Buy Expensive, Use Cheap Buy Many, Use Few Wasted MSDN Overlicensed Outsourcing Wasted MPN Benefit Overlicensed Non-production Customer purchases Premium and/or Ultimate editions but Administrator fails to assign and users cannot access Customer uses fewer products than they purchased and fails to deploy or renew down, renews unused software Customer with an active MSDN subscription does not take advantage of new version, Office production* and Azure use rights Customer uses outsourced development workforce internally and both parties pay to license those users due to miscommunication MPN partner qualifies for MSDN benefits but does not take advantage of them Customer purchases or renews more MSDN subscriptions than are needed in order to license all users reaching those environments

13 Licensing options for non-production environments Visual Studio and Visual Studio with MSDN Products Ultimate 2013 With MSDN Microsoft Premium 2013 With MSDN Microsoft Test Professional 2013 With MSDN Microsoft Professional 2013 With MSDN Microsoft Platforms Microsoft Operating Systems 2012 Microsoft msdn Professional 2013 Microsoft Professional 2013 Upgrade Microsoft MSDN subscriptions Stand-alone tool

14 MSDN Platforms Software, services, support, training: MSDN Platforms is a licensing option for non-developers that provides your organization cost effective and convenient access to wide range of resources. Lowers software acquisition costs Simplifies licensing Empowers your teams Increases agility

15 Topics covered by SAM Policies and processes MSDN Administrator in place Example policy: It is advisable that customers perform frequent software inventories to keep their non- production subscriptions up to date. Performing frequent self-audits include reviewing if employees are still with the company and if they have the correct licensing subscriptions. Regularly scheduled software inventories Ongoing employee training Maintenance and processes Defining processes, roles and responsibilities Training Employees, vendors, and others accessing organizational resources Post production guidelines for decommissioned servers

16 The path forward How optimal is your environment? Production Non-production Test Dev MSDN Are you taking full advantage of cost savings? Are there any licensing issues to discuss?

17 Next steps and Q&A


Download ppt "SAM for Non-production Environments Presenter Name."

Similar presentations


Ads by Google