Random Thread - Anything Goes
-
@hobbit666 said in Random Thread - Anything Goes:
@DustinB3403 @JaredBusch
That's what I wanted to hear, means we may be able to defer (if that's the term) buying new CAL's until we are migrating the VM's to 2019. Would it matter how the CAL's were purchased (I'm trying to track how/when/what at the moment)Using the Microsoft licensing center has been the "easier" approach I've used, as it stores your purchases right there.
Of course @scottalanmiller would disagree here as he's had a hell of a time using that licensing center.
-
@DustinB3403 Think that's where ours are, just checking once I find our login
-
@hobbit666 said in Random Thread - Anything Goes:
OK so take this as an example.
Server A license 2012 Datacentre
300 2012 User Cals
2012 DC VM & 2012 App/FileServerWe are migrating to new hardware
Server B 2019 Datacentre
Migrate the two VM's (So staying with 2012)
Do I need to purchase new CAL's? Or will the others transfer because the VM's are the same?Or is it a case the CAL's only need replacing when we upgrade or install a VM to 2019?
How can Server B be "2019" if there is no 2019 VM? Doesn't make sense. Servers don't have levels, only VMs have levels. Once you install 2019 anywhere, then you need CALs everywhere.
-
@DustinB3403 said in Random Thread - Anything Goes:
Because you are migrating to 2019 on Server B, as the host, but your VM's are unchanged, and your users are hitting 2012, and not 2019 you shouldn't need to purchase 2019 CALs.
This is incorrect. 2019 is "used to support the resources" so if 2019 gets installed, CALs need to be upgraded at that time. No way to keep the users in the real world from benefiting from it. Any VMs that run on top of it will be using it, for example.
-
@hobbit666 said in Random Thread - Anything Goes:
@DustinB3403 @JaredBusch
That's what I wanted to hear, means we may be able to defer (if that's the term) buying new CAL's until we are migrating the VM's to 2019. Would it matter how the CAL's were purchased (I'm trying to track how/when/what at the moment)But ANY install of 2019 is a VM of 2019, so there is no time you can use the term like you are using, where CALs are not needed.
CALs are CALs, how they are purchased does not matter.
-
@scottalanmiller said in Random Thread - Anything Goes:
How can Server B be "2019" if there is no 2019 VM? Doesn't make sense. Servers don't have levels, only VMs have levels. Once you install 2019 anywhere, then you need CALs everywhere.
Simple Server B will have a 2019 Datacentre OEM license stuck on it
-
@scottalanmiller said in Random Thread - Anything Goes:
CALs are CALs, how they are purchased does not matter.
I thought if you didn't have Software Assurance you could "Move" the license to new hosts? Or is that just a Server License thing (or RDS)?
-
@JaredBusch said in Random Thread - Anything Goes:
@DustinB3403 said in Random Thread - Anything Goes:
Because you are migrating to 2019 on Server B, as the host, but your VM's are unchanged, and your users are hitting 2012, and not 2019 you shouldn't need to purchase 2019 CALs.
Correct, you can have domain members of any level.
He does unless he's doing something really weird. But since the assumption is that he's installing a license-required 2019 control VM for Hyper-V (given the phrasing he is using) then that control VM that isn't required and we always say should be avoided, now requires the CALs be upgraded.
This is a perfect example of this...
This is where "but we have to license DC anyway" lazy installation tactics bite you. The problems that that causes sprawl in places we tend to forget because a clean "license-free" Hyper-V install doesn't have these problems.
-
@hobbit666 said in Random Thread - Anything Goes:
@scottalanmiller said in Random Thread - Anything Goes:
CALs are CALs, how they are purchased does not matter.
I thought if you didn't have Software Assurance you could "Move" the license to new hosts? Or is that just a Server License thing (or RDS)?
Sure, but CALs are never assigned to a host. So they can't be "moved" or assigned to one regardless. CALs are assigned to people.
So correct, Server Licenses move server to server, and/or are assigned to a server.
-
@hobbit666 said in Random Thread - Anything Goes:
@scottalanmiller said in Random Thread - Anything Goes:
How can Server B be "2019" if there is no 2019 VM? Doesn't make sense. Servers don't have levels, only VMs have levels. Once you install 2019 anywhere, then you need CALs everywhere.
Simple Server B will have a 2019 Datacentre OEM license stuck on it
So ONLY the sticker, and no installation of 2019 whatsoever? Then you are okay, you are allowed to use downgrade rights.
-
@scottalanmiller said in Random Thread - Anything Goes:
So ONLY the sticker, and no installation of 2019 whatsoever? Then you are okay, you are allowed to use downgrade rights.
Should of mentioned that
Yeah the 2019 is there only "ready" for when 2019 needs to be installed everything else will be from downgrade rights.Thanks all for clearing the CAL thing up. Hopefully we will just "move" the VM's and be done on the DC and Citrix stuff, until we upgrade some of the older machines to 2019 later.
-
@hobbit666 said in Random Thread - Anything Goes:
Yeah the 2019 is there only "ready" for when 2019 needs to be installed everything else will be from downgrade rights.
So no Hyper-V 2019? Then you are all set until you install.
-
@scottalanmiller said in Random Thread - Anything Goes:
@JaredBusch said in Random Thread - Anything Goes:
@DustinB3403 said in Random Thread - Anything Goes:
Because you are migrating to 2019 on Server B, as the host, but your VM's are unchanged, and your users are hitting 2012, and not 2019 you shouldn't need to purchase 2019 CALs.
Correct, you can have domain members of any level.
He does unless he's doing something really weird. But since the assumption is that he's installing a license-required 2019 control VM for Hyper-V (given the phrasing he is using) then that control VM that isn't required and we always say should be avoided, now requires the CALs be upgraded.
This is a perfect example of this...
This is where "but we have to license DC anyway" lazy installation tactics bite you. The problems that that causes sprawl in places we tend to forget because a clean "license-free" Hyper-V install doesn't have these problems.
Are you sure? Why would having the control VM being 2019 matter? The users aren't touching that - they are touching their 2012R2 VMs.
I mean - it's MS so anything is possible, but as long as the VMs the users are using are only 2012R2, the fact that the control VM is 2019 shouldn't matter. (with the possible exception of the admin connecting to the 2019 control VM from his PC).
-
@hobbit666 said in Random Thread - Anything Goes:
@scottalanmiller said in Random Thread - Anything Goes:
So ONLY the sticker, and no installation of 2019 whatsoever? Then you are okay, you are allowed to use downgrade rights.
Should of mentioned that
Yeah the 2019 is there only "ready" for when 2019 needs to be installed everything else will be from downgrade rights.Thanks all for clearing the CAL thing up. Hopefully we will just "move" the VM's and be done on the DC and Citrix stuff, until we upgrade some of the older machines to 2019 later.
Really - you should install Hyper-V 2019 now... there is no reason to install a 2012R2 control VM or even pure Hyper-V 2012R2... just go straight to the license untangled Hyper-V 2019 and be done with it. then migrate your VMs to the new host.
-
-
-
@DustinB3403 said in Random Thread - Anything Goes:
@wirestyle22 said in Random Thread - Anything Goes:
Um don't delete them.
Ding ding ding... don't use the fucking deleted items box as a storage bin... make a new fucking folder called shit I don't care about but still kinda do.
-
@wirestyle22 said in Random Thread - Anything Goes:
Thanks for sharing. I needed a good laugh this morning.
-
Youtube - The Jerk
It's pronounced "azaleas" -
Hopefully this doesn't hit too close to home and get me in trouble. I noticed something with one of the ad ads (the advertising of advertising here on ML).
Ok, so on the snake there's a head, there's a tail, and there's a body...
So what is that part coming down in front of him!?
