Windows Server 2016
-
I think the definition of active becomes an issue. Active means "running" not "accepting email" as far as I know. But there is normally a grace period for transferring over.
-
@scottalanmiller said in Windows Server 2016:
I think the definition of active becomes an issue. Active means "running" not "accepting email" as far as I know. But there is normally a grace period for transferring over.
it's worse than that - Even if it was active means accepting email, rarely is an environment so small that the migration would be done while no email was moving between both servers. So in that case, both servers would be online and working at the same time while you're migrating.
-
@Dashrender said in Windows Server 2016:
@scottalanmiller said in Windows Server 2016:
I think the definition of active becomes an issue. Active means "running" not "accepting email" as far as I know. But there is normally a grace period for transferring over.
it's worse than that - Even if it was active means accepting email, rarely is an environment so small that the migration would be done while no email was moving between both servers. So in that case, both servers would be online and working at the same time while you're migrating.
Depends, if you cut over with DNS you have that issue. But if you do with the firewall, you do not.
-
I mean internally. I suppose if you do a weekend cutover and move all mailboxes off one server and onto another, then you have only one in use at a time... But that seems to be the exception instead of the rule. Most people would migrate many boxes in a day, then more the next, and so on... in these cases, both servers are fully in use, at least by the end users.
-
Thankfully I do not have Exchange in house, and I would only be doing this process with DCs.