Exchange:NDR due to X500 address change Error:The email address you entered couldn’t be found

NDR with junk email address It is not uncommon that in Microsoft Exchange environment some times a user to whom uptill yesterday everyone was able to send the email, suddenly all the internal users start to get an NDR (Non Delivery Report) with a junk email address when trying to send email to the person. And If you are unlucky as me then that guy would always be some VVIP of the company 🙂 . we receive complain like some users are not able to send email to a particular user, and they get NDR as below: You might notice the user name is hyper linked and when you resolve it by pressing (Ctrl+Click) , new memo opens with junk email id. Example: Delivery has failed to these recipients or groups: Harish Chadda The email address you entered couldn’t be found. Please check the recipient’s email address and try to resend the message. If the problem continues, please contact your helpdesk. Diagnostic information for administrators: Generating server: CPUNEXCHOTZP14.xyx.itm IMCEAEX-_o=One+20Xyx+20Messaging_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23 SPDLT+29_cn=Recipients_cn=2b52ff2434754ff6b3ea72e2f0465c42-Vij@xyx.com Remote Server returned ‘550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found’ Cause: If you go behind the scene, you will find the tech team is not completely innocent in the case, some thing weird happened last night the original mailbox was deleted for the user and a new mailbox was created with the same SMTP address or something similar happened. This issue occurs because the value for the LegacyExchangeDN attribute changed. The auto-complete cache in Microsoft Outlook and in Microsoft Outlook Web App (OWA) uses the value of the LegacyExchangeDN attribute to route email messages internally. If the value changes, the delivery of email messages may fail with...

How to setup Office 365 Outlook Manually

Follow me Undoubtedly Autodiscover works flawlessly with Office 365, still there could be few times when you need to setup some odd outlook client manually. Its quite difficult to know the exchange server name and other details for Manual config from the office Admin console or user’s Outlook web access.  The following article explains how to setup outlook manually with Office 365 Manual configuration of MS Outlook for Office 365 account: To get started we need to get the ExchangeGuid for the user account that we need to configure manually Login and Connect to Windows Azure power shell, You can use following article for step by step instruction about how to connect to Windows Azure Power Shell How to Connect to Office 365 via PowerShell Run following command at Office 365 shell to extract ExchangeGuid PS C:\O365> Get-Mailbox -Identity <abc@xyz.com> | ft name, exchangeguid Steps to configure Office 365 MS Outlook account: 1 Goto Control Panel->Mail, start creating a new email profile 3 . Type in server as “ExchangeGuid” with “@SMTPDomain.com” as suffix. Here SMTPDomain is going to be replaced by the UserPrincipalName domain of the user account Click on More Settings and configure each tab under it as described below Hope this article helps you solve the issue at hand, We can also help you do complete office 365 Migrations, For quotes please visit out website here Follow...
Outlook 2010/2007 authentication prompts with Office 365

Outlook 2010/2007 authentication prompts with Office 365

Follow me Microsoft outlook 2007 and outlook 2010 often keep prompting for authentication while configuring Office 365 email profile.It’s a very common issue , outlook 2007 is a very old client and its only supported post sp2 with office 365 however Outlook 2010 is fully supported. After through analysis we have found that Office 365 requires “Anonymous Authentication” in Logon network security of tab “Security” and this option is actully missing on Outlook when you face such issues.   Thankfully the solution to the issue is quite simple Solution 1: Upgrade to Outlook 2013 : Its the latest and most compatible version with Office 365   Solution 2: If you want to use Outlook 2007 then make sure you have SP2 installed on it and then install the following two updates, this should resolve the issue KB2596598: (http://www.microsoft.com/en-in/download/confirmation.aspx?id=30311)  KB2687404: (http://www.microsoft.com/en-us/download/confirmation.aspx?id=35718)   For using Outlook 2010, Install the following two updates to get it working with Office 365 KB2687623 : http://www.microsoft.com/en-in/download/details.aspx?id=35702  KB2553248: http://www.microsoft.com/en-in/download/details.aspx?id=29361     Hope it resolves your issue, else reach out to us for help here Follow me  ...

Http Error 503 with Office 365 ADFS sign in page

Follow me Issue description: We had a working ADFS server farm serving production office 365 single sign on environment for one of our clients. Suddently users reported that they are at times getting  Office 365 login was given error “HTTP Error 503” while redirecting to ADFS page. Before that there were some issues with authentication of some outlook and Mobil clients as well however it was again sporadic. Environment: We had a Two windows 2008 R2 server installed with the latest version of  ADFS from O365 behind a hardware Load Balancer and along with that the usual Active directory domain infrastructure with over 20 domain controllers. It was quite evident that the issue is with ADFS server as, first there were no other issues reported inside the orgnization and second we were seeing Http Error 503 every now and then, which was definitely atleast starting from ADFS server. Hence, To Begin troubleshooting the issue, its best to try and isolate the cause by individually trying to sign into both the server internally, the one which gives the issue is causing the problem.  like this https://<ADFS server 1>/adfs/ls/IdpInitiatedSignon.aspx https:// <ADFS server 2>/adfs/ls/IdpInitiatedSignon.aspx If one of the server gives error like “HTTP Error 503”,problem with that server. As an immidiate solution we can try to remove it from the load balancer by the time we resolve the issue, so that external users do not run into this server causing the error   We started to look around to find the issue and not too later we found that ADFSAppPool was down on one of the server, started it to resolve the issue...

Dirsync in Multi Forest Multi domain environment

I recently got an opportunity to setup directory sync with password sync for a big organization.  During this setup I realised that alot changes when the scope increased from 200 users to 50000 users. I faced multiple challenges and learnt alot, to make it simple for other, I am publishing my learning here. hope it helps   Office 365 Directory Sync with password Sync: Are you considering password sync with directory sync for your big multi-domain environment, you may face following issues: Issues with configuring Directory Sync: The user name or password is incorrect Unknown error (0x80005000) Directory Sync tries to reach domain controllers of all the child domains in the environment to give permission to MSOl user, and if somehow DirSyn is not able to reach some domain controller or the domain controller it is reaching is not responding properly. You may face any of the above error, then you need to find out which domain controller is creating problem, net mon can help you with that. Start Netmon trace and then run DireSync, expend the configuration.exe section, the last entry in this section would tell, you DirSync could not proceed with which DC, if you expend it, you would get information about the reason.   The above example shows that the child Domain controller is  not able to authenticate the Enterprise admin ID that is being used for configuring Directory Sync, it seems that the DC is  not able to communicate with Root domain controller. In this way you can find out, which domain controller has got problem, you can fix it. If you have multiple domain...