It seems as though you can install another DC, then replicate, then demote the EVAL one.
But I think I'll just go with not doing that.
It seems as though you can install another DC, then replicate, then demote the EVAL one.
But I think I'll just go with not doing that.
@Dashrender said:
But then the question is, where do you get the downgraded key from? If you don't have any 2012 R2 servers now, you don't have any keys. So either you'd have to buy yourself into a Volume License agreement so you have the current and all the old keys, or you'd have to buy a stand alone 2012R2 server so you have a key.
Perhaps this is something I am also wrong on, but I thought all versions of MS Server OSes came with downgrade rights. AKA I could license 2016 (when it comes out), but install 2012.
@Jason said:
Not if it's already a DC. You switch the licensing and you kill the DC and how AD works. You can do that on Member servers but not DCs.
In addition to this thread saving me a lot of money, that bit of advice just saved me a bunch of time.
Why in heck would they not allow that?
@Jason said:
You can't switch from a Eval to a full version on a DC, member servers it's fine it's just a DISM activation command. But once promoted to a DC you can't have the machine ID changing. You'd have to bring up a new DC if it had already been made a DC before activated.
But if I wanted to go with 2012R2, couldn't I just put a valid (aka purchased) retail product code into the activation section?
I was thinking of a scenario where I would license 2016 but use the downgrade rights to get a valid 2012R2 key.
Just to let everyone know, I have not died.
I spent the weekend not thinking about servers, or server OSes, or SSDs. I thought about beer, and how terrible most of my fantasy football teams are. And how hard it is to put in a good Fanduel lineup with a terrible hangover.
So here is the update from Friday.
Kingston has agreed that these drives are not going to work in this application, unless I want flashing amber lights and no information. Not really how I want to proceed. I am going to send them back.
I was able to cancel all the paperwork on the Server 2012 R2 purchase. I am still a bit on the fence about that, but at least now I am not pressured to make a decision. I'm still leaning towards going with Server 2012, but am giving it a few days to let the mangolassi sink in.
I spoke with xByte about their EDGE SSD drives. EDGE has special firmware that allows them to work in the DELL servers. According to xByte, there will still be an exclamation mark in OMSA, but the LEDs on the drives will work, and the drives should be SMART accessible.
@scottalanmiller said:
Because I doubt that it will work.
I was thinking about that, still in the mindset of using Server 2012.
You are right upgrading to 2016 from eval probably would be sketchy at best.
@scottalanmiller said:
I would put that at "pretty risky".
Because it might not work, or because Server 2016 won't be out until after July 2016?
@scottalanmiller said:
You don't want to do an in-place migration anyway. Especially not over that number of versions.
Yeah I was thinking more the AD migration.
Definitely going to start anew.
@scottalanmiller said:
That's definitely what I would do. Practice, migrate, prioritize. You can have everything tested and ready with release candidates before it is time to go live. You can be SO ready
Would you go right to 2016 the day it launches? Or just use the downgrade rights and install 2012? I generally stay away from new releases!
Do we even know if there is a supported 2003 to 2016 migration? Maybe you have to go to 2012 first anyway?
Also: does anyone know if you can upgrade from an evaluation copy? I just installed one on my server, and it gives you 6 months without a key. If I delayed until the end of 2015, I could roll the dice and hope 2016 releases before 6 months.
@mlnews said:
To a partner, not a reseller. Go to a reseller and you get less, not more. Go to a partner and you get more. Resellers like GoDaddy can shave the price but you lose control that you otherwise have.
Got it.
@Dashrender said:
While I think you can add a reseller to your account, they won't have the same type of access I don't believe as they would if they sold you the account originally.
Oh I was figuring I'd just switch over to a reseller.
@scottalanmiller said:
And, BTW, we just topped TWO HUNDRED posts in under a day for this thread
Is that a record?
This should probably go into another thread, but ... what hosted Exchange platform do you all like?
I've been using Office 365 for my own e-mail.
I have to co-setup, and all my e-mail forwards to my onmicrosoft account. Works great. And it's cheap. Even if you do the $8 month option.
But heaven forbid if you nead tech support.
@scottalanmiller said:
Or he could use the spare time to move to hosted email and eliminate that from the migration process when 2016 releases
I was actually thinking that.
I did throw all these ideas onto another forum, I will say. I'm glad I was directed here, though.
And trust me, I have been practicing with Hyper-V. I've set up quite a few test servers on 2012 R2, Hyper-V. The whole nine yards. Now I ready to rumble!
Though highly considering what you are saying!
Then I would have a new server sitting around for a few months, and probably a lot of questions.
OK, next comment from yesterday that got me thinking...
Someone mentioned about waiting for Server 2016.
Is THAT a good idea? Considering we aren't sure when it's coming out, and since I am moving from 2003 (not 2008), and I need an OS now...
I looked into Software Assurance but it adds about 50% to the cost, so not sure it is worth it.
Thoughts?
@Dashrender said:
if you split the load over two server, you're still loosing 50% of your stuff, and how usable is your business with one but not the other?
Yeah I guess I was thinking it would be easier to spin in up off a backup, but it wouldn't be that much worse to do it twice. Plus I am considering outsourcing the e-mail in the near future anyway.
It was technically day yesterday when we decided.
Not just the $800 ... also the cost of another server.