Exchange Server relocation (Internal IP change)

Hello,
We are in process of relocating our Data Center with this move we need to change our internal IP For Exchange ( CAS,HT,MB and Edge Transport Servers).
Server A
Client Access Role & Hub Transport
Server B
Mail Box Role
Server C
EDge Transport Role
Do I need to change IP's in any sequence or I can just them.
I really appreciate any insight on how to change IP on the Exchange 2010 SP2.
Thanks
RG

Hi Rao G,
1. Please make sure the certificate on the server is not expired. Also make sure the thumbprint on the certificate matches the thumbprint enabled for SMTP.
2. Please make sure that the Micorosft Exchange Credential Service (EdgeCredentialSvc) is running on the target Edge Transport server.
3. Please Re-subscribe the Edge Transport server, to generate new credentials. Following is the details:
Remove-EdgeSubscription
http://technet.microsoft.com/en-us/library/bb124807(v=exchg.141).aspx
New-EdgeSubscription
http://technet.microsoft.com/en-us/library/bb123800(v=exchg.141).aspx
4. Please run Start-EdgeSynchronization on Hub Server, to have a test.
5. Also suggest to check Event Log for the further troubleshooting.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

Exchange Server 2013: Internal Certificate Issue

Dear All,
I have MS Exchange 2013 with domain name: Exchange.local (fqdn: ex001.exchange.local).
I had created the accepted domain for xyz.com. I bought the Wildcard Certificate for *xyz.com. I had issued the certificate to my MS Exchange server.
External/Internet users: they can setting up and connected with MS Outlook
but I had problem with internal. when I setup account to MS Outlook. it failed and cannot connected to MS Exchange server because invalid ex001.exchange.local.
Do you have best solution and commend on this issue for internal users?
BR,
KH
[email protected]

Hi khemarin,
Did you set correctly the internal url´s for the services?
For Autodiscover URL:
If you are using a single server or all servers are in the same AD site, then the following commands can be used:
Get-ClientAccessServer | Set-ClientAccessServer -AutodiscoverServiceInternalUri https://mail.example.net/autodiscover/autodiscover.xml
However if you are using multiple servers in multiple AD sites, then you need to set the commands as per the box below, replacing "CAS-Server" with the real name of the server that holds the CAS role.
Set-ClientAccessServer -Identity "CAS-Server" -AutodiscoverServiceInternalUri https://mail.example.net/autodiscover/autodiscover.xml
For Webservices URL:
As with Autodiscover, if you are using a single server then the following commands can be used:
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -InternalUrl https://mail.example.net/ews/exchange.asmx -ExternalUrl https://mail.example.net/ews/exchange.asmx
However if you are using multiple servers, then you need to set the commands as per the box below, replacing "CAS-Server" with the real name of the server that holds the CAS role.
Set-WebServicesVirtualDirectory -Identity "CAS-Server\EWS (Default Web Site)" -InternalUrl https://mail.example.net/ews/exchange.asmx -ExternalUrl https://mail.example.net/ews/exchange.asmx
For Outlook Anywhere URL:
Right click on the Client Access Server and choose Properties. Click on the tab Outlook Anywhere and adjust the URL to match the external name on the SSL certificate.
You should also need to check OAB Virtual Directory on IIS and see if it is enabled for SSL.
And you should have a Split DNS in this case.
I hope it helps.
David Paris Vicente

Exchange Server 2013 internal and external DNS records

I recently installed Exchange Server 2013 and I've register a pubic ip too for exchange server. How can I create internal DNS as well MX record for my Exchange server to send and receive internet mails. It's my first time configuring exchange for a organization.
registered domain name=====np.bbcmediaaction.org
public ip=====202.166.212.221

Hi,
For external mail flow, we need the following DNS records: MX records for the domain part of the external recipient, A records for the destination messaging servers. For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/bb676467(v=exchg.150).aspx
Additionally, to ensure external mail flow works well, we also need to configure send connector.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange Server 2010 Edge - Port Change

I am learning Exchange 2010 and have set it up. BUT my ISP blocks port 25 so I thought no problem I have a windows VPS set up I will install an Exchange Edge Server there and then it will work. However it looks like exchange uses port 25 to send the messages
to the Edge server.
I have used this command to change the ports of the send connectors but my router shows it is still trying to send on port 25. Any ideas?
Set-SendConnector “EdgeSync - Home To Internet” -port 2525
Set-SendConnector “EdgeSync - Inbound to Home” -port 2525
Get-SendConnector | fl
shows the ports as set to 2525
Any Ideas?

For home learning I would recommend you approached this from a slightly different angle.
Don’t make any changes to your servers that you would not encounter in a real environment.
Get a POP3 connector (POPCON is cheap) and pull all email from your gmail account using that application.
That application will then dump the messages using SMTP to your Edge or your HT (you choose)
Outbound messages are obviously SMTP and you can configure your servers to authenticate to your ISPs relay and send messages in the normal way.
"Dan Messano" wrote in message news:fa3b47e8-daa0-46b0-a78a-d646b3d5b7fa...
I am learning Exchange 2010 and have set it up. BUT my ISP blocks port 25 so I thought no problem I have a windows VPS set up I will install an Exchange Edge Server there and then it will work. However it looks like exchange uses port 25 to send the messages
to the Edge server.
I have used this command to change the ports of the send connectors but my router shows it is still trying to send on port 25. Any ideas?
Set-SendConnector “EdgeSync - Home To Internet” -port 2525
Set-SendConnector “EdgeSync - Inbound to Home” -port 2525
Get-SendConnector | fl
shows the ports as set to 2525
Any Ideas?
Mark Arnold, Exchange MVP.

Display name of shared calendar in Outlook clients after name change on the Exchange Server

I have changed the name of a conference room resource calendar on the Exchange server but the name change is not being reflected in the end user's Outlook clients. I tested a remove/re-add and that worked but I cannot have everyone in the company do this.
Is there anyway to force the change down to the Outlook clients?

I don't know for sure, but if this is the case, then it's highly likely that the GUID is used by the client after its first view of the calendar. From that point on, it appears it doesn't "revisit" the directory for updated names.
We'd need Outlook team feedback for confirmation.

Outlook 2011 Exchange server name changes

I set the server name in Outlook 2011 to the "public" FQDN. Network DNS is set to resolve this name to the private IP address of the Exchange server. This configuration works properly for all my users, whether they are connected locally or remotely.
For one computer, though, when connected locally, Outlook changes to the "private" FQDN of the Exchange server. This undesired change then requires editing the server name when the computer is remotely connected.
How do I get Outlook to leave the server name as the "public" FQDN?

Try going to [mactopia.com], which is Microsoft's Mac help area or you could go to [microsoft.com/mac]. These Discussion boards are for Apple products, so you should find help over there.

Problems using Outlook 2013 with Exchange Server Small Business Server 2003

Hello,
We have just upgraded our Office suite from Office 2007 Pro to Office 2013 Pro. When I try to configure Outlook 2013 to connect to Exchange Server 6.5 (SMS 2003) I get an error "Outlook 2013 being blocked by current version of Exchange Server".
Outlook 2013 at present is not communicating with Exchange server 6.5
Are there any fixes I have to install on our SMS 2003 server to allow Outlook 2013 to work with SMS 2003 Exchange Server?
Any configuration changes I need to make? Any help is appreciated.
Thx
John G.
John Grace

Hi
Outlook 2013 is not supported with exchange 2003:
http://technet.microsoft.com/en-us/library/ee624351.aspx#section10
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange Server 2013 - Lab setup with internal emails only

Hi,
I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
go over the internet.
I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
Regards,
Nithin

Hi,
You need not to configure send/receive connectors for internal email.
The following article for your reference:
http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
Default Receive connectors created during setup
Certain Receive connectors are created by default when you install the Mailbox server role.
Default Receive connectors created on a Mailbox server running the Transport service
When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
These connectors are the following:
Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
mentioned, their TransportRole value is HubTransport.
To view the default Receive connectors and their parameter values, you can use the
Get-ReceiveConnector cmdlet.
Default Receive connectors created on a Front End Transport server
During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
In a typical installation, no additional Receive connectors are required.
Niko Cheng
TechNet Community Support

Http 500 internal server error exchange server 2013

Hello Everyone
Here is my little scenario.
i have a domain named contoso.com
i then installed exchange server 2013 in my environment. cas and mailbox server are on seperate box.
switched of my exchange servers for a week, during that period i changed the netbios name of my domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
a week later i switched on my exchange servers. during the same time i created two new servers one cas and the other mailbox
i now have 2 cas server and 2 mailbox server
problem now is that when i log into my ecp on one of my cas server using https://servername/ecp. after inserting my username and password i get http 500 internal error
although with exchange management shell i can connect to all the servers

-->switched of my exchange servers for a week, during that period i changed the netbios name of my
domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
Did you change your domain to toso.com? If yes then your first/previously installed exchange is broken. Exchange server is fully integrated with domain.
Renaming of domain is not supported in Exchange2007/2010/2013. (Even in Exchange2000/2003 you need some netbios name resolution. Check this for an info)
Anyway did you try login to the newly installed exchange (i.e. Exchange installed after Netbios rename)?
Try that first https://newserverip/ECP and https://newserverip/OWA (that is supposed to work), If
that works I suggest you try to uninstall the previously installed Exchange after moving the database using database portabilityand install again as new
server.
Please get back with the result.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Outlook 2013 not connect with Exchange server 2013 in internal network

Hello All,
I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network.
Can you please suggest as soon as possible.
Thanks,
Parvez

Hi,
Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
Thus, let’s try the following resolutions:
1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
3. Check if the above host name is in your certificate.
Thanks,
Angela
Angela Shi
TechNet Community Support

Email changes on iPad via IMAP are not updating on Exchange Server

I have set up IMAP access to my company email from the iPad. Reason being so that I can manage emails (delete, move to folders etc) whilst working off-line.
Seemed to work fine for a day or so but now any changes made via the iPad are not syncing and updating the Exchange Server once back on-line.
Any hints?

I see. okay, well, on my iphone with iOS 3.x I always saw similar issues. I had email on 2 Exchange servers, so one of the accounts had to be IMAP, and it never worked properly.
Yes, it would mark emails as being read, etc, but anytime I moved or deleted an email, it would do so, but would also keep a copy on the original mailbox it was in. Basically the IMAP "Expunge" command wasn't properly being sent by the iPhone
I submitted this as a bug to Apple via bugreporter.apple.com and they confirmed it. Whether it's fixed or not in iOS 4 I don't know as iOS 4 has the ability to use multiple Exchange accounts so I no longer need the IMAP.

Integrating Exchange Server in the cloud with Project / Sharepoint Server internal

Hi,
I wonder how do I integrate service Exchange Server with Project Server 2010.
I have a Project Server 2010 you need to send emails with project updates and other integrations with Outlook.O standard procedure is to perform procedures (run commands in Exchange Server Shell) and create users in Project Server.
But I have a situation where my client uses a service exchange in the cloud and not a server for internal mail.
How do I integrate Project Server with Exchange this scenario where the mail server is an external service (cloud)?
I made the settings as the procedure () but got no success, no mail was received to be alert or reminder:
Below are the screens with the settings that were made.
Crawl Resource Configuration (http://technet.microsoft.com/pt-br/library/ee806927(v=office.14).aspx)
1) I Installed SMTP service on my server.
2) I made the configuations above
3) I configured the outgoing/Ingoing Setting in Sharepoint Central Administration

Hi Marcelo,
Without providing the extended rights to project user, I dont think you will be able to successfully integrate project server with exchange cloud. Here is the technet article about how to integrate it with extended rights which needs running commands running
on exchange server:
http://technet.microsoft.com/en-in/library/ff468700%28v=office.14%29.aspx
Vikram Daruru - MSFT

CANNOT ACCES EXCHANGE ADMIN CENTER (ECP) ON EXCHANGE SERVER 2013. GOT HTTP 500 INTERNAL SERVER ERROR

HI, I just installed Exchange server 2013 Standar SP1 on a windows server 2012. I have 3 servers one is a Domain Controller, the other one has the MBX role, and the last one the CAS role, first i installed the MBX and after the CAS role, i passed
prerequisite check without any issue. However when I tried access Exchange Admin Centre (ECP) at https:\\servername\ecp
I got HTTP 500 Internal Server Error saying "This website cannot display the page. Most likely causes: 1. The website is under maintenance. 2. The website has a programming error." I tried access ECP at https://localhost/ecp and
I got the same problem. Under either cases I was able to see the logon page of ECP and I was able to enter my credential (e.g. domain\user name, password). However I got HTTP 500 Internal Server Error at the next page.
I appreciate your help, on my case.

Hi,
The link that Jatin points to should be this.
https://social.technet.microsoft.com/Forums/en-US/2f64d305-e9e2-4f48-a5b4-4f72d7bca801/exchange-2013-owaecp-http-500-internal-server-error?forum=exchangesvrclients
Please view the Application Pool to check whether the version of .NET Framework is 4.0 and try the following command.
%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i.
If this does not help then please check if there is any warnings or errors in Event Log and take your time to post them for my further troubleshooting.
Thanks.

Exchange server name not changing in mail profile after migration from 2010 to 2013

Following a migration from 2010 to 2013 we are finding that for a number of users the old exchange server address stays in the mail profile (control panel -> mail -> e-mail accounts) which causes Outlook not to load.
We are able to go into control panel -> mail -> e-mail accounts and change this manually to the new exchange 2013 server address but we have quite a number of users and don't really want to do it manually.
Shouldn't it be updating automatically and if so why is it?

Hi,
Yes, it should be changed by autodiscover. Does this issue occur to all the migrated users?
I have seen this kind of issues before when migrating from Exchange 2003/2007 to Exchange 2010. The most efficient way is to rebuild the Outlook profile.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Messaging tracking logs filename format changed in Exchange Server 2013 sp1

Hi,
I have noticed that the file name format is changed for exchange server 2013 sp1.
Now it will have hh attached to it like
MSGTRKMSyyyymmddhh-n.log;
MSGTRKMDyyyymmddhh-n.log:
MSGTRKyyyymmddhh-n.log.
So the "hh" will goes from 00 to 23 for single day.
So Lets say at 24 april 2014 first fill is created @7.30 AM, so the first file name will be
MSGTRK2014042400-1.log. Now exchange server will create new file every hour by incrementing hh part of file name. Now the last file i.e
MSGTRK2014042423-1.log will be created on 25 April 2014 at 6.30 AM.
I am not able to understand why exchange server is creating the file with old date on next day ( with 24 April on file name time stamp on 25 April).
And also how it will be decided to create the first file @ 7.30 AM.
Can anyone explain to me about this ? Why it is happening like this?
Thanks
Sandeep Gupta

Hi Sandeep,
This could related to the time difference. What’s the time zone of your server? In my lab, many files in the last day were created in the next day. For example, files in 20140410
were created on 20140411.
Also, as you mentioned, the file name format is as:
MSGTRKMSyyyymmddhh-n.log;
MSGTRKMDyyyymmddhh-n.log:
MSGTRKyyyymmddhh-n.log.
However as I know, the format is like
MSGTRKyyyymmdd-m.log, it will not have “hh”(you mean hours) in the behind and the file is not created every hour but create a new file when the old is full. So please capture some screenshots of the message tracking files
and the date/time information of the file to verify.
Title: Message Tracking
Link:
http://technet.microsoft.com/en-us/library/bb124375(v=exchg.150).aspx
Regards, Eric Zou

Exchange Server relocation (Internal IP change)

Similar Messages

Maybe you are looking for