The SSL certificate server name is incorrect. ID no: c103b404
This error occurs when trying to view Public Folders in the Exchange System manager when he SSL certificate name differs between the FQDN and the local server name. The Exchange System Manager will not allow you to view the public folders as it believes the folder name to be incorrect.
This can be resolved using a front-end, back-end scenario, but what if you are stuck with a single Exchange server (ie. SBS) in your environment?
On following a few blogs and sites, the solution seems to be to remove SSL requirement for that particular folder in the IIS Manager. This didn’t work for me though – and I found a lot of people out there with unresoved issues on Experts Exchange etc.
The end solution was to use the ADSIEdit utility to manually stop the Exchange System Manager from using SSL.
The steps are as follows:
1) Install the ADSIEdit Utility (one of the Windows Server 2003 Support tools) from your SBS2003 CD (CD2) using suptools.msi
2) Run a Microsoft Management console (Start->Run->MMC)
3) Open the ADSIedit.msc (browse to the Support Tools folder)
4) Browse through to
Configuration > Services > Microsoft Exchange > Domain Name > Administrative Groups > First Administrative Group > Servers > Servername > Protocols > HTTP > 1 > Exadmin
5) Right click msExchSecureBindings, and click Properties
6) Highlight :443: and click Remove
7) Click OK
Restart the Exchange System Attendant and the IIS Admin service
Exchange system manager will now no longer try to use SSL when connecting to the service.


Thanks – that is really working …
Milos said this on July 1, 2008 at 5:07 pm |
Thanks a lot!!! You saved me
Jakub Siroky said this on July 18, 2008 at 5:00 pm |
Fantastic. A solution that works. Thank you.
Jamie Callaghan said this on August 8, 2008 at 2:23 am |
Awesome stuff. Works like a charm!!!
Vito said this on August 21, 2008 at 6:57 am |
THANKS!!
j said this on September 22, 2008 at 10:18 pm |
what are the security ramifications of this, with respect to Outlook Web?
Jeff said this on October 7, 2008 at 6:55 pm |
The only security issues are that traffic sent between the ESM and the Exchange server is unencrypted. There is no impact on OWA. If concerned about encryption between the management console and the Exchange server you can always RDP into the Exchange server and run the Exchange System Manager locally.
Roachy said this on October 8, 2008 at 5:40 am |
extremely helpful. my compliments sir.
Big O said this on October 10, 2008 at 2:50 am |
Much Appreciated, getting rather worried about not being able to see the public folders…. SBS sucks
HK135 said this on October 20, 2008 at 12:32 pm |
[...] Jos törmäät moiseen ongelmaan eikä Microsoftin KB:n antamat ohjeet riitä korjaamaan vikaa, niin ratkaisu löytyy täältä. [...]
suursavo.org » Blog Archive » Exchange Public Folders SSL-sertifikaattiongelma said this on November 10, 2008 at 2:19 pm |
Thanks – saved my day (or night maybe)
Anders said this on December 10, 2008 at 9:46 am |
Tanks,
It works fine, good luck with your blog.
A Admin.
Von said this on December 10, 2008 at 11:49 am |
[...] schimb a functionat: Gasita aici: The steps are as [...]
vandrei Blog » Blog Archive » Exchange System Manager said this on January 6, 2009 at 10:27 am |
Thanks,
It works like acharm, very nice job !
Hilitec
Hilitec said this on March 6, 2009 at 12:31 am |
GJ m8y, proper pleased with that.
Thanks V much
Andy said this on March 13, 2009 at 12:04 pm |
Wow. Hours and hours of trying to fix this…and THAT was all I had to do?
THANK YOU!!!
sys said this on March 19, 2009 at 10:47 pm |
No luck here. Some other service to restart, maybe?
Jim said this on May 8, 2009 at 5:41 pm |
Found it! When I removed SSL from Exadmin, it either didn’t stick or I screwed up the 128 bit/require SSL box sequence. Thanks.
Jim said this on May 8, 2009 at 6:24 pm |
Worked perfectly. Thank you for posting the fix.
Corey said this on May 14, 2009 at 12:19 am |
After all these hours searching for solution finally bingo!
Thanks a lot!!
Tomaz said this on July 3, 2009 at 11:47 am |