Kooler on DFS-R Issues
-
@bigbear said in Kooler on DFS-R Issues:
@KOOLER originally we were talking about Hyper-V free but @scottalanmiller indicated it requires a CAL for whatever that SAN product is
Which I guess runs on Windows server???
The linked article in OP says hyper-v free
Hyperv is free, this doesn't mean that you may legally be required to user Microsoft Server to perform the job at hand.
-
All I want is a clarification on what licenses are supposedly required here.
That you can do something on a Microsoft OS (Hyper-V in this case) means nothing. Microsoft has never been about locked down compliance.
If it requires a Server 2012 R2 license and then CALS, it is simply Server 2012R2 + Hyper-V roles, even if you only installed Hyper-V Server 2012 R2.
If it somehow only requires user CALS, then great.
-
@bigbear said in Kooler on DFS-R Issues:
@KOOLER originally we were talking about Hyper-V free but @scottalanmiller indicated it requires a CAL for whatever that SAN product is
Which I guess runs on Windows server???
The linked article in OP says hyper-v free
I didn't mention CALs. Was someone else.
-
@JaredBusch said in Kooler on DFS-R Issues:
All I want is a clarification on what licenses are supposedly required here.
That you can do something on a Microsoft OS (Hyper-V in this case) means nothing. Microsoft has never been about locked down compliance.
If it requires a Server 2012 R2 license and then CALS, it is simply Server 2012R2 + Hyper-V roles, even if you only installed Hyper-V Server 2012 R2.
If it somehow only requires user CALS, then great.
Nah, you don't need anything except CALs.
-
@KOOLER said in Kooler on DFS-R Issues:
@JaredBusch said in Kooler on DFS-R Issues:
All I want is a clarification on what licenses are supposedly required here.
That you can do something on a Microsoft OS (Hyper-V in this case) means nothing. Microsoft has never been about locked down compliance.
If it requires a Server 2012 R2 license and then CALS, it is simply Server 2012R2 + Hyper-V roles, even if you only installed Hyper-V Server 2012 R2.
If it somehow only requires user CALS, then great.
Nah, you don't need anything except CALs.
That doesn't make sense to me... that you can clearly violate the license terms and the whole point of Hyper-V Server as long as you have CALs?
-
@Tim_G said in Kooler on DFS-R Issues:
@KOOLER said in Kooler on DFS-R Issues:
@JaredBusch said in Kooler on DFS-R Issues:
All I want is a clarification on what licenses are supposedly required here.
That you can do something on a Microsoft OS (Hyper-V in this case) means nothing. Microsoft has never been about locked down compliance.
If it requires a Server 2012 R2 license and then CALS, it is simply Server 2012R2 + Hyper-V roles, even if you only installed Hyper-V Server 2012 R2.
If it somehow only requires user CALS, then great.
Nah, you don't need anything except CALs.
That doesn't make sense to me... that you can clearly violate the license terms and the whole point of Hyper-V Server as long as you have CALs?
What licenses would you resolve it with?
-
@KOOLER said in Kooler on DFS-R Issues:
@JaredBusch said in Kooler on DFS-R Issues:
All I want is a clarification on what licenses are supposedly required here.
That you can do something on a Microsoft OS (Hyper-V in this case) means nothing. Microsoft has never been about locked down compliance.
If it requires a Server 2012 R2 license and then CALS, it is simply Server 2012R2 + Hyper-V roles, even if you only installed Hyper-V Server 2012 R2.
If it somehow only requires user CALS, then great.
Nah, you don't need anything except CALs.
I'm confused. As far as I know it @JaredBusch is correct.
-
@bigbear said in Kooler on DFS-R Issues:
@Tim_G said in Kooler on DFS-R Issues:
@KOOLER said in Kooler on DFS-R Issues:
@JaredBusch said in Kooler on DFS-R Issues:
All I want is a clarification on what licenses are supposedly required here.
That you can do something on a Microsoft OS (Hyper-V in this case) means nothing. Microsoft has never been about locked down compliance.
If it requires a Server 2012 R2 license and then CALS, it is simply Server 2012R2 + Hyper-V roles, even if you only installed Hyper-V Server 2012 R2.
If it somehow only requires user CALS, then great.
Nah, you don't need anything except CALs.
That doesn't make sense to me... that you can clearly violate the license terms and the whole point of Hyper-V Server as long as you have CALs?
What licenses would you resolve it with?
Windows Server Standard or Datacenter. To use "Windows features" of Hyper-V in a non-Hyper-V support role requires normal Windows licensing. It's a Windows VM that you are using. The exemption from licensing is only for very specific Hyper-V management functions. Otherwise you must license as normal.
You'd still need CALs too of course. But additionally. Not instead of a server license.
-
With Starwind's coming Linux release (or has it already been released?)... Would this not be done in a Linux VM? That would eliminate concerns about licensing and such.
-
@dafyre said in Kooler on DFS-R Issues:
With Starwind's coming Linux release (or has it already been released?)... Would this not be done in a Linux VM? That would eliminate concerns about licensing and such.
The KVM release should fix this, yes.
-
@dafyre said in Kooler on DFS-R Issues:
With Starwind's coming Linux release (or has it already been released?)... Would this not be done in a Linux VM? That would eliminate concerns about licensing and such.
-
StarWind Linux VSA is released
-
There's no problem to install anything like us into parent partition, question was is it OK to use it as a file server with a free version of Windows
-
