Run EMS when Exchange server is offline

I have an Exchange 2013 server that is disconnected from the network, and I cannot reconnect it because of the problems it will cause our users (we've migrated to Office 365). But I need to pull a mailbox out of the old database on it, so I need to find a way to get Exchange Management Shell to work without being able to contact a domain controller.

Has anyone ever found a way to make this work? I've found ways to get around the certificate check and the CN check, and the Kerberos authentication, but it consistently crashes trying to contact a domain controller.

Any suggestions would be appreciated.
PBITAsked:
Who is Participating?
 
PBITAuthor Commented:
We ended up restoring the original mailbox from the deleted mailboxes list in Office 365, information I didn't have when I started this process. So I no longer need to try to force that old server to cooperate. Thanks for all the suggestions!
0
 
Adam BrownSr Solutions ArchitectCommented:
The only way to get that to work is to build a secondary domain with Exchange on it, then restore the Database files from the failed exchange server. Exchange won't work if it can't contact a DC. The necessary services won't start and the DB won't mount.

That said, what issues does turning this Exchange server on cause your users?
0
 
PBITAuthor Commented:
That's what I was afraid of.

It causes security certificate popups; not a game-changer, but annoying. I'm trying to limit the help-desk calls, mostly.

Thanks for that, looks like something I'll just need to tackle on the weekend.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Adam BrownSr Solutions ArchitectCommented:
The security certificate popups are likely due to the Autodiscover SCP pointing Outlook to the Exchange server for autodiscover, rather than Office 365. That's actually pretty easy to resolve. I wrote an article on how to change it with AD Sites and Services (So the server doesn't have to be up to fix the problem) here: http://wp.me/pUCB5-7X 
Just make sure that any servers remaining in your AD Services node for Exchange point to autodiscover.outlook.com (or autodiscover.company.com, if you have a CNAME set up to redirect to O365 for that) instead of the on-prem exchange server name. That should keep the certificate error from popping up when you turn the exchange server on.
1
 
PBITAuthor Commented:
I'll give that a try, thanks!
0
 
PBITAuthor Commented:
The solution came from someone in my organization and we didn't even try to implement any of the suggested solutions, so I don't know if they would have worked or not.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.