microsoft exchange 2010

reconfiguring Microsoft Exchange to use Fully Qualified domain name.  trying to reconfigure my exchange server  to accept a fully qualified domain name ( FQDN).   CHANGE INTERNAL NAME SERVER.LOCAL TO FQDN MAIL.myservername.com.  Below is a link on how to  get this done. I don't know how accurate this article is.  Looking for advice on this issue. Trying to upgrade SSL cert. on  exchange 2010.  


http://support.godaddy.com/help/article/6281?locale=en&ci=46061
patrickstAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Miguel Angel Perez MuñozCommented:
You don´t need change your fqdn server name. Simply creating split dns configuration resolve your problem. Resolve with internal IP using external hostname, make your clients connects to your external hostname (p. ex mail.domain.com) and problems go away.
0
Jonathan GeorgeCommented:
DigiCert has some good documentation on this (https://www.digicert.com/internal-domain-name-tool.htm), and they also have a tool that will help you make the necessary changes on the Exchange server. You do not have to use DigiCert to use their tools and documentation.
0
Michael MachieFull-time technical multi-taskerCommented:
In my honest opinion AVOID SPLIT DNS AT ALL COSTS!

Here is the solution to convert from .local to FQDN for Exchange 2010. I literally just performed this process last night..

Use your own internal Exchange Server name in place of CAS1 in the below commands:

Set-ClientAccessServer -Identity CAS1 –AutodiscoverServiceInternalUri https://webmail.mycompany.com/autodiscover/autodiscover.xml

Set-WebServicesVirtualDirectory -Identity “CAS1EWS (Default Web Site)” - InternalUrl https://webmail.mycompany.com/ews/exchange.asmx

Set-OABVirtualDirectory -Identity “CAS1oab (Default Web Site)” –InternalUrl https://webmail.mycompany.com/oab

Set-UMVirtualDirectory -Identity “CAS1unifiedmessaging (Default Web Site)” - InternalUrl https://webmail.mycompany.com/unifiedmessaging/service.asmx

When done running these commands, restart IIS -OR- recycle the MSExchangeAutodiscoverAppPool

Do this off-hours as it will interrupt service briefly.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

patrickstAuthor Commented:
Machientet


going to try the procedure over the weekend.  Would you please look at the attach file and  see if I have the correct  Syntax.  All the  set of commands is  what I think are correct.

please let me know thanks
convert.localto-FQDN.txt
0
Michael MachieFull-time technical multi-taskerCommented:
Hi, I'm a friend posting for MachieNet at his request to update you because you want confirmation before the weekend.

He will try to look at this a bit later today and respond. Unfortunately he happens to be driving all day. He cannot look at this just yet and has asked me to post this to notify you.
0
patrickstAuthor Commented:
OK  thanks for the post I will wait for his responds later today.

thanks
0
patrickstAuthor Commented:
Hi Machienct

did you have time to take a look   at the  text file yet.

thanks
0
Michael MachieFull-time technical multi-taskerCommented:
Really sorry about the long delay, truly. Drove all day to repair a solar system and when I got there it was more than a repair - it was a full re-install! Awesome because I never installed it in the first place and had to learn the configuration! Being an off-grid system in the middle of nowhere we had no internet, even cell signal, until it was finished.

OK, down to your business..
(Default web site): No, leave this as long as your default website on the server is your mail.domain.com . If you have configured it as other than the default site on the server then change to the site name. Exchange SHOULD recognize Default Web Site as the default for your server. You should have no issues. If for some reason it fails you can specify your site name.
 
Do not add any "-", run exactly as specified.

If not using Unified Messaging then you will error on the last command - this is normal.

Let me know how it works out but I will say that I had no issues with my change-over but also have no experience fixing this if it fails and causes problems, so I strongly suggest a system backup be done first... (just adding that disclaimer)
0
patrickstAuthor Commented:
All

Still having problems upgrading MS exchange server fully qualified domain name. When installing the internalURL EWS

Set-webServicesVirtualDirectoery -Identity " Nameof server\EWS {Deafult web Site}" -InternalURL https://mail.doaminname.com/ews/exchange.asmx  i get an error ( see attach file).

can anyone help
Expert-exchange-1A.png
0
Jonathan GeorgeCommented:
Just to re-post this, you might find it useful if you haven't checked it out all ready. The DigiCert Internal names tool is easy to use!

DigiCert has some good documentation on this (https://www.digicert.com/internal-domain-name-tool.htm), and they also have a tool that will help you make the necessary changes on the Exchange server. You do not have to use DigiCert to use their tools and documentation.
0
patrickstAuthor Commented:
I replace the " webmail" with " mail". And that work,  YOu can close the ticket
0
Michael MachieFull-time technical multi-taskerCommented:
I apologize for that confusion patrickst... I should have been more specific and stated such to you. By (webmail) I meant (webmail public server name). In your case it is mail.domain.com .

Sometimes little things can be overlooked and thanks for pointing that out to me.
0
patrickstAuthor Commented:
no  problems you help me out and everything is good.  we can close the out
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.