Installing SSL on Exchange 2013

%3CLINGO-SUB%20id%3D%22lingo-sub-2272699%22%20slang%3D%22en-US%22%3EInstalling%20SSL%20on%20Exchange%202013%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272699%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20everyone%20and%20thanks%20for%20the%20help%20in%20advance.%26nbsp%3B%20I%20have%20been%20tasked%20with%20installing%20a%20SSL%20certificate%20on%20an%20Exchange%20Server%202013%20for%20a%20small%20organization%20with%20no%20IT%20help.%26nbsp%3B%20I%20an%20neither%20an%20Exchange%20or%20SSL%20expert.%26nbsp%3B%20Previously%2C%20the%20organization%20was%20using%20self-signed%20certificates%2C%20but%20now%20wants%20to%20allow%20users%20to%20access%20OWA%20as%20well%20as%20Outlook%20clients.%26nbsp%3B%20I%20installed%20the%20GoDaddy%20SSL%20on%20the%20server%20successfully%20and%20it%20is%20recognized%20in%20IIS%20and%20on%20the%20Exchange%20Admin%20Console.%26nbsp%3B%20However%2C%20I%20am%20confused%2Fterrified%20of%20the%20next%20step.%26nbsp%3B%20In%20reading%20documentation%2C%20it%20appears%20you%20assign%20services%20to%20the%20SSL%20through%20the%20Admin%20Console%2C%20but%20I%20have%20been%20fearful%20of%20taking%20the%20next%20step%20through%20lack%20of%20knowledge.%26nbsp%3B%20Currently%2C%20OWA%20can%20be%20accessed%20by%20going%20to%20%3CA%20href%3D%22https%3A%2F%2Fmail.mydomain.com%2Fowa%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmail.mydomain.com%2Fowa%3C%2FA%3E.%26nbsp%3B%20I%20see%20no%20bindings%20on%20the%20default%20website%20pointing%20to%20mydomain.com%20and%20actually%20stops%20access%20when%20I%20add%20a%20binding.%26nbsp%3B%20So%20I%20stopped%20before%20I%20hurt%20myself.%26nbsp%3B%20Would%20someone%20be%20able%20to%20walk%20me%20through%20the%20steps%3F%26nbsp%3B%20Do%20I%20really%20only%20need%20to%20add%20the%20service%20to%20the%20SSL%20in%20the%20Exchange%20Admin%20for%20OWA%20to%20work%20on%20this%20SSL%3F%26nbsp%3B%20Any%20help%20would%20be%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2272699%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

Hello everyone and thanks for the help in advance.  I have been tasked with installing a SSL certificate on an Exchange Server 2013 for a small organization with no IT help.  I an neither an Exchange or SSL expert.  Previously, the organization was using self-signed certificates, but now wants to allow users to access OWA as well as Outlook clients.  I installed the GoDaddy SSL on the server successfully and it is recognized in IIS and on the Exchange Admin Console.  However, I am confused/terrified of the next step.  In reading documentation, it appears you assign services to the SSL through the Admin Console, but I have been fearful of taking the next step through lack of knowledge.  Currently, OWA can be accessed by going to https://mail.mydomain.com/owa.  I see no bindings on the default website pointing to mydomain.com and actually stops access when I add a binding.  So I stopped before I hurt myself.  Would someone be able to walk me through the steps?  Do I really only need to add the service to the SSL in the Exchange Admin for OWA to work on this SSL?  Any help would be appreciated.

0 Replies