User Profile
imschmidt
Brass Contributor
Joined Sep 01, 2021
User Widgets
Recent Discussions
Re: Hyper-V Server 2022
Almost found a role for it, but costs/performance ended up on a standard converged solution. It’s an awesome solution on paper and the future concepts but I haven’t found the golden egg yet. Keeping in mind that when spec’ing for HCI you need to over-spec. the servers to account for the CPU and RAM the SAN would provide for the cluster. Storage optimization does not always correlate with something like SQL server compute optimization. So you have to balance, which can mean either, not always, or even often, compromise. TBH, after rearranging the hardware/software lifecycle, (which I’ve spent the last several years doing), the lack of Hyper-V server vs core+role has diminished to nothing. So over it by now… This (years old) product change from MS should no longer be a factor in any solution design by this point.565Views0likes0CommentsRe: Hyper-V Server 2022
OMG, Why is this conversation even still something that ding's in my email... Let's lay it out real quick (ok, turned out long) for people not caught up on the last 3+ years or so of conversation. (Yes I had issues with hardware vs software lifecycles I had to deal with... (in 2021!?); done... Years ago)..? 1) If you do not have a single Windows Server VM in your environment, Don't run Hyper-V. That's it... just don't do it? Why would you? Move along...best wishes? 2) If you have Windows VM's in your environment that are not S2022, run HV2019, done... You've already done the hard part and licensed the S2003-S2019 VM's 'Somehow'(right?)... 3) If you have S2022 VM's in your environment; run S2022 core w/HV role installed. DO NOT count this HV as a Server in your licensing for Windows Server VM's. The HV with no other roles installed Does Not count towards your S2022 workloads. It Doesn't Exist from a licensing perspective if it's Only a HV role is installed. (which is exactly the same as HV2008,HV2012, R2, HV2016, & HV2019) Nothing Has Changed.? (why are we still talking about this?!?!?) 4) License your Windows Server is based on the number of physical cores that can be assigned to Any VM on a HV (16c minimum). You get two VM's per Server Standard Lic. (don't count the HV server doing HV ONLY), by the time you cross ~7 vm's, you're better to go with Datacenter and get unlimited VM's on the physical box. (Clarity, a physical server with 16 or less physical cores, can run S2022 with nothing but the HV role, that serves no purpose than running up to two Windows Server 2022 VM's, with unlimited Linux VM's. All with a default Server Standard 2022 license for the physical box) 5) In any scenario beyond #1, where you do not have any single Windows Server VM above S2019, go ahead and run 39,6732 VM's of any other operating system (arbitrary number). You ONLY LICENSE YOUR WINDOWS VM's. ========== If you are "Testing", "Lab", "Pre-production", "doing something anywhere that is not in production, making money, learning, or anything other than using Windows Server to run a functioning organization. Download and install an evaluation and run that... Bonus, every three year you are forced to learn about how to do a new migration to the next version of Windows Server Eval, which you need to practice anyways if you're an IT professional.... =========== ***You Do Not Pay for the physical box running your VM's. The Hypervisor role is, and Always Has Been "Included" (not free because you pay for the VM's). You pay for the Production VM's running workloads that your business (or client businesses) need. This is not a "cash grab", this is not the end of the world, this is day to day changes in IT infrastructure. License your sh*t, NOTHING has actually changed if you're running Windows VM's in your environment beyond how you install the hypervisor. OMFG F*k798Views1like0CommentsRe: Hyper-V Server 2022
bmartindcs I think this is the wrong approach. Do I disagree with the decision to discontinue HV server, Absolutely! For several reasons I've posted in this thread over the past several months. The costs at the end of the day are paid by the client, and it is what it costs. Those costs aren't any different even, just now bundled between software and hardware. As long as you are running one single Windows Server VM, than I don't see any reason whatsoever to not do Server Core w/HV role.4.6KViews0likes0CommentsRe: Hyper-V Server 2022
SGGGG I think the whole Lab/Home Use thing is a bit of a red herring. We have always had the ability to install the current version of a Windows Server Core (for any service) in an evaluation/lab/non-production environment. There is nothing about this move that prevents you from running Server 2022 Core w/HV Role, in a lab or at home to test out or experiment with features and management. I don't see that ever changing, in fact Server Eval. has gotten more open and better over the years. The problem I have is the impact on licensing a hypervisor, either by updating the VM licensing before it would be necessary, or via an Azure subscription on more expensive hardware. This is the largest impact to SMB.14KViews0likes74CommentsRe: Hyper-V Server 2022
I've actually recently learned HCI will install on uncertified hardware just fine, as well as inside another hypervisor using nested virtualization. For a lab, you can get started without certified hardware. As for the comment: That's windows server with Hyper-V feature added. It literally costs nothing if you are already buying MS Server licenses. This is true, to some extent. I cannot install Server 2022 as a hypervisor, to run Server 2016 VM's, if I own S2016 licensing. Where I could install HV2019 and run licensed S2016 VM's. With HCI and HV servers, the hypervisor licensing is not tied to the VM licensing.5.1KViews1like0CommentsRe: Hyper-V Server 2022
Elden_Christensen Awesome to hear you're addressing the single node issue, that will help a lot in the SMB space. If you can do certified hardware next, then we'll almost be to HV Server 2022... As for the idea of a crippled HV, that's a non-starter. If you're looking for some limitation, I'd say look at a mode for free, that's not registered with Azure. We need the business features, cause we're in business. We all understand the monthly subscription requirement for an Azure service, and there's lots of benefits to using those features, when they make sense. Most of our clientele does not need Azure, they need a server in their office running Sage or something. What people on This thread want, is a hypervisor, not tied to the VM licensing, without strings attached and a monthly bill. Keep in mind, no one is asking for hand outs. Every one of us (or nearly), is purchasing Windows Server and Application licensing, and CALs for the VM's. We're your customers, and our customers are your customers. We're spending $10's of thousands a month at Microsoft, and we're just one small Partner. Give us a mode, where HCI runs more or less the same as a HV Server 2019, on the same type of hardware scenario, for the same price and this thread/issue goes away tomorrow. It sounds like you're half way there.5.3KViews1like85CommentsRe: Hyper-V Server 2022
Elden_Christensen Hi Elden, As I've previously noted, the biggest problem with this model is you're tying the Hypervisor licensing to the VM licensing. You can't do a hardware migration to a newer hypervisor unless the you have licensing for All the VM's updated at the same time. ie: We regularly have HV servers running 2012-2019 VM's. We can deploy HV2019 to them, without purchasing new licensing for the 2012's at the same time. In our new hardware deployments we're going to have to purchase licensing for VM migrations planed 18-24 months out. We can't use S2022 core, to host 2012 VM's without buying S2022 licensing for them on day one.9.8KViews0likes0CommentsRe: Hyper-V Server 2022
Elden_Christensen Azure Stack HCI is absolutely not a replacement for Hyper-V Server. For an MSP, what you have done here, is break the disconnect the hardware cycle from the licensing cycle. Many (if not every) one of the servers we got upgraded in the 2008 EOL was done in multiple stages, by upgrading the hardware, migrating the VM's and performing the OS migrations at a later date. We did dozens of clients over 18 months like this. This was only possible due to the HV license being independent of the guest license. These are SMB clients, their not putting out for HCI hardware. End Of Story. The Server 2012 EOL is putting us in the same position, but this time if we're going to stick to Microsoft Hypervisors, we have to sell them on the 2022 licensing and CAL's along with the hardware. You're doubling to tripling the up front investment we have to sell to these SMB's. If MS does not have a hyper-v server available for the next migration, it will not be a Microsoft Hypervisor that goes on the hardware. Highly disappointing, and frankly shortsighted decision on Microsofts part. (edit: spelling)27KViews8likes0Comments
Recent Blog Articles
No content to show