Back in Exchange 2010, the Set-MailboxServer cmdlet had a parameter named SubmissionServerOverrideList, which would instruct the respective mailbox server which Hub Transport server to notify when new messages were to be picked up from the users' mailboxes.

Looking at the corresponding Exchange 2013 version of the same cmdlet, we now find out that the SubmissionServerOverrideList is reserved for internal Microsoft use. Has something changed or become deprecated in the meantime ?

Since there is no hub transport role and the transport service runs on a mailbox server , the SubmissionServerOverrideList doesn't make sense in Exchange 2013.

Maybe similar functionality would be achieved by indicating the preferred "Transport service" entities to the "Mailbox Transport Submission service" ones, based on the mail flow diagram here.

Just curious if it's actually just an error in the documentation, or it's being planned to have this reflect some functionality in the future.

Pls review.

https://msdn.microsoft.com/en-us/library/microsoft.exchange.data.directory.management.mailboxserver.submissionserveroverridelist(v=exchg.150).aspx

Thx

IJSingh - "Hub Transport" in the msdn article. Hence it talks about Exchange Server 2010 - but the mechanism behind is already known. My question is whether that parameter is still doing something in 2013 or the documentation left it by mistake. Guess only someone in MS can provide an aswer.