Microsoft Licensing Primer
-
So you are saying my original theory was right? That I can spin it up only once (for less than a week in that instance) every 90 days?
-
@BRRABill said:
So you are saying my original theory was right? That I can spin it up only once (for less than a week in that instance) every 90 days?
Yes. That is what it means.
-
Since it is December and hopefully e-mails from ML are flowing again, let's see if we can get an official chime in from @Chris .
-
@JaredBusch said:
@BRRABill said:
So you are saying my original theory was right? That I can spin it up only once (for less than a week in that instance) every 90 days?
Yes. That is what it means.
I called MS to confirm this today.
You were 100% right.
Once every 90 days, and only with SA.
-
@BRRABill said:
@JaredBusch said:
@BRRABill said:
So you are saying my original theory was right? That I can spin it up only once (for less than a week in that instance) every 90 days?
Yes. That is what it means.
I called MS to confirm this today.
You were 100% right.
Once every 90 days, and only with SA.
No SA is required for this per our MS rep. Though all we do spin them up with no network connection and the shut them right back down. Once per quarter.
-
@Jason said:
No SA is required for this per our MS rep. Though all we do spin them up with no network connection and the shut them right back down. Once per quarter.
You might want to check on that.
It's only allowed once every 90 days WITH SA.
-
@BRRABill said:
@Jason said:
No SA is required for this per our MS rep. Though all we do spin them up with no network connection and the shut them right back down. Once per quarter.
You might want to check on that.
It's only allowed once every 90 days WITH SA.
That's not what our EA Rep says. We have checked on it many times.
-
I believe you are referring to cold/standby licensed backup servers. Which is a right under SA's standby server rights but that is highly different then making sure a live backup boots and then turning it back off, there is no 90 day restriction either, if you have SA you can also use Standby servers.
Also if you have Azure for your DR site then you don't need anything. All windows base licensing is covered.
-
@Jason said:
I believe you are referring to cold/standby licensed backup servers. Which is a right under SA's standby server rights but that is highly different then making sure a live backup boots and then turning it back off, there is no 90 day restriction either, if you have SA you can also use Standby servers.
Also if you have Azure for your DR site then you don't need anything. All windows base licensing is covered.
What do you mean a "live backup" ... if you boot a copy of server up for 1 second you need another license for it. MS has no disaster recivery rights.
With SA, you can boot it once every 90 days.
@scottalanmiller I am sure will chime in here to support this...
-
A bit offtop:
Isn`t MS is the only company who has certification program for its licensing? -
@BRRABill said:
@Jason said:
I believe you are referring to cold/standby licensed backup servers. Which is a right under SA's standby server rights but that is highly different then making sure a live backup boots and then turning it back off, there is no 90 day restriction either, if you have SA you can also use Standby servers.
Also if you have Azure for your DR site then you don't need anything. All windows base licensing is covered.
What do you mean a "live backup" ... if you boot a copy of server up for 1 second you need another license for it. MS has no disaster recivery rights.
With SA, you can boot it once every 90 days.
@scottalanmiller I am sure will chime in here to support this...
That's not true. SA is what gives you disaster recovery rights and you can keep this live backup DR running as a cold site as long as it's not being actively being used for production.
We're on Enterpise so we don't need SA to test backups, but you do need SA for Diaster recovery on other hardware and no you do not need a second windows license for a replicated DR copy.
-
@Jason said:
That's not true. SA is what gives you disaster recovery rights and you can keep this live backup DR running as a cold site as long as it's not being actively being used for production.
That is what the whole latest discussion was about. That the usage rights for SA state:
The backup Instance can run only during the following exception periods:
ā¢ For brief periods of disaster recovery testing within one week every 90 days;
ā¢ During a disaster, while the production Server being recovered is down; and
ā¢ Around the time of a disaster, for a brief period, to assist in the transfer between the primary production server and the disaster recovery Server. -
@Dashrender said:
man, you guys have completely left out Software Assurance, which can be a HUGE savings here.
One step at a time. Microsoft Licensing is a beast, that even they themselves don't understand.
-
@BRRABill said:
@Jason said:
That's not true. SA is what gives you disaster recovery rights and you can keep this live backup DR running as a cold site as long as it's not being actively being used for production.
That is what the whole latest discussion was about. That the usage rights for SA state:
The backup Instance can run only during the following exception periods:
ā¢ For brief periods of disaster recovery testing within one week every 90 days;
ā¢ During a disaster, while the production Server being recovered is down; and
ā¢ Around the time of a disaster, for a brief period, to assist in the transfer between the primary production server and the disaster recovery Server.The second line is the part that Jason had mentioned.
-
@scottalanmiller said:
The second line is the part that Jason had mentioned.
When @Jason said "SA is what gives you disaster recovery rights and you can keep this live backup DR running as a cold site as long as it's not being actively being used for production"
I thought he meant the server was constantly running. Not just being booted up once every 90 days.
And I still think you need SA for this. I do not believe it is allowed without SA.
-
@BRRABill said:
And I still think you need SA for this. I do not believe it is allowed without SA.
On not normally licensed hardware yes.
To boot up on the same hardware to test when you have enterprise no.
-
-
This requirement for SA has really foxed me. How do people without SA perform Disaster Recovery testing? It's almost impossible isn't it? But if it's impossible, how to companies get away without have any DR testing?
And you don't just need SA on your Windows licence do you? You need SA on all your applications, SQL Server, Exchange, Sharepoint etc etc
-
Am I right in thinking a Windows licence is effectively assigned to a physical host rather than to individual VMs running on that host?
So if I had a DR/Lab host, used purely for testing, and purchased a single Windows Server Standard licence, could I run various different VMs on the box provided I never had more than two VMs running at the same time? So I could test a DC and Exchange, then shutdown Exchange and restore Sharepoint and test that? Is that how it works? (I appreciate I would need SA or separate licences for the applications eg Exchange and Sharepoint)
-
@Carnival-Boy said:
This requirement for SA has really foxed me. How do people without SA perform Disaster Recovery testing? It's almost impossible isn't it? But if it's impossible, how to companies get away without have any DR testing?
They buy multiple licenses.
It's been my understanding that larger shops typically don't run into this because they either have Datacenter Edition, or just buy enough licenses to cover it. It has also been brought to my attention you could do it the old fashioned way. Actually perform a test disaster recovery.
I assume a lot of places just look the other way, because it makes no sense to follow the licensing. Kind of like doing 56 in a 55.
But to each their own...
