RSS

Tag Archives: Cloud Solution Program

VDI Under SPLA? Maybe it’s possible after all – Multitenant Hosting Rights for Windows 10

Good news for those who have customers who want you to host Windows 10 in your shared cloud environment –  they might now have that as an option.  Microsoft recently announced “Multitenant Hosting Rights for Windows 10.  You can read the announcement here 

We also created a new website called MSCloudlicensing to help SPLA and CSP partners understand the different program options and use rights available to them. The new website is www.mscloudlicensing.com it’s designed to be a collaborative platform that includes a forum to ask and answer licensing questions, document library, and licensing articles.  Check it out, it’s free.

What is it?

Allows customers who purchased qualified Windows 10 licenses the ability transfer those licenses over to a Qualified Multi-Tenant Hoster shared datacenter environment.

Why is this important?

For years SPLA partners have asked for VDI in SPLA.  Although this is not technically VDI in SPLA, is does provide an avenue to implement a virtual desktop session from your shared server environment.  At the end of the day, it gives your end customers deployment options.

Can I still license Windows Desktop in SPLA?

No.  Windows desktop licenses were removed last year.  You can read/download the lease agreement that outlines the details here

What are the requirements?

To no surprise, the SPLA partner must be CSP Tier 1 authorized.  They must also sign the Qualified Multitenant Hoster addendum and have an active SPLA with Microsoft.  To get the QMH (another Microsoft acronym) you can contact info@splalicensing.com or your Microsoft Reseller.

What happens if I offer dedicated environments?  Do I still need the addendum?

No.  If it is 100% dedicated (isolated hardware) you can always transfer end customer  licenses over to your datacenter environment.  Whenever it is shared – VM or hardware, you must consider SPLA or in this case the QMH addendum)

When is it available?

Program will be available August 1, 2017 for VL and September 6, 2017 to transact in CSP.

Can I bundle my customers Office solution they purchased as well as Windows 10 to offer a complete VDI experience?

Yes.  This is a great way to bundle different desktop applications.

Conclusion 

If you provide IaaS to your customers, this is definitely something you should consider.  Any time you can offer your customers the ability to leverage existing investments the better.  Azure is not going away.  In fact, you don’t have to be QMTH authorized to leverage Azure as your datacenter provider.  Please review the announcement, there will be a lot more information on this in the coming days.  I will also write out several scenarios to make this more simple.  As always, you can email me at info@splalciensing.com

Thanks for reading,

SPLA Man

 

 

Advertisements
 
2 Comments

Posted by on July 12, 2017 in Office 365

 

Tags: , , , , , , , , , , , , , , , , , ,

Top 5 Compliance Trends for MSP’s and SPLA

There are so many license changes and gotchas with SPLA, Azure, AWS, and all the others that I thought I would highlight for you some of the trends we see when it comes to compliance.

  1. Licensing Office Standard when Office Professional is installed.  In many cases, an IT administrator will inadvertently install Office Pro, report Office Standard to their procurement team who in return reports it to the reseller.  The IT admin will leave the company, and the procurement team continues to report Standard not knowing Pro is installed until audit time.  In this situation, Microsoft will check when Office was installed, and take the delta of what was reported (STD) v. what should be reported (Pro).  Don’t make this mistake.  Many partners are only charging their customers for Standard pricing!
  2. Not reporting SPLA at all.  Sounds silly, but many providers focus on developing software and not on the licensing.  We have found instances in which the procurement manager (who was in charge of reporting SPLA) left the organization and no one else took over their responsibility.   The reseller continues to email the procurement manager but obviously the email goes unnoticed.  After many months, their SPLA will be terminated and all licenses will have to be trued up.  The problem with this scenario is not just unexpected licensing expense, but when your SPLA terminates, you must sign a new one.  When you sign a new SPLA, you must adhere to the latest SPUR use rights.  As an example, if you had a SPLA prior to the Windows core licensing change, you could continue to report processors.  If your SPLA terminates, you would be forced to license by core now instead of later when your previous agreement (that is now terminated) expired.
  3. Using a VL copy of Office to deploy Shared Computer Activation (SCA).   SCA is specific to Office 365.  If you install Office Pro Plus VL, it goes against the product use rights in which Office (without SCA) cannot be installed on shared hardware.  It takes a lot of negotiation power and time to prove you are SCA eligible, the customer purchased Office 365, and you inadvertently installed the wrong product.
  4. Using License Mobility without License Mobility.  This is by far the most popular compliance trend.  Many organizations do not know what is installed in their datacenter when it comes to customer owned licenses.  Be sure to have the right documentation, addendum, and licensing to ensure compliance.
  5. Leasing an application, hosting the application, and purchasing volume licensing agreement to offer software as a service.   A healthcare company may lease an EMR application, host the application to other healthcare organizations, and license the infrastructure through volume licensing.  If your organization does not own the application you are hosting, you must license it through SPLA.  Self-Hosted for ISV is only eligible for providers who develop and own the application.  This means the code, the rights, everything must be owned by the organization.  Leasing the application and using other plugins you may have developed does not qualify.

I hope this provides you a little insight into the world of compliance.  If you find yourself out of compliant, let us know and we can connect you to the right resource.  info@splalicensing.com

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on July 5, 2017 in Compliance

 

Tags: , , , , , , , , , , , , , , ,

More Dynamics 365 Fun

Quick update for those interested in Dynamics 365 for SPLA and what you should remember when selling to your customers.

  1. No Enterprise Plans in SPLA
  2. No PowerApps in SPLA
  3. Transitions SKU’s are available in SPLA
  4. 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

 
Leave a comment

Posted by on June 1, 2017 in Dynamics 365

 

Tags: , , , , , , , , , , , , , , , ,

The Cloud Insider Times

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
Computer Business Review – Three Private Cloud Myths Busted!
 
Leave a comment

Posted by on April 20, 2017 in The Cloud Insider Times

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , ,

Exchange 2007 support ended. What does that mean for you?

This past weekend I was forced to buy new running shoes.  I run 3-4 times a week, and my philosophy had always been if not’s broke, don’t fix it.  Recently, my shoes started to feel heavy, my feet started to hurt, and I knew it was my body telling me to change (something).  After googling (sorry binging) different causes for running pain, one of the top results came up “change your running shoes.”  I then proceeded to look at my shoes more closely and noticed the bottoms were worn, the shoe itself was very flexible ( bends easily – a bad thing) and realized my shoes were no longer the shoes I once I loved.  It was time to upgrade.   In a strange way, my buying decision is similar to most IT departments.  If it’s not broke, don’t fix it until we absolutely have to.  For consumers running older versions of Exchange, that time is now.  This past week, Exchange 2007 support has gulp…ended.

One (of the many) reasons customers move to the cloud is outdated technology.   When something as critical as security updates, product updates, etc. are no longer available, customers start looking for other solutions.  In the case of Exchange, customers either upgrade on premise (which also means upgrading their hardware)  or finally start thinking about the cloud.  Now that can mean good news for you (if you are an Exchange hoster) or bad news if you haven’t started the conversations with your potential clients.  It’s also great news for Office 365.

I would  guess that Microsoft is looking at all end customers who purchased Exchange 2007 but haven’t upgraded to Exchange 2010.  Those customers  are all  prime for Office 365 conversations.   Every Office 365 distributor and reseller are also reaching out to these customers.  Check out Sherweb, Intermedia (one of Microsoft’s largest Exchange hosters), and Rackspace Every single one of them are not saying “go to our cloud” when exploring migration options, the top reason is “Migrate to Office 365”

If your company has not investigated getting into the CSP game or partnering, the time is now.  I’m not selling you on Office 365, I am selling you to watch out for the competition.  As mentioned above – SherWeb, Intermedia, and Rackspace are all hosting Exchange but they are also promoting Office 365 through product support life cycles.   One way to stay ahead of the competition, is to know when product life cycles end and which products are impacted.   For a list of product support updates and life cycles check out https://support.microsoft.com/en-us/lifecycle/search

Thanks for reading,

SPLA Man

 

 

 

 

 
Leave a comment

Posted by on April 17, 2017 in In My Opinion, Uncategorized

 

Tags: , , , , , , , , , ,

Why Windows 10 in CSP stinks now but could be GREAT later

Microsoft made a pretty big announcement around Windows 10 and CSP.  Here’s a breakdown for those that are interested:

  1. Software Assurance is not included
  2. Windows 10 is available E3 and in CSP only
  3. Customers need a qualified OS license.  In other words, this is an upgrade license only.
  4. Not available under SPLA
  5. Not available in the shared computer activation model.
  6. Per user licensing with the ability to license on up to 5 devices per license.
  7. No minimum and surprise…no maximum either.
  8. Subscription is 1 year
  9. Pricing varies
  10. New use rights highlighted in the Product Terms

So why does this stink now but could be great later?  Pay attention to number 1, 4, and 5 in the list above.  That’s what stinks.   Think this will allow VDI?  Think again.

So why not?  Why the mystery around VDI and SPLA?  If I was Microsoft, I would go ahead and allow it but for only a select few SPLA providers.  Those providers are:

  1. Report on time.  Not one late payment/report during their agreement no matter what the excuse – “My reseller sucks” is not an excuse.  It’s a good reason to work with me though 🙂
  2. Deployed Hyper V (they must have some incentive to do this)
  3. Joined CSP program.

There you have it.  Microsoft wins big time – all that missed revenue from non reporters will get reported. Now you, the compliant service provider, will be allowed VDI in SPLA.

The likelihood of this happening is slim to none.  I do think Microsoft is missing out with the Windows 10/VDI restriction.  Ever since I started in SPLA, I’ve been asked about VDI (or the lack thereof).  That was 11 years ago.

Thanks for reading,

SPLA Man

 

 

 

 
Leave a comment

Posted by on September 29, 2016 in VDI

 

Tags: , , , , , , , , , , , , , , , , , , , , ,

“I want VDI!!!!!”

You probably have said that a thousand times as a service provider.  The truth is it’s still not available in SPLA.  If I was a betting man (big if by the way for those that work for the IRS) I would wager they would allow VDI in SPLA.   Why not…right?  Everything else is changing why not this?  Before you get too carried away as to why Microsoft will not allow VDI in shared environments, let me ask…do you REALLY want VDI?  Just as SQL is complex in SPLA (and VL for that matter) so is VDI.  In this article I will review the licensing rules with VDI/VDA and what exactly needs to happen if you were to host this from your datacenter.

Let’s take scenario 1.  Bill has a PC that can run a qualified operating system but the PC itself has been running slow recently.  He get’s his email from Joe’s Hosting so logically he asked good ole’ Joe if he could host a virtual desktop as well.  Joe tells him  “Sure” but it MUST be dedicated and his cost will go up.  Bill tells him that’s not issue, his wife won the lottery recently.  You would think the last thing Bill would be worried about is a virtual desktop.  Just buy a new computer Billy and head to the beach!  Nonetheless, Bill wants VDI and wants it now.  Joe’s Hosting tells him to go to the store, buy a Windows 10 license, and bring that disc over to their datacenter.  Joe will host it on a server solely dedicated to Bill.  Problem solved.  Joe is happy he just won over a customer, Bill is happy he gets his virtual desktop.  The compliance police call, Joe is in trouble.  Why?

In order to host VDI 3 things must happen.

  1. The PC must have VDI use rights. This means the desktop license itself (Windows 10 as an example) must be Enterprise and have active Software Assurance (SA).  Think of VDI as a Software Assurance benefit.  Without SA, no chance of having VDI.  In order to buy Software Assurance, I would need a volume licensing agreement; not a retail version.
  2. The service provider must indeed host it in a dedicated infrastructure.  This means the hardware, not just the VM.
  3. If the PC is incapable of running a full version of Windows 10 (such as a tablet) the customer must purchase a VDA license.  VDA is a use right that allows the end user the right to access a virtual desktop from a server environment.

The 3 items mentioned above is really just the beginning of the licensing roller coaster.  You must also license Windows Server, RDS, and any other applications by your SPLA or be purchased by your end customer.  If they are purchased by the end customer, they would transfer that license into your datacenter, which means they can no longer run it on premise.

Now I ask you this question – is VDI worth it?  Some say “yes” as this is what the customer wants and mean old Microsoft licensing rules just keep getting in the way.  Most complain about dedicated environments, but as mentioned earlier, dedicated environments is just the beginning.  Last, you may say the licensing of the VDI environment is not your problem, it’s your customers.  You have it hosted in a dedicated environment.  As far as SPLA is concerned, you are covered.  Or are you?

Maybe I’ve been doing this too long and I am just an old fogey.  But if I was a customer and my service provider (you) told me I could receive my VDI dedicated infrastructure and all I need was a desktop OS license, I would be all in.  Fast forward a couple years and you tell me you are going through an audit and apparently I (not you) had licensed VDI incorrectly and it’s my fault; I think I would be a little upset.  Yeah I would ditch you faster than that girl in 9th grade who ditched me at the dance (apparently when I told her my future involved SPLA licensing it turned her off…what a fool) but I would also make sure if any other organizations were looking at you as a service provider, I would tell them to stay away.  As any marketing organization would tell you, recommendations and word of mouth is the best way to advertise.

Moral of this story?  Like all the rest, know the licensing first, sell it second.  Stay tuned for scenario 2.  Your customers will thank you.

Thanks for reading,

SPLA Man

 

 
6 Comments

Posted by on February 1, 2016 in VDI

 

Tags: , , , , , , , , , , , , ,

 
%d bloggers like this: