Storage Question
-
@BRRABill said:
Do we even know if there is a supported 2003 to 2016 migration? Maybe you have to go to 2012 first anyway?
We looked at all the options for upgrading 03 to 12 - tl;dr nuke & pave.
-
@MattSpeller said:
@BRRABill said:
Do we even know if there is a supported 2003 to 2016 migration? Maybe you have to go to 2012 first anyway?
We looked at all the options for upgrading 03 to 12 - tl;dr nuke & pave.
By that I assume you mean you stood up a brand new install of 2012 R2, inserted the server disk for 2012 into the 2003 server, updated the schemes, etc..
Then back on the 2012R2 box you DC Promo'ed it. Then transfered the roles from 2003 to 2012 R2, then demoted the 2003 server, then killed it, right?
-
@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:
I would put that at "pretty risky".
Because it might not work, or because Server 2016 won't be out until after July 2016?
-
@Dashrender lol yes, though you un-tl;dr'd my post
-
@BRRABill said:
@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?
Because I doubt that it will work.
-
@MattSpeller said:
@Dashrender lol yes, though you un-tl;dr'd my post
I had no idea what tl:dr meant until 5 seconds ago...
-
@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.
-
Worth doing to learn it before going to production with it. But plan to blow it away and do a fresh migration when the time comes.
-
@BRRABill said:
@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.
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.
-
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.
-
-
@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.
-
@BRRABill said:
But if I wanted to go with 2012R2, couldn't I just put a valid (aka purchased) retail product code into the activation section?
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.
-
Terminology is an issue here.
2016 is currently in beta, not evaluation mode.
If you get a 2012R2 Eval from MS, While I've never done it, I'd be damned surprised if you couldn't add a valid license key to activate it and leave it running.
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.
-
Getting into an Open License is probably the way you want to go anyhow - you'll need the server license and CALs too.
-
@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?
-
@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:
@BRRABill said:
But if I wanted to go with 2012R2, couldn't I just put a valid (aka purchased) retail product code into the activation section?
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.
huh - If I have time this week I think I'll stand up a new 2012 R2 server, make a new domain using only the eval codes to confirm this - no promises on time though.
-
@BRRABill said:
Why in heck would they not allow that?
AD security is based heavily on the IDs of the computers, changing that breaks it.
-
@Dashrender said:
@Jason said:
huh - If I have time this week I think I'll stand up a new 2012 R2 server, make a new domain using only the eval codes to confirm this - no promises on time though.There's no mechanism to stop DISM from working (as far as I know) on DC; it just will break things.
https://technet.microsoft.com/en-us/library/jj574204.aspx?f=255&MSPPError=-2147217396
