6. Platinum Sponsor
Pre-audit Health Check Process
ITAM Review Microsoft Seminar, London 17th September 2015
Gather
Entitlement
Gather
Deployment
Allocate
Entitlement
Update ELP
Optimize
Resolve
Gaps
Iterative
Continuous
Process
7. Platinum Sponsor
Gather Entitlement
ITAM Review Microsoft Seminar, London 17th September 2015
Gather POL
Update (your)
Effective
Entitlement
Reconcile to
VLSC
Resolve
Omissions
Update
Entitlement
DB
Continuous
Process
8. Platinum Sponsor
Gather Deployment
ITAM Review Microsoft Seminar, London 17th September 2015
Identify
Sources
Normalize
Deployment
Report
Usage
(CALs)
Assign
State
Continuous
Process
12. Platinum Sponsor
Gap Resolution Options
ITAM Review Microsoft Seminar, London 17th September 2015
• Uninstall / Decommission
• Consolidate
• Optimize
• Purchase – but on your terms
13. Platinum Sponsor
Takeaways
ITAM Review Microsoft Seminar, London 17th September 2015
• It’s about adding Process to your
Tools
• It’s an iterative process
• Validate & Reconcile your
sources of information
• Start early before it’s an audit
14. Platinum Sponsor
Are you STILL ready for an audit?
ITAM Review Microsoft Seminar, London 17th September 2015
15. Platinum SponsorITAM Review Microsoft Seminar, London 17th September 2015
piaras.macdonnell@suredatum.com
@PiarasMacDonnel #ITAMtips
Editor's Notes
Good afternoon everyone, my name is Piaras MacDonnell from Suredatum and we help companies reduce their Microsoft license costs.
My presentation today will focus on Microsoft License Pre-Audit Healthchecks.
So what is that?
It’s an internal audit you conduct BEFORE you receive that “letter” from Microsoft
Why should I care?
Although we’ll be focusing on audits today there are many reasons why you’d want to do a pre-audit healthcheck.
Are we buying the right software (Enterprise, core based, CALs, etc)?
Do we already have it (stock taking)?
Are we using the software we already have?
Today we’ll be focused on preparing for an audit but there are many benefits to doing regular health checks
So will you get audited?
Why you should care
This is a summary of some research from Gartner tracking the frequency of vendor audits.
As you can see it’s been increasing year on year until now the likely hood of an audit is around 70%.
The lesson to take from this is that audits are no longer about compliance but are a Sales tool being used to generate a compelling event or a sense of urgency to purchase.
Whether you have an EA, are about to make a significant purchase or have spent nothing in the last few years you are still an audit target.
Let me have a show of hands
Who here today thinks they are ready for a Microsoft audit?
Do you have a plan to be ready for an audit?
Is anybody here audit exempt?
I am sure all of you here have SAM tools to support your business. Tools used correctly will help but they are not the complete solution.
They are only as good as the data they hold.
In your business today you have accounting systems that help you keep track of stock, invoices, payments, etc. These are regularly reconciled to ensure their accuracy. If there are gaps you track down the problem and resolve it.
This is the same thing, just for Microsoft licensing. You must have the processes and other data sources to ensure your data is accurate and you are confident.
It’s also worth noting that bad quality data in your tools can go against you in an audit as it’s a record of non-compliance should you receive a full audit.
Pre-audit Health Check Process
I’m going to go through the typical steps in a pre audit health check. The steps are:
Gather Entitlement
Gather Deployment
Allocate Server Entitlement
Update ELP
Optimize
Resolve Gaps
It is important to remember that this is a iterative process, getting better each time you do it. It is also a continuous process as no organization’s IT remains static.
Gather Proof of License
Collect all the PoL that relate to your organizations
Contracts, Agreements, invoices, emails to VAR or Account Manager.
For OEM it might letters of confirmation
Example: Purchases put through under a different SKU, only letter from VAR documented the process
Update (your) Effective Entitlement
This is your record of entitlement. It will change over time due to the impact of SA.
e.g. Server 2008 R2 with SA becomes Server 2014
e.g. Purchase of Upgrades rather than new licenses
Reconcile to VLSC / MLS
This is Microsoft record of entitlement and you need to review this regularly as this is the starting point for an audit.
Resolve Omissions
Work with your LAR or Microsoft to update their records. The gathered POL becomes invaluable at this point.
What ever happens get a response from Microsoft on any omissions.
Updated Entitlement DB (or SAM Tool)
You should flag this as reconciled (or not) and reference the evidence (POL, email, etc.) supporting it.
What ever happens get a response from Microsoft on any
Areas to pay attention too:
Versioning & Downgrade Rights
Software Assurance (SA)
end dates
Current entitlement
Purchased Upgrades
OEM
3rd Party Apps (bundles & embedded)
Organization Change
Decentralised Purchase
Reconciliation
Identify Sources
Minimum Information needed:
Desktop – installed s/w
Servers – Installed s/w & h/w configuration (CPU, cores, etc)
VMWare – VM to host mapping, hardware config, clustering, vMotion, etc
Active Directory – devices and users
Common Sources:
SCCM, MS MAP,KACE, SNOW, etc.
Also be manually prepared sheets
Not just one
Normalise
Deduplication
Apply downgrade rights
Remove ‘noise’ patches, runtimes, etc.
Consistent naming
Deployment Report
Desktop straight forward but server more complex due to virtualisation, core counts, etc.
Often need to go outside tools or scripts to handle server deployment.
No matter what the tool used it is recommended that you spot check this report.
Usage (CALS)
This is a complex area and a challenge for some tools. Examples SQL server or Exchange Enterprise
Simple approach and the one that auditors start with is to get CALs for everyone in your organization. This process is about proving that not everyone needs a CAL for all products.
Example: Where a few employees need access to the latest SQL server 2012, you don’t want to buy CALs for the entire organization
Assign State
The state directly impacts the license required
Production
QA
Training
Academic
Dev
Backup / DR
Naming conventions help, as does a well maintained AD
RISKS
Desktop Deployment Risks
Normalisation (dups, downgrades, etc)
Edition mismatch with entitlement
Multi installs Standard + Pro
OS Upgrades
CAL Deployment Risk
Device verses User
Exchange Enterprise Feature
Exchange Active Sync / OWA
Impact of server upgrade
CAL’s less that total user count
Server Deployment Risk
Virtualisation
vMotion
Counting Serve Cores
4 core minimums
Core factor
Desktop Apps on Server
Citrix and VDI
SQL
2008 -> 2008 R2
Mixing
SharePoint Enterprise Features
Exchange, etc
Allocating Entitlement
Allocating desktop entitlement is relatively straight forward just be careful where you have device and user based license.
Server entitlement is a complex process and as the licensing rules change so does the optimum deployment.
The swings in the required license can be dramatic, 1+1=3
Factors that impact this are:
Virtualization
SA
Status of server
Version and Edition
Clusters
Update the ELP
This all culminates in an Effective License Position (ELP).
This report must cover ALL Microsoft products. It should show where the is over & under licensing.
It will also indicate where you are likely to have a current or future risk.
If anyone would like a sample please email me after.
Optimize
With your ELP you can now see areas to optimize how you are using your licenses.
Examples: Dual installs of Office across an org after a company wide upgrade.
When you do find an area for optimisation find the root cause and prevent it happening again.
The standard areas for optimization are:
Desktop
Remove duplicate installs
Reclaim unused installs
Validate requirement for Pro verses Standard edition
Validate requirement for expense products (visio, project, etc)
Server
Migrate Physical to Virtual
Consolidate SQL to dedicates servers
Validate requirement for Enterprise Features
Remove Desktop apps
VDI
Enforce small security groups for access
Multiple Profiles
Gap Resolution Options
There will be gaps, especially on the first pass. If you do it early, before an audit, you have the following options:
Uninstall / Decommission
Consolidate (move to VM or cluster)
Optimize
Purchase – but on your terms
If you do need to purchase you can now do it on your terms, with discounts.
Don’t Wait!
If you received any notice from Microsoft you will have no other option but to purchase, on their terms
Takeaways
After hearing all that do you still feel you are ready for an audit?