RSS

Monthly Archives: September 2016

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

 

 

 

Advertisement
 
Leave a comment

Posted by on September 29, 2016 in VDI

 

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

Worried about Windows 2016 Cores?

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

 
13 Comments

Posted by on September 9, 2016 in Windows 2016

 

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

 
%d bloggers like this: