Import-ExchangeCertificate -FileData (]$(get_content -Path c:\whereveryouput\cert.pfx -Encoding byte -ReadCount 0)) -Password:(Get-Credential).password
Once this is done, copy over the file you’ve just created to your other CAS servers and import using the command: Set-Content -Path “C:\somethinghere\cert.pfx” -Value $file.FileData -Encoding Byte You’ll be prompted for a username & password.Īfter this, dump the contents of the $file variable somewhere using: $file = Export-ExchangeCertificate -Password (Get-Credential).password -BinaryEncoded:$true
#Configure autodiscover exchange 2010 install#
If you are going to have multiple CAS servers an easy way to install them is to do a complete install on one of your CAS servers following the above process and then export the certificate & private key using the command (make sure you have your Thumbprint handy): Hi, came across some challenges with certificate imports across multiple front end servers as the private key wasn’t on the other servers. I corrected my statement, sorry for misinformation. But you definitely need Autodiscover configuration on HE 2010. Please check:Ĭould you let me know why you saying this?Īctually I’m not sure why I said that. Thanks in advance.Īttention: You don’t need Autodiscover configuration after Exchange Server 2010 SP1. Everything, except autodiscover, was working fine, till I ran this script.Ĭan someone please help. However works fine.Īll that i did was replace all “” with “”. is just giving message “Internet explorer cannot display the webpage”.
Now my OWA is not working by domain name. I shouldn’t have run the script, without reading the entire thread. If you are still having issues, then you need to check your SSL configuration. We have more than three different Exchange environments with using same configuration without problem. Your Autodiscover hostname: Īs you see, you have to seperate mx hostname and autodiscover IP addresses. We don’t have any Autodiscover issue right now, I hope we can fix your issue too. You are right, this script breaks EMC but I changed it after I saw the issue. And if I remove the 80 binding from the Default website, then EMC breaks again.īear in mind, I need to tread carefully because we already have clients live on the installation so I can’t afford to break anything. It’s OK if I bind an IP to 443, but not to 80.
Do I need to remove that virtual directory and create a new Autodiscover site?Īnd, if I bind an IP to the default website, it breaks EMC. I’ve installed a hosted Exchange 2010 environment which is working well, except for the Autodiscover issue.Įven though I’ve created the Autodiscover_redirect site and have configured it correctly, I still can’t get this working.īy default, Exchange 2010 has installed an Autodiscover virtual directory under the default website. You won’t get any SSL error on Outlook after changes. New-ItemProperty IIS:\Sites\”Default Web Site” -name bindings -value ) -PSPath IIS:\ -location Autodiscover Remove -WebBinding -Name “Default Web Site” -BindingInformation *: 80: New-Item "C:\inetpub\Autodiscover_redirect\Autodiscover\Autodiscover.xml" – type File New-Item "C:\inetpub\Autodiscover_redirect\Autodiscover" - type Directory New-Item "C:\inetpub\Autodiscover_redirect" - type Directory
0 kommentar(er)
