virtualboy blog

Matt McSpirit on Virtualisation, Management and Core Infrastructure

Are you a Hosting Partner? Running Hyper-V? Thinking about it? Read this.

Are you a Hosting Partner? Running Hyper-V? Thinking about it? Read this.

  • Comments 3
  • Likes

If you’re a Hosting Partner, your licensing is quite different to the regular type of licensing that most Partners/Customers fall under, and in some instances, the licensing is actually more complex for Hosters!  How does the complexity increase further?  Virtualisation, as per usual!

Well, a whitepaper has landed on my desk which is up to date, and goes into a good level of detail around Hosting & Virtualisation, but also SQL 2008 and System Center.

“This white paper documents common hosting scenarios using Windows Server® 2008 Hyper-V™ virtualization technology and Microsoft SQL Server® database management software with the Microsoft Services Provider License Agreement (SPLA). The SPLA has two licensing models – Per Processor and Per Subscriber (via a Subscriber Access License, or SAL). Some products are available through both licensing models. In a virtual environment, there are no new restrictions on the number of instances running under the SAL licensing model. However, the Per-Processor model introduces new considerations, which are outlined in this white paper.

The primary focus of this paper is how to license different editions of Windows Server 2008 and SQL Server 2008 in a virtualized hosting environment that is leveraging the SPLA model. We will outline the SPLA licensing implications for some common Hyper-V-based virtualized hosting scenarios. These scenarios include:

  1. Unmanaged dedicated server with Hyper-V
  2. Virtual dedicated server (VDS) for Web scenarios (using Windows Server guests in anonymous mode)
  3. Virtual dedicated server with line-of-business (LOB) scenarios (using Windows Server guests in authenticated mode)
  4. Use of virtualization in shared hosting scenarios
  5. Desktops as Hyper-V guests
  6. End customers running Microsoft products using the customers own licenses on the guest OS

In addition to these common scenarios, we present how the Microsoft System Center family of products can be used to help manage the virtualized hosting environment and the associated licensing implications.”

The document also goes into useful detail around a number of typical hosting scenarios, such as managed, unmanaged, authenticated, unauthenticated and so on.  Definitely worth a read.

You can pull the document down from here.

  • Great guide. At last something out of MS we can all understand, thanks for sharing.

  • Hi

    i'm read this doc, but not understand a one.

    what is "Anonymous Datacenter" and  "the guest operating systems need to run in unauthenticated mode"?

    if i'm right - Datacenter host and virtual machines on it can't be AD Server

    They can join to Windows domain as member? They can accept connections from domain users? or they must be standalone servers with local users only?

    If you can give link to the official Microsoft answer on this - i'm be very glad.

    very thanx, sorry for bad english.

  • Hi,

    This is now old information - at the time, Hosters were not allowed to rent Windows Server Datacenter edition and provide it to their customers for use in an authenticated scenario i.e. integrated with Active Directory.  The only option in that scenario was Enterprise edition, which wasn't as attractive because each licence only gave you 4 free Guest OS's instead of unlimited like Datacenter editon.

    Now however, this has changed, and there is more info here:



Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment