Here’s the latest news of the month for all MSP’s and SPLA providers. Enjoy!
SQL 2017
This month is a month we will remember for the rest of our lives. That’s right, today SQL 2017 is available to run on…a non-Microsoft system?
From the licensing guide: “SQL Server 2017 now supports deployment on RedHat Enterprise Linux (RHEL), Ubuntu, and SUSE Linux Enterprise Server (SLES). The SQL Server 2017 SKUs are platform agnostic, so customers can run the software on either Windows or Linux.” (check it out here)
What this means for those anti-Microsoft lovers is a customer who demands SQL can now install SQL 2017 on a Linux machine and not report Windows. The machine cannot run any Windows guest VM’s for it not to be reported. Pay attention to that last sentence as we get asked a lot about licensing individual VM’s instead of the actual host. In Windows licensing, you license the physical host, not the VM’s. If there are 100 Linux VM’s and only 1 Windows VM, you must license the host with Windows Datacenter to be in compliant.
Azure Stack Availability
The long await is over – Azure Stack is now shipping through the OEM channel (Dell, Lenovo, HPE) You can read more about this announce here From a licensing perspective, I think it is less expensive to license Windows through SPLA than pay as you use model. It’s more of a predictable cost in my opinion. This is one way Microsoft is attempting to extend Azure (public cloud) into your private cloud and have the best of both worlds.
“Hit Refresh”
Satya Nadella “Hit Refresh” book is available at a time when we are all in a strange way, hitting refresh. The cloud transformation is only getting more complex – hybrid, dedicated, Google, AWS, Azure, every company is transforming to try and get the slightest edge over their competitors. I look forward to reading it and every dollar goes to Microsoft charities. Regardless of what you think of Microsoft, Satya seems like one of the good guys. You can check out more about the book here
More to come –
Thanks for reading,
SPLA Man
Like this:
Like Loading...
Tags: AWS, Azure, Azure stack, Cloud Solution Provider Program, CSP, Digital Transformation, Google, Hit Refresh, Hybrid cloud, Microsoft, Microsoft Licensing, Microsoft SQL Server, Satya Nadella, spla, SQL 2017
Quick update for those interested in Dynamics 365 for SPLA and what you should remember when selling to your customers.
- No Enterprise Plans in SPLA
- No PowerApps in SPLA
- Transitions SKU’s are available in SPLA
- More differences found here
Not all bad news but not all good either. You can read more about my opinion here
Thanks for reading,
SPLA Man
Like this:
Like Loading...
Tags: Azure, Cloud Solution Program, Dynamics, Dynamics 365, Dynamics CRM, Hosting, Microsoft, Microsoft Cloud, microsoft CSP, Microsoft Hosting, MicrosoftSPLA, MS Cloud, O365 Enterprise Plans, Powerapps, SaaS, spla, SPLAlicensing
Where can I get my license keys for CRM? My Microsoft contact can’t seem to find the answer and my reseller doesn’t know either. Any ideas?
For CRM and D365 you can download them directly from the VLSC website. All other Dynamics products need to go through the License Key Creator Tool.
If I am a CSP Tier 1/direct provider, can I sell CSP to another CSP Tier 1 provider?
Yes. There are no limitations as to who you can sell to. Good luck!
Is CSP replacing SPLA?
Not entirely. I am not Microsoft but I can see the similarities. In the end, they are both Microsoft programs, how they consume it doesn’t really matter. The only drawback to SPLA (In Microsoft’s eyes) is the service provider has the option of offering other software outside of Microsoft. Exchange as an example, could technically be replaced with Zimbra. If they use Office 365, the customer is using Office 365.
I offer desktop as a service. When can we expect VDI to be available in SPLA?
Never.
Will I get audited?
Yes. Make sure to read the MBSA agreement that you signed.
Thanks for reading,
SPLA Man
Like this:
Like Loading...
Tags: audits, CRM, CSP, CSP Direct, CSP Tier 1, desktop as a service, Dynamics 365, Microsoft, Microsoft Cloud, microsoft CSP, Microsoft SPLA, VDI, Zimbra
In this edition of The Cloud Insider Times, you will find articles on the likes of Google, Amazon, IBM, Veeam, and the infamous Shared Computer Activation (among others) If your company would like to be included in future articles, please email info@splalicensing.com
Like this:
Like Loading...
Tags: Amazon, AWS, Azure, BetaNews, bluelogix, BusinessCloud Media, Cloud Computing, Cloud Solution Program, Cloudyn, CNBC, Computer Business Review, CSP, Forbes, Google, google cloud, Healthcare, Microsoft, Microsoft Cloud, Microsoft SPLA, myanalytics, Office, Office 365, Private Cloud, shared computer activation, The Register, Yahoo, ZDnet
Article update (April, 2018 ) This article can be found at https://mscloudlicensing.com/2018/03/06/licensing-sql-2016-and-windows-2016/ We review best practices in reducing audit exposure, use rights and guidelines for SPLA licensing.
Like this:
Like Loading...
Tags: container virtualization, containers, Core licensing, Datacenter Ousourcer, ESX, fail-over, hyper thread, hyper-V, License Mobility, Microsoft, nano-server, spla, SQL, SQL 2016, SQL Enterprise, Windows 2016, Windows Server
We created The Cloud Insider Times as a way to provide valuable content to the splalicensing.com reader. Each week our team will search the web for relevant information as it relates to SPLA and other cloud related technologies and solutions. Have a question or hot topic or would like to be added to “The Cloud Insider Times” Contact me at info@splalicensing.com
Thanks for reading,
SPLA Man
Like this:
Like Loading...
Tags: Applied Innovations, Azure, Cloud, Cloud Computing, cogeco, Datacenter outsourcing, Datapipe, FP Web, Hostway, IBM, Microsoft, Microsoft SPLA, Peek 10, Peer 1, Project Hosts, Pronet Solutions, Rackspace, RoseASP, spla, TierPoint, Veeam, Virtustream
The healthcare community has increased concerns with the way they have deployed (and licensed) their electronic medical record (EMR) software such as Epic Community Connect and others. As a reader of this blog, you know that when you deploy software for the benefit of a third party (non employee) SPLA must be part of the conversation. The only exception to this rule is if you actually own the code to the software you are hosting. In other words, if you developed the software, you can use your own volume licenses to host your software. If you host a third party software (such as Epic) you must license this in SPLA. In most cases, many healthcare companies do not own the application, but lease it from the EMR vendor.
Rewind a few years and let’s pretend you are a large hospital who partnered with Epic to provide best in class patient record management for your clients, doctors, and other clinics. Your Epic deployment resides on a Windows Server, SQL Server, and RDS. As the IT director, you purchased several server licenses and hundreds of Client Access Licenses (CAL) to cover all the external users. You think you are covered; no one mentions you need to license this via SPLA. Your reseller didn’t tell you, Microsoft didn’t tell you, and for that matter the vendor didn’t tell you. You think all is well based off the information you received. Fast forward 3 years and your volume licensing agreement is up for renewal. Someone on the licensing side informs you that you shouldn’t true-up licenses or renew your agreement under volume licensing, you need to license SPLA. You think that’s fine, if you must license under a different program who are you to argue. But what about all those license you already purchased and own? Unfortunately, you cannot return them, you must allocate those internally. You think to yourself that’s fine, except for one minor detail…. you purchased hundreds of CALs and you do not have hundreds of employees; those license you own are essentially worthless. On top of everything else, you just received an audit notification.
Why would they receive an audit notification? Once a vendor recognizes you have been under-licensed, the vendor might want to dig in deeper to see how long you have been out of compliant and if you purchased enough licenses to cover all the users. In 90% of all audits, the customer is under-licensed. Now you own licenses you don’t need, but should’ve purchased more because you don’t own enough licenses to cover all external users initially. The vendor will want you to pay the delta of what you should’ve paid under SPLA and what you purchased under volume licensing (plus an audit fee).
If you are a healthcare provider and have been notified by Microsoft or any other vendor, please contact us. We have found that in many cases the licenses report is not always 100% accurate.
Thanks for reading,
SPLA Man
Like this:
Like Loading...
Tags: 3rd party software, Client Access Licenses, Datacenter outsourcing, EMR Hosting, Epic Community Connect, Epic Software, Hosting, Microsoft, Microsoft Audit, Microsoft Azure, Microsoft Cloud, Microsoft Compliance, Microsoft SPLA, Office 365, self Hosted, spla, SQL Server
Yes, it’s the talk of the town. “Windows 2016! Oh my! It’s moving to cores!!!” That part is true. What is NOT true is even when Windows 2016 is released, it doesn’t mean you have to license by core – you can still license by processor for all 2012 and earlier editions. The catch? Once your agreement expires and you sign a new SPLA after October 1st (when Windows 2016 is released) you must license by core regardless which version you are running.
So what does this mean to you? If I was a service provider that reports over 2k in Windows and SQL licenses, I might readjust when my SPLA expires to extend processor based licensing. Wait…What? You can readjust when my SPLA agreement expires? Sure. I’m SPLA Man. Anything is possible with SPLA Man.
Thanks for reading,
Windows 2016 Man
Like this:
Like Loading...
Tags: Hosting, Microsoft, Microsoft Cloud, Microsoft SQL, Processor Licensing, Service Provider User Rights, spla, SPUR, SQL Server, technology, WIndows, Windows 2016, Windows Core Licensing, Windows Server
For those that read my earlier post “Predicting the future” one intuition has already come true. Microsoft announced price increases for Microsoft Dynamics CRM come January, 2015.
All 3 SPLA CRM SKU’s are effected (Basic, Essentials, and Service Provider/PRO edition). For complete breakdown I would suggest reaching out to your SPLA reseller.
So why the increase? Microsoft stated “The CRM price change is intended to more closely align our online and on premises pricing.” So there you have it.
Windows, Core Infrastructure Suite (CIS) and other Dynamics AX, NAV, GP will also see increases. This was previously announced by Microsoft and communicated through the reseller channel.
Thanks
SPLA Man
Like this:
Like Loading...
Tags: Cloud Solution Program, Core Infrastructure Suite, CRM, CRM Basic, CRM Essentials, CRM Professional, Dynamics 365, Dynamics AX, Dynamics CRM, Dynamics GP, Dynamics NAV, Hosting, Microsoft, Microsoft Cloud, Microsoft Hosting, Microsoft SPLA, Price Increases, Service Provider Licensing Agreement, spla
It’s easier than you think. ( and no, I am not saying you should be out of compliant). The goal of this blog is to educate and help the service provider community with their licensing decisions. Keep in mind that I do this as a hobby. I also try not to solicit, as that can be frustrating to the reader.
That being said, I do know the reseller channel well, I also know the agreement better than most lawyers. If you are looking to potentially reduce your spend from a reporting perspective, reduce compliance risk, or just simply want to chat about a licensing scenario that can be unnerving, let me know. Send me a message on LinkedIn or shoot over an email – blaforge@splalicensing.com
So how do you reduce your spend? That’s a tough question without a quick answer. I would have to review your report to understand exactly how you can potentially reduce costs. Nonetheless, I’ll give her a try. Here’s my top 3 ways service providers can reduce their licensing costs –
1. Run multiple instances of SQL on the same VM. A little blurb in the SPUR states “For each virtual OSE for which you have assigned the required number of licenses….you have the right to run any number of instances of the software in that virtual OSE” (page 23 of the SPUR for your boredom). Keep in mind, there’s a difference between running an “instance” and running a VM.
2. License the Core Infrastructure Suite (CIS) to run Windows and System Center Servers. If you are reporting System Center and Windows separately….STOP! System Center needs Windows. In other words, you have to report Windows regardless; might as well pay less.
3. Do not report Windows Standard….report Windows Datacenter. You have the option of running unlimited VM’s with Datacenter edition. If you are reporting Windows Standard, that means you are not virtualized. Get virtualized.
One more for good measure…
4. SAL for SA – I still don’t understand why service providers do not report this SKU. It’s less expensive, your customer can still deploy on premise and in your cloud, and you will be unique. (I’ve only seen it reported once).
There are many more ways to reduce spend. (even outside of simply licensing/virtualizing, etc.) There’s too many scenarios to review on a blog post. How about this trade off – If I can reduce your spend, you owe me a beer at a hosting conference. (joke for the record). If I can’t, at least you know your reporting correctly.
Thanks,
SPLA Man
Like this:
Like Loading...
Tags: CIS, Core Infrastructure, Licensing Mobility, Microsoft, SAL for SA, spla