Exchange 2013 - reset all settings

We have an exchange 2007/2013 coexisting environment. I've been migrating a few test mailboxes from 2007 to 2013 and everything was working fine.
When I tried to change the internals and externals virtual directories to make the 2013 proxy to 2007 ( , I certainly messed up a few things. Or maybe when I rolled back that attempt...

Now, users whose mailbox is on 2013 works fine in OWA, but Outlook clients can't connect to Exchange server. Everytime I try to create an Outlook profile whose mailbox is on Exchange 2013 it's asking for credentials.

If I dig further and try to manually configure server settings:

 - If I specify the Exchange 2013 server and try a 'Check Name', it says: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."

 - If I specify the Exchange 2007 server and try a 'Check Name', the server changes for the fqdn of the 2013 server and it does resolve 'Check Name' process. Clicking on Next at this point completes the 'Add new e-mail account wizard". But is I try to start Outlook, I got an error saying "Microsoft Exchange is unavailable"

I'm thinking of uninstalling the Exchange 2013 server and reinstalling it, but I'm afraid of AD behavior. As I'm in prod mode, that would be the last thing to try.

I would like to know if anyone knows a way of resetting all Exchange 2013 server settings, including IIS.


Who is Participating?
Jamie McKillopIT ManagerCommented:
Run get-exchangecertificate | fl on all your CAS servers. On the 2007 servers, you should see the cert and it should have "IIS" in the Services property. On your 2013 servers, you should have a cert that has and and IIS should be in the Services property.

You should be able to resolve these domain names to the corresponding CAS or CAS array both internally and externally.

Run Get-ClientAccess server for each of your client access servers. Make sure the AutodiscoverInternalURI property points to

Run Get-OutlookAnywhere for each of your client access servers. Make sure the internal and external URL are set to on each one

Run Get-Webservicesvirtualdirectory -Identity "<CAS Server>\EWS (Default Web Site)"  and make sure ExternalUrl is on the 2013 servers and on the 2007 servers

Run Get-OABVirtualDirectory -Identity "<CAS Server>\OAB (Default Web Site)" and make sure the ExternalURl is on the 2013 servers and on the 2007 servers

Jamie McKillopIT ManagerCommented:

Have you setup a legacy FQDN for your 2007 environment and have you obtained and installed a cert for that FQDN?

deewaveAuthor Commented:
yes I have set up an internal FQDN for our legacy (2007) server in our DNS

I'm not sure about the cert. How can I verify that?  Here is the output of get-exchangecertificate on my 2013 server:
Thumbprint                                Services   Subject
----------                                --------   -------
F4548A32306A6ABEB57BC729D3414F7E780496F5  ......., OU=IT, O=Transdev, L=QC, S=Boisbr...
3CFFBFAF44CA22640E1AB3B6B18FE5EF5FD5C9B3  .......    C=CA, S=QC, L=Boisbriand, O=Transdev Canada Inc., OU=IT, CN=mai...
B62CC75DB32D3FB32401C5C5A2C4205FE1ADD338  ....S..    CN=serv-exch2013
072D556BC6A83342CFCF0C0368AC8188066D0F24  ....S..    CN=Microsoft Exchange Server Auth Certificate
C5C3B1EBD738878223524BE851A404C881FE8C27  IP.WS.., OU=Domain Control Validated, O=mail.transd...
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Jamie McKillopIT ManagerCommented:
Run get-exchangecertificate | fl

That will show you which certificate each protocol is active on.

Did you purchase a new cert for the legacy name?

deewaveAuthor Commented:
No I haven't purchased a new cert. I created one with the wizard on Exchange 2013 and did the request with our internal certificate authority server
Jamie McKillopIT ManagerCommented:
Do all your clients and the Exchange servers have that CA's root cert installed?

deewaveAuthor Commented:
I guess so, because as I said, it was working before.
How can I verify that?
deewaveAuthor Commented:
ok, we finally hired an external consultant to complete that job, so I wont go much in details

1st, there is an issue with WinXP + Office2007 or WinXP + Office2010 combinaison. There are several threads on the web, but mainly we needed to use a split-dns and create a forward lookup zone for our external domains, so they could be resolved internally

2nd, OutlookAnywhere and AutoDiscover needed some tweaking
Set-OutlookProvider EXPR -Server exch2013.domain.local -CertPrincipalName none
Set-OutlookProvider EXPR -Server $null

3rd, upgrade all WinXP - Office2007 to client to either Win7 and/or Office2010. Because WinXP - Office2007 was still asking credentials (at startup only)
deewaveAuthor Commented:
not quite sure on how to attribute points in this case. Answer was well described by jjmck, but not very accurate. My question was how to reset Exchange 2013 settings to their default, finally ended up to something else. So 250 points and a grade A should be correct.

Thanks for the help!
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.