diff --git a/Servers/Microsoft Exchange/Configuring ACME LetsEncrypt Bot.md b/Servers/Microsoft Exchange/Configuring ACME LetsEncrypt Bot.md index edaa9d7..5cf51a1 100644 --- a/Servers/Microsoft Exchange/Configuring ACME LetsEncrypt Bot.md +++ b/Servers/Microsoft Exchange/Configuring ACME LetsEncrypt Bot.md @@ -35,36 +35,36 @@ * Searching the external IP of the server on [Shodan](https://www.shodan.io/) will reveal all open ports. ### Troubleshooting: -If you find that any of the services such as [https://mail.example.org/ecp](https://mail.example.org/ecp), [https://autodiscover.example.org](https://autodiscover.example.org), or [https://mail.example.org/owa](https://mail.example.org/owa) do not let you log in, proceed with the steps below to correct the "Certificate Binding" in IIS Manager +If you find that any of the services such as [https://mail.example.org/ecp](https://mail.example.org/ecp), [https://autodiscover.example.org](https://autodiscover.example.org), or [https://mail.example.org/owa](https://mail.example.org/owa) do not let you log in, proceed with the steps below to correct the "Certificate Binding" in IIS Manager: - * Open "**Server Manager**" > Tools > "**Internet Information Services (IIS) Manager**" - * Expand the "**Connections**" server tree on the left-hand side of the IIS Manager - * Expand the "**Sites**" folder - * Click on "**Default Web Site**" - * On the right-hand Actions menu, click on "**Bindings...**" - * A table will appear with different endpoints on the Exchange server > What you are looking for is an entry that looks like the following: - * **Type**: https - * **Host Name**: autodiscover.example.org - * **Port**: 443 - * Double-click on the row, or click one then click the "**Edit**" button to open the settings for that endpoint - * Under "**SSL Certificate**" > Make sure the certificate name matches the following format: "**\[Manual\] autodiscover.example.org @ YYYY/MM/DD**" - * If it does not match the above, use the dropdown menu to correct it and click the "**OK**" button - * **Type**: https - * **Host Name**: mail.example.org - * **Port**: 443 - * Repeat the steps seen above, except this time for "**mail.example.org**" - * Click on "**Exchange Back End**" - * On the right-hand Actions menu, click on "**Bindings...**" - * A table will appear with different endpoints on the Exchange server > What you are looking for is an entry that looks like the following: - * **Type**: https - * **Host Name**: - * **Port**: 444 - * Repeat the steps seen above, ensuring that the "**\[Manual\] autodiscover.example.org @ YYYY/MM/DD**" certificate is selected and applied - * Click the "**OK**" button - * On the left-hand menu under "**Connections**" in IIS Manager, click on the server name itself - * (e.g. "**EXAMPLE-EXCHANGE (DOMAIN\\dptadmin**") - * On the right-hand "**Actions**" menu > Under "Manage Server" > Select "Restart" - * Wait for the IIS server to restart itself, then try accessing the webpages for Exchange that were exhibiting issues logging in +* Open "**Server Manager**" > Tools > "**Internet Information Services (IIS) Manager**" +* Expand the "**Connections**" server tree on the left-hand side of the IIS Manager +* Expand the "**Sites**" folder + * Click on "**Default Web Site**" + * On the right-hand Actions menu, click on "**Bindings...**" + * A table will appear with different endpoints on the Exchange server > What you are looking for is an entry that looks like the following: + * **Type**: https + * **Host Name**: autodiscover.example.org + * **Port**: 443 + * Double-click on the row, or click one then click the "**Edit**" button to open the settings for that endpoint + * Under "**SSL Certificate**" > Make sure the certificate name matches the following format: "**\[Manual\] autodiscover.example.org @ YYYY/MM/DD**" + * If it does not match the above, use the dropdown menu to correct it and click the "**OK**" button + * **Type**: https + * **Host Name**: mail.example.org + * **Port**: 443 + * Repeat the steps seen above, except this time for "**mail.example.org**" + * Click on "**Exchange Back End**" + * On the right-hand Actions menu, click on "**Bindings...**" + * A table will appear with different endpoints on the Exchange server > What you are looking for is an entry that looks like the following: + * **Type**: https + * **Host Name**: + * **Port**: 444 + * Repeat the steps seen above, ensuring that the "**\[Manual\] autodiscover.example.org @ YYYY/MM/DD**" certificate is selected and applied + * Click the "**OK**" button + * On the left-hand menu under "**Connections**" in IIS Manager, click on the server name itself + * (e.g. "**EXAMPLE-EXCHANGE (DOMAIN\\dptadmin**") + * On the right-hand "**Actions**" menu > Under "Manage Server" > Select "Restart" + * Wait for the IIS server to restart itself, then try accessing the webpages for Exchange that were exhibiting issues logging in ### Additional Documentation: