Exchange will not work in that scenario. Period. Nor will SCCM.
From: [email protected] [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Monday, June 9, 2014 5:33 PM To: [email protected] Subject: [Exchange] RE: Rejoin Exchange to New Domain? For clarity, the Exchange server is dedicated to Exchange and the SCCM server is dedicated to SCCM. Didn't mean for that to look like they were living on the same box. Thanks, Geoff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Monday, June 09, 2014 2:29 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] Rejoin Exchange to New Domain? I was instructed to build out an Exchange server on a domain provided to me. Performed the initial install (along with SCCM), but then it was discovered the internal domain and the registered web domain are different. Because of SSL certificate implications and some other non-Exchange domain impacts, they are going to build a new DC with the proper registered domain. I was told to just join the Exchange server to the new domain. Is that advisable...or even possible? I was clear I thought the best course would be to rebuild the servers (AD/Exchange/SCCM) to ensure no weirdness, but they pushed back suggesting a simple disjoin/rejoin step. With all the AD hooks (groups/containers) that are created by Exchange...will that happen during a simple joining of the domain? I was pretty confident until the other parties stated this is how we should do it. Sanity check, please?
