Windows Server 2016 Pricing
-
@crustachio said in Windows Server 2016 Pricing:
If we're comfortable riding 2012 into the sunset....
I have a rule of thumb about this... anything that something like this is said, it probably means you should not be on Windows
-
Is Microsoft going to be selling 2 pack core license at the Standard Server License level as well?
-
@scottalanmiller said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
I agree in hypothetical terms, but as the environment is already bought and paid for, save Windows licensing, what's the "lot of down the road cost" we risk suffering?
This is where expensive software sucks people in.... they have two really good emotional ways to get people to keep spending money. First is the sunk cost fallacy, which you mentioned above, that feeling that since you paid for it, you should use it. The second is the belief that it is already paid for and incurs no more cost.
The second is untrue for many reasons. For example, with VMware you have to license it year after year, you pay continuously. And when you want to update, you pay even more. You pay for tools and invest in designs and other decisions around the fact that you have it - indirect investments in whatever design you have. In your case this includes VSAN and Windows licensing investments, at the very least, and probably a few others that haven't been mentioned.
And last, you invest in knowledge. You put your time and effort into learning what you are running currently. Right now, Hyper-V has little downside compared to ESXi. But in three years when your whole team has built all documentation, policies and procedures around ESXi that will be a very different picture.
Running systems always incurs debt. Putting your debt into your future rather than into your past is an important thing to always consider in IT.
Thank you, there's a lot of good stuff to chew on in that post.
If I am completely honest and stop making excuses to rationalize our predicament, then yes, you're completely right. It is not too late to stop and rethink this. It would be a MAJOR uphill climb for me vs my manager though, as he is pushing for the VSAN deployment to be operational "yesterday", and I'm 99% there except for licensing.
I would also need to go back to square one in terms of research and education. I am comfortable administering a Vmware environment, I know VSAN pretty well and I've engineered the hardware and network (new 10GbE TOR switches) around VSAN. I have almost no comparable experience in terms of Hyper-V. Could I? Sure. But it's a factor. Like you said, investment in knowledge is a factor. And Vmware is something we already have a comfortable investment in knowledge and experience with.
Side point: Switching horses in midstream to Hyper-V would require using Starwind for the local shared storage component, as I don't think 2016's Storage Spaces Direct is the way we'd want to go. I have no idea what Starwind licensing is like, but wouldn't that be a similar argument about future costs as sticking with Vmware? Either way we will have to continue paying licensing.
-
@scottalanmiller said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
If we're comfortable riding 2012 into the sunset....
I have a rule of thumb about this... anything that something like this is said, it probably means you should not be on Windows
See above... We have an unsettling amount of 2003 servers in production.
-
@crustachio said in Windows Server 2016 Pricing:
@scottalanmiller said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
If we're comfortable riding 2012 into the sunset....
I have a rule of thumb about this... anything that something like this is said, it probably means you should not be on Windows
See above... We have an unsettling amount of 2003 servers in production.
Perfect time to move away from Windows then. You've made it clear you can't afford it so investing the time and money into moving away from it would pay off in the long run.
The other thing is, your boss doesn't think the organization can afford Server 2016, does the organization (management) feel the same way?
-
@crustachio said in Windows Server 2016 Pricing:
@scottalanmiller said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
If we're comfortable riding 2012 into the sunset....
I have a rule of thumb about this... anything that something like this is said, it probably means you should not be on Windows
See above... We have an unsettling amount of 2003 servers in production.
The question is why do you have those 2003 servers? Lack of funds to upgrade, lack of motivation to upgrade? lack of support from vendors to upgrade?
-
@coliver said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
@scottalanmiller said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
If we're comfortable riding 2012 into the sunset....
I have a rule of thumb about this... anything that something like this is said, it probably means you should not be on Windows
See above... We have an unsettling amount of 2003 servers in production.
Perfect time to move away from Windows then. You've made it clear you can't afford it so investing the time and money into moving away from it would pay off in the long run.
The other thing is, your boss doesn't thing the organization can afford Server 2016, does the organization (management) feel the same way?
Organization has no opinion; he is director of IT and has sole discretion over IT infrastructure budget/purchases.
Moving away from Windows... We have numerous 3rd party vendor applications that are Windows based. Not to mention Exchange, AD, terminal services, etc. If switching to Hyper-V is an uphill climb, what do you think my odds are of pitching a MS exodus?
ETA: I don't think I said that "we can't afford Windows". My reason for bringing up the 2016 licensing bump was to point out that it is a big cost increase for some organizations, not to say that we outright can't afford it. The question is, is it worth it to us? Running a Windows environment has huge value to us. Running 2016 Server in particular, I don't see the value yet. IF we made the decision to switch to Hyper-V, then 2016 would be a no-brainer.
-
@Dashrender said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
@scottalanmiller said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
If we're comfortable riding 2012 into the sunset....
I have a rule of thumb about this... anything that something like this is said, it probably means you should not be on Windows
See above... We have an unsettling amount of 2003 servers in production.
The question is why do you have those 2003 servers? Lack of funds to upgrade, lack of motivation to upgrade? lack of support from vendors to upgrade?
That's a question but it's not the question. Pick a reason.
-
@crustachio said in Windows Server 2016 Pricing:
And Vmware is something we already have a comfortable investment in knowledge and experience with.
So sunk cost and technical debt are and have been driving decision making already. Which they should be partially, they cannot be ignored, but it is important to recognize that they are debt drivers rather than investment drivers.
-
@crustachio said in Windows Server 2016 Pricing:
Side point: Switching horses in midstream to Hyper-V would require using Starwind for the local shared storage component, as I don't think 2016's Storage Spaces Direct is the way we'd want to go. I have no idea what Starwind licensing is like, but wouldn't that be a similar argument about future costs as sticking with Vmware? Either way we will have to continue paying licensing.
You are correct on all points. Starwinds would introduce cost (maybe, not necessarily, you have a ton of VSAN induced cost there), and SSD is not remotely ready for prime time yet. But even in the worst case, Starwind is fractional compared to VSAN and Hyper-V is totally free compared to... well, anything.
But it sounds like a lot of your costs in hardware terms as well come from VSAN. I would guess that if you left the VMware world, you could reduce to two hosts and go to 100% free Hyper-V and Starwind.
-
Dammit, wrong browser window.
-
@crustachio said in Windows Server 2016 Pricing:
Moving away from Windows... We have numerous 3rd party vendor applications that are Windows based. Not to mention Exchange, AD, terminal services, etc. If switching to Hyper-V is an uphill climb, what do you think my odds are of pitching a MS exodus?
Depends on your pitching skills. If I talked to the people in charge, my reasons for moving off of Windows would probably not only make them move off immediately, but might get someone fired for having used it already
Basically.... wasting money while not being supported. Basically Windows isn't an option as described. It's incredibly obvious that Windows isn't a valid solution in this case and any apps chosen with that dependency are simply not valid options either by logical extension - they depend on things that can't be afforded or supported in the current environment.
Money is being thrown around on things like VMware and VSAN, but there isn't enough to run viable software on top of them. Massive mismatch of expenditures. Something doesn't add up.
I'm pretty confident that if I made a pitch, they'd drop Windows without question. And investigate how they got into the current situation. As a government entity, a good pitch in this case should secure the case because it would mean not following it would call corruption into question.
-
@crustachio said in Windows Server 2016 Pricing:
Running a Windows environment has huge value to us.
What value is that? That you can't get to supported, secure versions generally is an indicator that Windows is a huge negative value, rather than a positive one. Not 100% of the time, but 99%+
-
@mlnews said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
Side point: Switching horses in midstream to Hyper-V would require using Starwind for the local shared storage component, as I don't think 2016's Storage Spaces Direct is the way we'd want to go. I have no idea what Starwind licensing is like, but wouldn't that be a similar argument about future costs as sticking with Vmware? Either way we will have to continue paying licensing.
You are correct on all points. Starwinds would introduce cost (maybe, not necessarily, you have a ton of VSAN induced cost there), and SSD is not remotely ready for prime time yet. But even in the worst case, Starwind is fractional compared to VSAN and Hyper-V is totally free compared to... well, anything.
But it sounds like a lot of your costs in hardware terms as well come from VSAN. I would guess that if you left the VMware world, you could reduce to two hosts and go to 100% free Hyper-V and Starwind.
That's what I was thinking as well. VMWare requires at least 3 host for VSAN but recommends 4. 48 VMs aren't really that many and unless you have IOPS number ready you won't really know one way or the other if two hosts can handle what you are speccing 4 hosts for.
-
@crustachio said in Windows Server 2016 Pricing:
Organization has no opinion; he is director of IT and has sole discretion over IT infrastructure budget/purchases.
Who does he report to in the command chain?
-
Again, I didn't say we "can't afford 2016". I'm just having a hard time justifying the price increase as applies to our current environment.
-
@scottalanmiller said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
Organization has no opinion; he is director of IT and has sole discretion over IT infrastructure budget/purchases.
Who does he report to in the command chain?
City Manager.
-
@coliver said in Windows Server 2016 Pricing:
@mlnews said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
Side point: Switching horses in midstream to Hyper-V would require using Starwind for the local shared storage component, as I don't think 2016's Storage Spaces Direct is the way we'd want to go. I have no idea what Starwind licensing is like, but wouldn't that be a similar argument about future costs as sticking with Vmware? Either way we will have to continue paying licensing.
You are correct on all points. Starwinds would introduce cost (maybe, not necessarily, you have a ton of VSAN induced cost there), and SSD is not remotely ready for prime time yet. But even in the worst case, Starwind is fractional compared to VSAN and Hyper-V is totally free compared to... well, anything.
But it sounds like a lot of your costs in hardware terms as well come from VSAN. I would guess that if you left the VMware world, you could reduce to two hosts and go to 100% free Hyper-V and Starwind.
That's what I was thinking as well. VMWare requires at least 3 host for VSAN but recommends 4. 48 VMs aren't really that many and unless you have IOPS number ready you won't really know one way or the other if two hosts can handle what you are speccing 4 hosts for.
Yeah, 48 VMs is a two server scenario at least 80% of the time. And at least 5% of the time is just a single server scenario. Three or more isn't unheard of, but quite unlikely.
-
@crustachio said in Windows Server 2016 Pricing:
Again, I didn't say we "can't afford 2016". I'm just having a hard time justifying the price increase as applies to our current environment.
Understood. In the "do we update now" world, it makes sense to possibly hold off. But, I would say, that that should make every single person immediately say "and now we are moving off of Windows because we no longer see it as financially viable." Not that you can't afford it, that it isn't a good ROI for you.
Once you can't justify the spend to run Windows "well", it means that WIndows is the wrong toolset. That's the general rule. Not afford, justify.
-
@scottalanmiller said in Windows Server 2016 Pricing:
@crustachio said in Windows Server 2016 Pricing:
Running a Windows environment has huge value to us.
What value is that? That you can't get to supported, secure versions generally is an indicator that Windows is a huge negative value, rather than a positive one. Not 100% of the time, but 99%+
Well that really depends on the answer to my earlier question:
@Dashrender said in Windows Server 2016 Pricing:
The question is why do you have those 2003 servers? Lack of funds to upgrade, lack of motivation to upgrade? lack of support from vendors to upgrade?
If it wasn't lack of funds, but other reasons for not moving, i.e. lack of motivation, then being on another platform won't solve that problem. really the same could be said for vendor software that can't update to a new version of the OS.
