Odd change in exchange 2010.

so i was moving dns providers and as a result my mail stopped flowing.. nothing out of the ordinary
how ever once things started getting set up again i got IP Resolution Error when running tests on the domain..
i started poking round the logs and i noticed my smtp sender had changed to one i had not seen before.
ran the troubleshooting assistant and got that same smtp server whiich is not my domain and not sure how it got changed or where to change it back
this is a what im seeing on one of the tests
[email protected] where did it get that from i never put that in and im trying to find out how it got changed to that from my domain.. any ideas
and i see mail.Fabrikam.com as my smtp server and no idea where that came from or how it got changed or even worse how to change it back to mail smtp server

Hi,
Please ping your Exchange transport server and check whether the DNS record for your server is resolved. Also send a message and collect the NDR message for more troubleshooting.
In Event Viewer, please confirm if there is any logs related to your mail flow issue. Please refer to the following to do some troubleshooting and collect the results for further analysis:
Troubleshooting Mail Flow and SMTP
http://technet.microsoft.com/en-us/library/aa996805(v=exchg.65).aspx
Exchange 2010 mailflow troubleshooting guide
http://blogs.technet.com/b/ehlro/archive/2014/01/15/exchange-2010-mailflow-troubleshooting-guide.aspx
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

Change to Exchange 2010 after SP3, Update 5 installed

After updating Exchange 2010 from SP3 Update 2 to Update 5, a change has occurred for users with SendAs and Full Access to other mailboxes. Version 14.3 (build 123.4).
Before the Update, after giving a user these permissions to another user's mailbox, the mailbox would show in their Outlook 2010 client, and everything worked as expected.
After Update 5 was installed, when users select the other user's mailbox, they get a message "the folders are not available," or the connection to the Exchange server is not working." They can access their own mailbox with no issues.
The other mailbox has to be added to the Outlook client via Account Settings, Account Settings, Change, More Settings, Advanced tab, Add the other mailbox. The mailbox then shows up twice on the client, but only the one that has been added works,
the original still gives the same error.
Lou H.

Hi,
I have seen some people have the same issue with you. After upgrading to Rollup 5, they need to add others' mailboxes that they have full access permission and send as permission manually on Outlook. But when they upgrade Outlook to 2010 SP2, this issue
is solved. I recommend you upgrade your Outlook to 2010 SP2 and check the result.
Besides, I'm not sure what changes after Rollup 5 lead to this issue, there is no official article explain it, thanks for your understanding.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Staging the NLB cluster Static port change of Exchange 2010 CAS or do it all in one day ?

Folks,
Here is the server deployment in my AD domain:
Email flow and Outlook client connection go through the NLB cluster VIP email.domain.com.au which is served by the following server:
PRODHT-CAS01 (HT-CAS Server Windows NLB node 1)
PRODHT-CAS02 (HT-CAS Server Windows NLB node 2)
Public Folder access through Outlook client goes through the following servers:
PRODMBX01 (Stand-alone Mailbox Server 1) no DAG
PRODMBX02 (Stand-alone Mailbox Server 2) no DAG
Can I make the changes first on the first stack of Exchange Server set as below first:
PRODHT-CAS01 (HT-CAS Server NLB node 1)
PRODMBX01 (Stand-alone Mailbox Server 1) no DAG
in order to test the Outlook email & Public Folder connectivity in the first week and then followed by the rest of the server set:
PRODHT-CAS02 (HT-CAS Server NLB node 2)
PRODMBX02 (Stand-alone Mailbox Server 2) no DAG
would that cause the NLB or user email access problem?
Do I have to make the changes all in one day for those four servers followed by the reboot?
Reason of changing: The hardware load balancer (Riverbed) requires to have static RPC port to work properly.
This is the article to change the Static port in my NLB cluster Exchange HT-CAS server role on Exchange Server 2010 SP2: http://social.technet.microsoft.com/wiki/contents/articles/864.configure-static-rpc-ports-on-an-exchange-2010-client-access-server.aspx
Thanks in advance.
/* Server Support Specialist */

All the servers behind the load balancer must be the same.
You can change the stand alone MBX server's RCA port as that traffic is not load balanced.
Changing Exchange is straight forward, just be careful to enter the registry keys correctly and then check AB and RCA is listening on the new static ports after you restart the services.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Rhoderick,
Many thanks for the suggestion. My goal here is to minimize any impact / email service downtime to the user while configuring the static ports.
1. Do I have to dissolve the Windows NLB cluster after the static port configuration on both HT-CAS servers or can I still keep the NLB cluster?
2. "All the servers behind the load balancer must be the same." Do you mean do I have to do the static RPC port the same day for all server set ?
/* Server Support Specialist */

Exchange 2007 to Exchange 2010 Cross Forest

Hi
We have a scenario where we have an Exchange 2007 organization (Org A - Source) and a separate Exchange 2010 organization (Org B - Target). Both the organizations (AD Forests) have two way trusts between them.
We want to have our Exchange 2007 users have their mailboxes hosted on Exchange 2010 organization. Meaning that the user (AD) accounts of Org A will remain in Forest A but there mailboxes will be available on Exchange 2010 servers in Org B. So we don’t need
a user / group migration stuff here and mailbox data on Exchange 2007 servers is also not critical (not required to be migrated) so we will be creating new disabled accounts and mailboxes in Org B for each user in Org A and connect the mailboxes. There will
be a brief period of co-existence between two Orgs (to enable mail-flow) until all the users have their mailboxes active in Org B. Need to figure out a way to achieve this.
We are planning to follow the steps below:
Setup name resolution between the forests (although basic connectivity is there and we can ping servers in one forest using IP Addresses from other forest) –
Please suggest if this is necessary or we can get away with it?
Setup SMTP namespace sharing for Exchange 2007 SMTP Domain name
Add Exchange 2007 SMTP domain as authoritative domain to E2K10
Create EAP for new SMTP Domain
SMTP Connector Creation for Direct E-mail Routing (Co-exist) Between Forests
Create disabled Mail Enabled (not Mailbox Enabled) User or Mail Enabled Contact in Org B.
Can we use Prepare-MoveRequest.ps1 script to create these?
Once a mail enabled user / contact is created in Org B for all the users, change incoming traffic from Internet for Org A SMTP domain to hit HT server in Org B
Make changes to Exchange 2010 certificate and install new certificate
Select a batch of users every day, create new mailbox for them using scripts in Org B and delete the corresponding contact in Org B
Can someone please confirm if this is correct and point out something I am missing?
Is there any other way to achieve the same goal?
Thanks
Taranjeet Singh
zamn

Hi Everyone
Thanks for the inputs so far. I need to confirm some steps to establish direct email flow unless all the mailboxes are created in target organization, can somebody have a look at the steps below and confirm if they are correct or add something that
I missed here:
Setup source Exchange organization:
a) Add unique SMTP domain for source organization, like @source.local. This domain will be added to all mail enabled objects in this organization and will be used for internal routing only
     i) Add to Accepted Domains list
     ii) Create EAP to add domain to existing objects
b) Use manual means to stamp SMTP domain to objects in source organization on objects that don’t have EmailAddressPolicyEnabled set to False
c) Create Send Connector to target forest. The target domain should also have a unique e-mail address, like @target.company.com (in our case 19 SMTP domains including JUBL.COM)
     i) Include the valid SMTP domains and the unique one for internal routing
         (source.local)
     ii) Point to a smart host in the target forest
d) Set existing SMTP domain (JubilantRetail.com) as “Internal Relay Domain”. The target Exchange org will be authoritative for this domain
Setup target Exchange organization
a) Create Send Connector to unique SMTP domain in source forest. Includes shared name space (source.local) and @JubilantRetail.com
b) Set Default receiver connector, being used by source forest, to allow anonymous connections
c) Add shared SMTP domain (source.local) to Accepted Domains list as authoritative
d) Create EAPs to replicate the SMTP domains (e:g JubilantRetail.com and source.local) in the source environment
Thanks
Taranjeet Singh
zamn

Exchange 2010 - Decommissioning Exchange 2007 Coexistence and Removal of Public Folders

We are about to decommission exchange 2007, currently in coexistence with Exchange 2010.
We do not want to use ANY public folders in exchange 2010 going forward. Will do this after decom of 2007:
http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
I see this in the outlook connection status in outlook:
I have changed all Exchange 2010 mailbox databases to use a temporary 2010 public folders db named "public1" so that it is not communicating with the 2007 mailbox virtual server. However, the exact same connection status appears after I changed
the 2010 mailbox DBs to use a 2010 public folder db instead of the old 2007.
Question is, is it safe to decom the 2007 environment now? Is it normal to still have a connection to 2007 in "connection status" in outlook when the users mailbox is on a 2010 mailbox db? Is this connection related to public folders or something
else that needs modified before decom?
Thanks,
Josh

So, that wasn't the answer. I switched the Public folder DB on each mailbox database to a exchange 2010 server, PF DB, but hadn't actually moved any data from 2007 to 2010.
I didnt realize this is needed when we don't use public folders except for free-busy, default, etc.
What is the correct way to move the default public folders to a 2010 public folder?
I'm using the below URL as a template to migrate this info to a 2010 PF db.
https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
"The user Public Folders then need to be replicated to the Exchange 2010 Public Folder database as well. It is possible to manually configure
all Public Folders with a new replication partner, but it’s better to use PowerShell scripts that Microsoft delivers with Exchange Server 2010. Open the Exchange Management Shell and navigate to the Scripts directory
by entering the CD $ExScripts command,
and execute the following script:
AddReplicaToPFRecursive.ps1 -Server 2007MBX -TopPublicFolder "\"
-ServerToAdd 2010MBX"
My question is, do I have to do this "3rd step" since I don't think i have any custom "user public folders". Is this the user's free busy that I have to migrate, or is this author referring to custom PF db info?
Do I have to have public folders for free-busy and default exchange services at all in 2010?

Error upgrading form exchange 2010 to exchange 2013

Hello,
I have Exchange 2010 sp3 running on win server 2012 R2 sp1 standanrd. I would like to upgrade to exchange 2013 and I read that installation of exchange 2013 is coexistent with exchange 2010 already installed. But When I try to install exchange 2013 I keep
getting this error :"Exchange server is in an inconsistent state. Only disaster recovery mode is available. Please use Setup /m:RecoverServer to recover this Exchange server." But after closing set up the server is still running
fine.

Hi,
Based on my research, the issue can occur when the Exchange server object already exists within Active Directory.
Thus, I’d like to confirm the following information:
1. Does your new Exchange 2013 server have the same server name with the previous one?
2. Have you change your Exchange 2010 server name to legacy.domain.com?
Here is a similar thread you can refer to:
http://social.technet.microsoft.com/Forums/exchange/en-US/20bab6f7-56e6-49b9-94df-48707fb915f7/installation-errorfresh-install-on-a-fresh-clean-server-2012?forum=exchangesvrgeneral
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

TMG 2010 publishing Exchange 2010 OWA cannot change password if user must change password at first logon is set

Hi,
I have an odd issue whereby if I set "user must change password" on an AD account, the end user cannot logon, they're simply taken back to the OWA login page as if their password is incorrect.
My setup is as follows:
outer TMG -- uses a listener for email.contoso.com and is configured for no authentication.This uses a publishing rule to publish the inner TMG server. This server is not a domain member.
inner TMG - uses a listener for email.contoso.com and is configured for NLTM\kerberos negotiation with forms authentication (Windows Active Directory). This server is a domain member and use a publishing rule to publish the internal CAS. Allow users to change
password is selected in the publishing rules.
Exchange 2010 SP1 - uses integrated windows and basic authentication. Has the appropriate registry key configured to allow users to change their AD password on first logon.
I've registered an snp for "http/email.contoso.com mailserver-dc1", all SSL certificates being used are valid and my configuration used to allow users to login and change their password with "user must change password on first login"
set in AD.
If I launch a web browser on an internal server and point it to email.contoso.com I'm immediately presented with a generic Windows authentication request (similar to what's seen in ADFS) rather than the standard OWA page. No matter what I do, I cannot login
and change my password using the correct URL. However if I point my browser at
http://192.168.4.10/owa I'm prompted to login and I can change my password using the sam credentials.
The only recent changes made are:
- Disabling SSL 3.0 and enabling TLS (http://www.isaserver.org/articles-tutorials/configuration-security/improving-ssl-security-forefront-threat-management-gateway-tmg-2010-published-web-sites.html)
- Replacing the TMG listener certificates so that they now use SHA2 rather than SHA2 (certificates are trusted on each TMG server)
Looking on the outer TMG and the DC logs I can see schannel errors which I believe are related to the problem. TMG monitoring also shows "Failed connection attempt: 1907 The user'spassword must be changed before logging on for the first time"
I've checked that my inner TMG and DC are using the same certificate for server authentication and gone through this guide:
http://blogs.technet.com/b/keithab/archive/2012/02/29/setting-up-and-troubleshooting-ldaps-authentication-in-forefront-tmg-2010.aspx
If I try to use ldp.exe on the inner TMG, I get the error in the pic below
Thanks
IT Support/Everything

Hi,
You could try to analyze the TMG tracing and try the troubleshoot steps in the blog below.
TMG 2010 – FBA, troubleshooting the change password feature
http://blogs.technet.com/b/isablog/archive/2012/05/07/tmg-2010-fba-troubleshooting-the-change-password-feature.aspx
Best Regards,
Joyce

Exchange 2010-2013 Migration - Outlook Client gets "Your administrator has made a change..."

So we're migrating from an Exchange 2010 environment to Exchange 2013. We use a single namespace ("exchange.contoso.com") for both internal and external clients.
In testing, we have taken a few machines running outlook 2013 and 2010, and edited their hosts file such that "exchange.contoso.com" points toward the new exchange 2013 environment, rather than the 2010 environment for our users. So far so good,
they can connect, no issues.
However, when we move a mailbox to the 2013 environment, the outlook client comes back with "Your Exchange Administrator has made a change which requires you to restart outlook". This error affects both Outlook 2013 and 2010. We do have public
folders in place in exchange 2010, but we have not yet migrated them to 2013 (because the user's still are on 2010).
Repairing the profile is no help, and recreating the profile does not work either. Any thoughts?

Hi ,'
On you first post you have said you have put host file entries for the namespace "exchange.contoso.com"
in few of the client machines .
what about for autodiscover namespace did you have put any host entries for that .If not please put that
too in the host file of the client machines and then check by moving anyone of the mailbox from exchange 2010 to exchange 2013 .
Same time please check this blog especially on the end of the page .
http://blogs.msdn.com/b/aljackie/archive/2013/11/14/outlook-and-rpc-end-point-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook.aspx
Regards
S.Nithyanandham
Thanks S.Nithyanandham

The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook in Exchange 2010.

Hi,
We have 2 Exchange 2010 servers with multiple roles installed ,also we have setup cas array on the same with help of Kemp load balancer. Both have 1 public folder on each node.
There are few accounts(including mine) those are recently migrated from Exchange 2003 to Exchange 2010 and they are getting intermittantly an error pop "The Microsoft Exchange administrator has made a change that requires you quit and restart
Outlook"
this generally happens when i switch the network for my laptop but not every time 2-3 times in a week.
i already gone through this link but didn't get any solution. Any help is appreciated.
http://blogs.technet.com/b/aljackie/archive/2013/11/14/outlook-rpc-end-point-and-pf-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook.aspx
Amit Rawat | MCITP - Exchange 2007/2010| CCNA |MCSE- 2003| Lync 2010|http://blog.amitrawat.net

Hi,
I recommend you check if any Public Folder on one member of a CAS array.
If yes, it will cause the issue.
I had encountered a similar issue.
The Problem exists when an Outlook client connects into a CAS array initial if
it connects to the CAS array member that contains the PF role, then Outlook
Converges all connections and displays both the Public and Private logons as one
single conneciton to Mail.company.com (the CAS array name) When the Clients IP
address changes, and it Re-connects, if it gets connected to a CAS array member
that does not have the PF server, then we get an ECwrong server Response from
Exchange, Outlook in it's reconnect logic Cannot follow the Redirection Result
that contains the correct PF server name, and displays the Error "the Admin has
made a change that requires you restart Outlook"
Finally, move PF to separate server as a workaround.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
Thanks !
As i started this question saying i have already read these things . If this is the case i am wonder why microsoft didn't release a technet article where it must discussed about CAS array and Public folder confliction.
However, you said
"if it gets connected to a CAS array member
that does not have the PF server, then we get an ECwrong server Response from Exchange, "
I do have PF on both node then why this pop up.. i do understand if only one node has PF and new connection intiated by outlook connecting to other node which doesn't have PF then it will redirect to the node having PF and while doing so there is
the message.
FYI..
I hve two node server having CAS array and DAG configured on it. keep one thing in mind i am using kemp load balancer for CAS array.
I will appreciate all your help if you elaborate in depth.
Amit Rawat | MCITP - Exchange 2007/2010| CCNA |MCSE- 2003| Lync 2010|http://blog.amitrawat.net

Cannot save any changes - Microsoft Forefront 2010 for exchange is unable to perform the requested function

HI, I have Forefront 2010 for Exchange installed for an Exchange 2007 SP2 running on Windows 2003 x64 SP2. Exchange has all roles installed on the same server.
When I try to save any change on Forefront I got the following message:
Microsoft Forefront 2010 for Exchange is unable to perform the requested function. This may be because Forefront services are unavailable. Ensure that all Microsoft Forefront services are running and that WindowsPower Shell is functional
Well, our FF services are running and PowerShell is functional. I checked some forums and found some problems when there is entries in the IP Allow / Block lists in Exchange UI. I removed those entries but problem remains.
Any ideas would be appreciated.
Xavier Villafuerte

In my case, I was able to work around this issue by using PowerShell directly. For example, to run an on-demand scan for all mailboxes, this worked:
#open EMS
$aliases = (get-mailbox -result unlimited).alias
Add-PsSnapin FSSPSSnapin
set-FseOnDemandScan -MailboxList $aliases
Start-FseOnDemandScan -EnableVirusScan $true
Windows 2008 R2 SP1
Exchange 2010 SP3, RU9
PowerShell 4.0 present on the machine (though EMS runs PS 2.0)
Forefront PowerShell cmdlets:
https://technet.microsoft.com/en-us/library/cc482986.aspx
Mike Crowley | MVP
My Blog --
Baseline Technologies

Can't change RUS in interop environment Exchange 2003/Exchange 2010

Hello!
We have interop environment with Exchange 2003 and Exchange 2010 Servers. We have many Exchange 2010 servers, and not so many days ago had a lot of exchange 2003 servers. So we moved all mailboxes from Exchange 2003 servers and started to remove exchange
2003 servers after that. Now it's all come to 2 Exchange 2003 servers. So what we have now:
Server 2003-A has replica of some Public folders, master in Routing group and a lot of other systems still use this server to send messages directly through SMTP.
Server 2003-B only assigned as exchange server in Recipient Update Service (RUS).
I wanted to change RUS properties from Server 2003-B to Server 2003-A and leave it as the last one, but it's impossible. I can't choose another server, can't even pick "Computers" in Objects during search. Also I can't create new RUS for the same
reasons.
Is there any possibility to change RUS from Server 2003-B to Server 2003-A or no at all?

What if you click on the Advanced Tab and then Find Now...don't you find Server
2003-A when you do?
Martina Miskovic

Change name of AD site hosting Exchange 2010 server

We want to change the name of an AD site which currently hosts an Exchange 2010 server. Is this possible? Are there specific steps we need to follow to keep Exchange up & running?
Thanks

Hi Sneaky,
As Vincez mentioned, it is possible to change the name of the AD site with Exchange 2010 is hosted,you just need to restart the AD topology service after changing.
You can also refer to the following threads:
Changing AD Site name in Exchange 2010
SiteName is hard-coded
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Exchange 2010 AD Site Changes

We have 2 Exchange 2010 servers. Hub Transport/Mailbox server is at our local office. CAS server is at a remote data center. It is all one AD site and all domain controller/DNS servers are in the local office.
We are now adding a domain controller with DNS to the remote data center with the CAS. This new domain controller will also be the DC for the new AD site that will represent the data center location.
What needs to be done to make sure adding a new AD site doesn't negatively affect Exchange?
IP addresses are not changing. Is there any problem with the CAS being in a different AD site than the mailbox/hub transport server?

Hi ,
Thank you for your question.
What needs to be done to make sure adding a new AD site doesn't negatively affect Exchange?
What is a new AD site? A new sub-domain or a new BDC?
If it is a sub-domain, by my understanding, it is important for us to make sure the DNS property of IP address point to local AD on Exchange CAS server. then Exchange CAS server will not communicate with new AD on remote site. If it is a BDC, we could add
the IP into the property of “alternate DNS server” on Exchange CAS server. if i have misunderstanding, please be free to let me know.
IP addresses are not changing. Is there any problem with the CAS being in a different AD site than the mailbox/hub transport server?
A: yes, we could do that, we just make sure all subnets could communicate without ant problem.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Exchange 2010 users cant change password in OWA when Cas server is Exchange 2013 cu3

Running Exchange 2010 and 2013 in mixed mode. users who is still on Exchange 2010 cant change password in OWA. It worked when it was clean Exchange 2010 installation. Password change is working for users migrated to 2013
LS

Hi
Please follow the below blog which will help you in solving this issue
http://technet.microsoft.com/en-us/library/bb684904.aspx
Note: Be careful while modifying the registry settings.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish

Exchange 2010 Sp3 AD Schema Changes

I am looking for a listing of Active Directory Schema Updates that Exchange 2010 SP3 makes. We are currently on SP1, and we will most likely end up at SP2 RU6, but if the changes are minimal to SP3, we may go ahead and extend the AD Schema to SP3 just
so we don't need to involve the AD Team again. Does anyone know where to find a complete list of AD Schema updates from Exchange 2010 SP3? I've checked:
Exchange Server changes to the Active Directory Schema webpage, but it does not have SP3, only Sp2.
Any help would be GREATLY appreciated.
Thanks!
Mark Currans

Please ensure that SP3 has been tested and validated by all the 3rd party apps and services in your org. You do not want to install it to find out that vendor X will no longer support you.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Odd change in exchange 2010.

Similar Messages

Maybe you are looking for