Exchange 2010, .local domain and a wildcard certificate
i have started new company , 1 of first jobs come across desk replace certificate on exchange server expires @ end of month. tried renew current cert godaddy has mydomain.local 'subject alternate name' cannot renewed. have wildcard certificate here have used internal clients certificate error resolving servername.mydomain.local not match our external name on certificate. there easy way fix this? have read stuff split dns , changing virtual directories via powershell make work want make sure nothing going stop working during process server live on 2500 users.
here article looking at. refers exchange 2013 there different commands exchange 2010 environment? http://exchangeserverpro.com/avoiding-exchange-2013-server-names-ssl-certificates/
hi,
i ended calling microsoft on issue. here commands ran on server work:
set-clientaccessserver -identity "mailservername" -autodiscoverserviceinternaluri https://mail.companynameoncert.com/autodiscover/autodiscover.xml
set-webservicesvirtualdirectory -identity "mailservername\ews (default web site)" -internalurl https://mail.companynameoncert.com/ews/exchange.asmx -externalurl https://mail.companynameoncert.com/ews/exchange.asmx
set-oabvirtualdirectory -identity "mailservername\oab (default web site)" -internalurl https://mail.companynameoncert.com/oab -externalurl https://mail.companynameoncert.com/oab
basically have redirected autodiscover, webservices , oabvirtualdirectory point address matches new certificate , created dns record resolves address email server. working bar couple of issues.
1. old cert configured pop3 , imap. unable work there no cert bound either of protocols now. engineer guarantees me cert used if tries connect protocols have not tested yet.
2. clients worked ok without reconfiguration except couple of pilot machines running windows 10 , office 2016. these machines had have email profiles deleted , recreated them work.
Windows Server > Windows Server General Forum
Comments
Post a Comment