infospecs
asked on
Exchange 2010 new ssl cert not including *.local server name
Since new ssl cert requirements are not allowing the servers local names to be included I have run into a few issues. I have followed the posts that go through the Exchange Shell and make the following changes for the .local changes:
Set-ClientAccessServer -Identity “server-name” –AutodiscoverServiceIntern
Set-WebServicesVirtualDire
Set-OABVirtualDirectory -Identity ““server-name”\oab (Default Web Site)”-InternalUrl https://”mx-record name”/oab
1.
2. Open IIS Manager.
3. Expand the local computer, and then expand Application Pools.
4. Right-click MSExchangeAutodiscoverAppP
Since then the clients are getting multiple errors in Outlook. First is a cert error that initially points to their mx-record name and then they get one that is coming from their firewall... The next issue is that they can no longer activate the Out of Office assistant from outlook either. They are getting the server is unavailable.. That started after I completed the above changes... OOF works from OWA..
Set-ClientAccessServer -Identity “server-name” –AutodiscoverServiceIntern
Set-WebServicesVirtualDire
Set-OABVirtualDirectory -Identity ““server-name”\oab (Default Web Site)”-InternalUrl https://”mx-record name”/oab
1.
2. Open IIS Manager.
3. Expand the local computer, and then expand Application Pools.
4. Right-click MSExchangeAutodiscoverAppP
Since then the clients are getting multiple errors in Outlook. First is a cert error that initially points to their mx-record name and then they get one that is coming from their firewall... The next issue is that they can no longer activate the Out of Office assistant from outlook either. They are getting the server is unavailable.. That started after I completed the above changes... OOF works from OWA..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER