• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 179
  • Last Modified:

exchange 2010 certificate issue

Hi Experts,
I have a small network, one 2003 DC (file and print server) and 15 workstations. I have decided adding a seperate windows 2008 R2 with exchange 2010 and I did. Now I am able to send and receive an emails without any problem. However, I have an issue that is certificate. Since I didn't expect the exchange server, I used domain name abc.com (for example) but acutual domain name is abcxyz.com so I got a certificate from godaddy.com for abcxyz.com but abc.com. This gives me some issue. First I am getting security warning whenever I open outlook. I just hit yes or no then it opens outlook no problem. I also realized that out of office assistant is not working for all workstations. I think this is related to the security.
What is my best solution for this at this moment? I cannot reinstall both servers.
Do I have to install ceriticate server on exchange server? If so, please let me know how to.
Thanks in advance
0
Ksean
Asked:
Ksean
  • 3
  • 3
  • 2
1 Solution
 
MAS (MVE)EE Solution GuideCommented:
out of office assistant will if you configure as per below
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27314996.html


create an entry in your internal DNS server 'autodiscover.domain.com' pointing to your exchange server
0
 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
You dont need to re-install server or install certificate server.

Get a proper certificate from godaddy and install it in Exchange. - Create a new cert request from Exchange with correct domain info and that will solve your issues.

OOF issue is because of the wrong certificate/configuration of urls.
0
 
KseanAuthor Commented:
The problem is that I couldn't get a certificate for abc.com from godaddy.com because this is not my domain.
I will try abbasiftt's recommandation and let you guys know
Thanks
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
You don't need abc.com, get one for your own domain and reconfigure all exchange urls.

If the error is only internal, run get-clientaccessserver | fl name, *uri

The autodiscoverserviceinternaluri should point to a url in your cert and your internal DNS should resolve it.
0
 
MAS (MVE)EE Solution GuideCommented:
Create a new zone in your internal DNS server name it as abcxyz.com as create an A record 'mail.externaldomainname.com' pointing to your exchange server.

Then as mentioned above change all your URLs .
0
 
MAS (MVE)EE Solution GuideCommented:
Please ignore the above post.

Create a new zone in your internal DNS server name it as abcxyz.com and create an A record 'externalname.externaldomainname.com' pointing to your exchange server.

Then as mentioned above change all your URLs .

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27245435.html
Attached a sample command for 2 servers exchange environment. You make the changes and make both internal and external the same.

OOA.txt
0
 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
Any update?
0
 
KseanAuthor Commented:
Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now