Windows Server 2016
-
Are any of you looking to deploy this when it releases? I've only looked at it a very small amount. I'm debating whether or not to pay for SA for my new pair of 2012 R2 licenses.
-
Paying for SA is the only option that ever makes sense (when running windows).
Would you rather buy Server 2016 at retail should you need it a year after release? How many systems are you running now with Server 2012?
I'm not considering it (as I'm not paid to) but I would only say, yes get SA so we can since we're a windows shop.
-
Considering how old 2012 R2 is, and that 2016 is right around the corner.. yes I'd buy 2016, may not renew it (probably would) but definitely would buy it now.
-
@DustinB3403 said in Windows Server 2016:
Paying for SA is the only option that ever makes sense (when running windows).
Would you rather buy Server 2016 at retail should you need it a year after release? How many systems are you running now with Server 2012?
I'm not considering it (as I'm not paid to) but I would only say, yes get SA so we can since we're a windows shop.
Well, with user CALs the difference between SA vs non SA is about $1800 (US). That works out to being about half of what I'd pay for 2016 without SA. If I don't use 2016 right on release, then the value goes down as I would be approaching a hardware refresh at some point in the future.
-
This is a situation where Scott would say you have to pay the Windows tax. You're choosing to use Windows, and you should always want to stay up to date, so yeah, you need it.
-
A further consideration is that two of my four licenses will be DCs. Upgrading them from 2012 R2 to 2016 is an unknown at this point.
-
@Kelly But that hardware refresh doesn't mean you need to re-purchase server licensing..
So the value still stays the same.
There is no lost value with SA, unless you never use it.
-
@DustinB3403 said in Windows Server 2016:
There is no lost value with SA, unless you never use it.
Therein lies the purpose of my initial question regarding other people's usage of 2016.
-
@Kelly said in Windows Server 2016:
A further consideration is that two of my four licenses will be DCs. Upgrading them from 2012 R2 to 2016 is an unknown at this point.
What makes them unknown?
-
@Dashrender said in Windows Server 2016:
@Kelly said in Windows Server 2016:
A further consideration is that two of my four licenses will be DCs. Upgrading them from 2012 R2 to 2016 is an unknown at this point.
What makes them unknown?
I don't know anyone that has upgraded a 2012 R2 DC to 2016.
-
@Kelly said in Windows Server 2016:
@Dashrender said in Windows Server 2016:
@Kelly said in Windows Server 2016:
A further consideration is that two of my four licenses will be DCs. Upgrading them from 2012 R2 to 2016 is an unknown at this point.
What makes them unknown?
I don't know anyone that has upgraded a 2012 R2 DC to 2016.
Why would you? it's not RTM yet.
-
Do you really expect 2016 DC upgrades to be worse than previous ones?
I've never had an issue installing new DCs into a 2000 or newer domain, then decomming old ones.
-
@Dashrender said in Windows Server 2016:
@Kelly said in Windows Server 2016:
@Dashrender said in Windows Server 2016:
@Kelly said in Windows Server 2016:
A further consideration is that two of my four licenses will be DCs. Upgrading them from 2012 R2 to 2016 is an unknown at this point.
What makes them unknown?
I don't know anyone that has upgraded a 2012 R2 DC to 2016.
Why would you? it's not RTM yet.
Exactly. Hence it is an unknown. I'm not trying to be sarcastic here (mostly). I'm just not sure what you're getting at.
-
@Dashrender said in Windows Server 2016:
Do you really expect 2016 DC upgrades to be worse than previous ones?
I've never had an issue installing new DCs into a 2000 or newer domain, then decomming old ones.
I'll only have a total of four licenses (2 Standards). If I've used all of them on VMs will I be able to stand up a new DC and decom the old one?
-
@Kelly said in Windows Server 2016:
@Dashrender said in Windows Server 2016:
@Kelly said in Windows Server 2016:
@Dashrender said in Windows Server 2016:
@Kelly said in Windows Server 2016:
A further consideration is that two of my four licenses will be DCs. Upgrading them from 2012 R2 to 2016 is an unknown at this point.
What makes them unknown?
I don't know anyone that has upgraded a 2012 R2 DC to 2016.
Why would you? it's not RTM yet.
Exactly. Hence it is an unknown. I'm not trying to be sarcastic here (mostly). I'm just not sure what you're getting at.
Why would you want to stay with a 2-3 year old OS when a new one is right around the corner. heck, if you can wait, why not wait?
I don't expect 2016 to suddenly start having problems compared to 2012 or 2008, etc, so I'm not worried about that part of it.
-
Server '16? Early adopting microsoft stuff?
I wait for crazy people to do the beta testing for me then learn from their foibles.
-
@Kelly said in Windows Server 2016:
@Dashrender said in Windows Server 2016:
Do you really expect 2016 DC upgrades to be worse than previous ones?
I've never had an issue installing new DCs into a 2000 or newer domain, then decomming old ones.
I'll only have a total of four licenses (2 Standards). If I've used all of them on VMs will I be able to stand up a new DC and decom the old one?
That's a great question - (oh and you actually only have two licenses, each allow 2 VMs) - I'm not sure of the legality of standing up a fifth VM, migrating, then decom'ing the old one... but I've done it, and I've know tons of people who have... again, I can't answer the legal question.
-
@MattSpeller said in Windows Server 2016:
Server '16? Early adopting microsoft stuff?
I wait for crazy people to do the beta testing for me then learn from their foibles.
Unless there's a new kernel, if I recall correctly, @scottalanmiller would say this isn't really new.
-
@Dashrender said in Windows Server 2016:
@MattSpeller said in Windows Server 2016:
Server '16? Early adopting microsoft stuff?
I wait for crazy people to do the beta testing for me then learn from their foibles.
Unless there's a new kernel, if I recall correctly, @scottalanmiller would say this isn't really new.
That's right. I'd not call the OS new, but the updates are new.
-
@scottalanmiller said in Windows Server 2016:
@Dashrender said in Windows Server 2016:
@MattSpeller said in Windows Server 2016:
Server '16? Early adopting microsoft stuff?
I wait for crazy people to do the beta testing for me then learn from their foibles.
Unless there's a new kernel, if I recall correctly, @scottalanmiller would say this isn't really new.
That's right. I'd not call the OS new, but the updates are new.
Both valid points, and I appreciate that it might not be "new" new, but I'd still hang back a bit. I have enough to fix around here without introducing new stuff to break
