On-premise Exchange 2010 SMTP Relay to O365 mailboxes does not resolve Display Name

Dear All,
We have SMTP relay receive connector in our on-premise Exchange 2010 server that accepts emails from anonymous users.
The Externally Secured check box is checked. Display Name of the sender in Emails to mailboxes in on-premise is resolved correctly.
But the display name of the sender in the same email to mailboxes which are migrated to O365 is not getting resolved.
Please let me know if anyone has seen this issue. Some of our mailboxes are in O365 and some are in On-premise server.
Thanks
Fred

Do you have a hybrid configuration set up, and if not, is there any particular reason?
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

Exchange 2010 SP3 RU7 - additionals mailboxes does not refresh automatically

Hello
On Exchange 2010 SP3 RU7 , my additionals mailboxes does not refresh automatically (Outlook 2010 up-to-date).
i need to perform "send/receive" and "update the folder" to get the mail.
Primary mailbox is running correctly and new mails are displayed .
Thanks

Hi,
Based on the description, you added additional mailboxes from Outlook, but messges sent to these additional mailboxes didn't show until you tried the option "update the folder".
How many additional mailboxes did you add?
Did this issue affect all users?
If possible, please remove these additional mailboxes and then re-add them. I recommend you add one additional mailbox first to check if the issue occurs. Then you can add another additional mailbox to check result.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2010 disconnect AD user from mailbox and reconnect the mailbox to a new copy of the same user with a different username

How can i get the following done:
Exchange 2010 disconnect AD user from mailbox and reconnect the mailbox to a new copy of the same user with a different username?
i nmust do this for 16 users TODAY, SO PLEASE HELP ME OUT HERE.
Thanks in advance!!
kind regards,
Rene Veldman
System Administrator Teidem bv, The Netherlands.

Rene,
Why are you not changing the username of the existing account, instead of deleting the existing one and creating a new one?
If you truly need to delete and create new, you can save the GUID for the mailbox (Get-MailboxStatistics <mailbox alias> | Fl MailboxGuid), mail disable the existing account (Disable-Mailbox <mailbox alias>
will work), clean the mailbox database it was hosted on (Clean-MailboxDatabase
<database name>), then create your new account and recover the existing mailbox to that new account (Connect-Mailbox -Identity <Guid from before> -Database <Database name> -User <SAM account name of new account> -Alias
<what you wish to set the alias to>). In PowerShell, for all steps, you would do the following:
$MbxAlias = <mailbox alias>
$NewMbxAcct = <SAM Account Name for new account>
$NewMbxAlias = <new alias for mailbox>
$DomCtrl = (dir env:\LOGONSERVER).Value.Substring(2)
$MbxGuid = (Get-MailboxStatistics $MbxAlias -DomainController $DomCtrl).MailboxGuid
$MbxDb = (Get-Mailbox $MbxAlias -DomainController $DomCtrl).Database
Disable-Mailbox $MbxAlias
Clean-MailboxDatabase $MbxDb
Connect-Mailbox -Identity $MbxGuid -Database $MbxDb -User $NewMbxAcct -Alias $NewMbxAlias -DomainController $DomCtrl
You will need to supply the information in bold in the above commands, and you will need to create the new account before you run the above commands. I include direct use of a specific domain controller so you won't need to worry about replication.
If you are changing the account from one domain to another, this will not help, and you will need to wait for replication throughout the process, running the commands individually.

Exchange 2010 - The name on the security certificate is invalid or does not match the name of the site

Scenario - Two Domains in different forests in production
Domain ABC.com - Contains Exchange Server 2010 + Windows 2008 R2 AD Domain controllers
Domain XYZ.com - Windows 2008 R2 Domain controllers + Contains all users + Desktop compuer accounts.
User logs in to the domain XYZ.com from a desktop and he configures outlook using the user ID in domain ABC.com.
When he opens Outlook it is getting connected and he gets an error message pop -up saying 'The name on the security
certificate is invalid or does not match the name of the site'
I am using an external certificate from Thawte for autodiscover.ABC.com & webmail.ABC.com
I read about one solution provided in MS KB article - http://support.microsoft.com/kb/2772058
But in my scenarion there are two domain involved. Pls guide how to clear this.

Hi,
How about logon [email protected] on ABC domain via OWA?
If OWA works well, it seems and issue on the Autodiscover side.
Please run "Test E-mail AutoConfiguration" on Outlook to check whether this issue caused by Certificate Mismatch.
1.
Firstly make sure how many host name in your certificate the certificate. Run “Get-ExchangeCertificate | select certificatedomain”.
2.
Secondly, check the web services URLs which Outlook are trying to connect to. Run “Test Email AutoConfiguration”.
3.
In this scenario, you need to check the host name for the following services:
Autodiscover, EWS, OAB, ECP, UM
4.
If any of the urls above does not match the one in the certificate, refer to the following article to change it via EMS:
http://support.microsoft.com/kb/940726
More details to see following FAQ on "Checklist for Exchange Certificate issues":
http://social.technet.microsoft.com/Forums/en-US/fa78799b-5c55-4c71-973b-0e186612ff6f/checklist-for-exchange-certificate-issues?forum=exchangesvrgeneral
Thanks
Mavis Huang
TechNet Community Support

The name on the security certificate is invalid or does not match the name of the site exchange 2010

We did an update to SP1 to SP3 for Exchange 2010 over the weekend and now I am seeing the following errors.
"The name on the security certificate is invalid or does not match the name of the site"
Any ideas why an update would effect this. I have looked at the names and everything seems to match up.

Hi,
Does the issue happen to all users? If it is, please run the following command to check your certificate configuration:
Get-ExchangeCertificate | fl
Generally, the certificate mismatch issue is caused by the name in URLs doesn't match the certificate names with IIS service. Please make sure all URLs that used to connect Exchange from internal and external should match the certificate names with proper
services.
http://support.microsoft.com/kb/940726
Best Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 w/Outlook 2013 "The name of the security certificate is invalid or does not match the name of the site"

I've completed an upgrade from Exchange 2003 to Exchange 2013 and I have one last SSL message that I can't get rid of. I've installed a 3rd party cert that is working great for webmail and cell phone access but for some reason the Outlook 2010/2013
clients get prompted for a security warning. I just implemented the SSL cert yesterday and I've noticed that new installs of Outlook seem to work just fine. My Outlook 2013 client doesn't prompt me with the message but I have other users who are
still getting the "The name of the security certificate is invalid or does not match the name of the site" error. The domain on the cert error show up as server.mydomain.local. I've gone through all the virtual directories and pointed
all of my internal and external URL's to https://mail.mydomain.com. This made one of the two warnings go away but not the second. I've dug around on google and gone through everything I could find here and as far as I can tell my internal
and external url's are configured properly and I can't figure out where this error is originating from. Any ideas on where I should look outside of the virtual directories?
I'm including a good link I found that contains all of the virtual directories I updated. I've checked them through both CLI and GUI and everything looks good.
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
http://jaworskiblog.com/2013/04/13/setting-internal-and-external-urls-in-exchange-2013/

Hi,
When the Outlook connect to Exchange 2013/Exchange 2010, the client would connect to Autodiscover service to retrieve Exchange service automatically from server side. This feature is not available in Exchange 2003 Outlook profile.
Generally, when mailbox is moved to Exchange 2013, the Outlook would connect to server to automatically update these information. It needs time to detect and update the changes in server side. I suggest we can do the following setting For autodiscover service:
Get-ClientAccessServer | Set-ClientAccessServer –AutodiscoverServiceInternalUri https://mail.mydomain.com/autodiscover/autodiscover.xml
Please restart IIS service by running IISReset in a Command Prompt window after all configuraions.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 - The name of the security certificate is invalid or does not match the name of the site

Hi,
I know this question has been asked a ton of times, but I haven't found any instance of this question asked for exchange 2013. Yes, I've seen Exchange 2010, Exchange 2007, but not Exchange 2013. The symptoms are all similar. Here is a description:
1 Exchange 2013 server, all roles installed.
External domain name: associates.com
Internal AD domain name: associates.local
Client installed a third party SSL certificate, but did not purchase a SAN or UC certificate, so there is one namespace on the SSL cert, and that represents the external OWA name: mail.associates.com
Now, when internal OUtlook 2010 clients start, they get the "The name of the security certificate is invalid or does not match the name of the site."
I'm just wondering if http://support.microsoft.com/kb/940726 still applies to Exchange 2013 to fix this issue. Does this article apply to Exchange 2013? If so, I will follow the above
article. If not, please direct me to any articles for Exchange 2013 that addresses this.
the autodiscoverserviceuri points to:
https://netbiosnameofmailserver.associates.local/Autodiscover/Autodiscover.xml
Thanks!
A

Yes, the http://support.microsoft.com/kb/940726 still applies to Exchange2013.
As per my understanding on this post;
- Poster's Exchange2013 has no SAN certificate.. (usually used for local address like; NETBIOS.Domain.lan). Be reminded that SSL providers will no longer accepts .LAN or .LOCAL in very near future.
- By default it uses local url for EWS, Autodiscover, etc.. (if you don't have SAN certificate installed in your CAS server, you would see the certi warning)
Anyway, I just want to share my case after applying the said work around long time ago (maybe some of you might encounter it as well): my Outlook still showed the certificate warning (I was just keep clicking the YES button).. I was wondering
that time what was wrong with my virtual directory settings.. until I decided to click "NO" for an answer to that certificate warning message, then voila! it didn't bug me anymore. Oh by the way, the certificate warning usually give you a hint
what triggers it like; "autodiscover.Domain.lan" on the first line of message, but in my case it just "NETBIOS.Domain.lan" (didn't make any sense, did it?).. Well, unfortunately I didn't have the chance to figure out what triggered that event..

Exchange 2013/2007 coexistence: The Name on the Security Certificate is Invalid or Does Not Match the Name of the Site.

In the midst of Exchange 2013/2007 coexistence configuration.
Currently:
Exchange 2007:
2 CAS\HUB
1 Mailbox server
Exchange 2013 (2 sites):
LA:
1 CAS
2 MBX servers
MKE:
1 CAS
2 MBX servers.
We purchased a certificate from Digicert and added every SAN name we could think of including "legacy.companyname.com", just to be sure. Added certificate to Exchange 2013 CAS servers and 2007 CAS\HUB boxes. Configured virtual directories on Exchange
2013 MKE-CAS01 but not on Exchange 2013 LA-CAS01. Configured virtual directories to on Exchange 2007 CAS\HUB to point to "legacy.companyname.com".
Mailboxes have not been moved yet. I just wanted to get the coexistence between Exchange 2013/2007 up first but some users (not all) receiving
"The name of the security certificate is invalid or does not match the name of the site" for
"LEGACY.COMPANYNAME.COM". I remember configuring the AUTODISCOVER virtual directory for Exchange 2007. Any ideas? Thank you.

Hi,
Please make sure that the certificate with "legacy.companyname.com" name is enabled for IIS service. We can check it by running the following command in Exchange server 2007:
Get-ExchangeCertificate | FL
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2010 SMTP Connector

Hello,
We are having an issue with our exchange 2010 hub transport server and its external SMTP connector. We use an external DNS CNAME as the smart host, this works on 2003 (As a FQDN of the host, not a smart host) but we receive DNS query failures on 2010.
We can successfully route to the relay if we use an A record but an CNAME doesn't seem to work, is this as per design? Can we only use A records or IPs?
Thanks

You mean Send Connector, right? (SMTP Connector is an Exchange 2000 or 2003 thing.)
Are you sure you entered the CNAME correctly in the connector properties? Can you ping the smart host or establish a telnet session over port 25?
I've never heard of that issue before. You might consider opening a ticket with Microsoft Support.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Close Exchange 2010 Open Relay

Hello,
I am experimenting and trying to setup an exchange 2010 server to use with my personal domain. Let's make the following assumptions:
Domain: domain.com
Mail Server address: mail.domain.com
My mail server sends emails using my ISP's SMTP server (suppose smtp.isp.com) as a smart host.
My problem is that my exchange server seems to work like an open relay. If I use telnet to connect to mail.domain.com:25, I can send email from any to any address. What I'd like to do is to require some kind of authentication so only users that have mailboxes
on my server can send email using mail.domain.com's SMTP.
I believe the reason this happens is because I have enabled Anonymous users in the "Client" and "Default" Receive connectors. If I disable the Anonymous users though, I cannot receive emails from the internet. For example, a @gmail user
won't be able to send an email to a user in my domain.
How could I achieve my aim to restrict the SMTP relay to authenticated users but still be able to receive emails from the internet?

Hi,
As far as I know, there are two relay type: authenticated relaying and anonymous or open relaying. And I recommend you use authenticated relaying which allows your internal users to send mail to domains outside of your Exchange organization,
but requires authentication before the mail is sent.
http://blogs.technet.com/b/exchange/archive/2006/12/28/3397620.aspx
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010 Emails relay to different server

Hi Guys
We are having some trouble in emails. We have hosted exchange for customer. The same Exchange Server(2010) hosts emails for company as well.
We migrate the email and accounts to hosted exchange from other mail server(exchange,google etc)
I need to migrate a new customer to hosted exchange but before that I need to migrate few accounts for testing. The issues I need to address is that as soon as I will migrate one mailbox to our hosted exchange, any emails sent to that users from our company
email address will be routed internally.
For Example
There is a customer with email : [email protected] and is hosted within their own exchange(ExchangeServe1)
We have a Hosted Exchange(ExchangeServer2) server which hosts our emails and we offer email solution to customers.
When I will migrate [email protected] into our Exchange server(Exchange Server2) and if after migration I want to send some email from my company email address(Exchange Server2) exchange will do internal routing and forward email to [email protected] which is
in the same exchange server(ExchangeServer2).
But I want exchange to forward email to existing customer exchange server(ExchangeServer1).
We are not changing MX record yet so incoming emails from anywhere else would be fine except when we will send emails from our company emails addresses to abc.com domain.
So my question, How do I configure our exchange that it does not send emails to an organization configured in the same exchange server.

you can do this manually with a contact on the old exchange server and a transport rule to forward a copy to the new server you will have to come up with a unique name for the new server at least on a temporary basis maybe a sub domain.
you could also remove the allowed domain name of this customer from your server this is how exchange determined delivery.

Appointments from Exchange 2010 show as Mail in Mailbox

I have a very frustrating issue with a single user on one of our post offices. For reasons unknown appointments sent to the user from Exchange 2010 appear as mail items instead of appointments within the mailbox. Other users on the same post office do not get the same issue. I have tried resetting the user's views and a full client reset via maintenance. I have set the user's client settings to be the same as another user who does not get the issue without any luck either. Maintenance checks on the account does not flag any errors. I'm pretty certain I'm missing something very simple, but alas I can not think what.
Software wise we're running client 8.0.1 on post office agent version 8.0.2. We seem to get the same results regardless of the Client version of outlook, (we have tried the web version and 2003 and 2010 of the client). Anything else I could try would be greatly appreciated.
Kind Regards
Rob

In article <[email protected]>, Rob naylor
wrote:
> Software wise we're running client 8.0.1 on post office agent version
> 8.0.2.
>
How about updating those as they are a bit old.
Try looking at that user's account from another machine and from
WebAccess (if installed).
It is good to separate the PC from the user account as sometimes an odd
problem can be from some funky issue on the PC.
I'm not surprised that different versions of the Exchange 2010 client
doesn't make a difference as there is the formatting is set when
Exchange formats the outgoing to the internet.
A thought there, is your user setup as a contact on the Exchange
system, there have been settings in the past that caused invalid
formatting of internet messages. Something to the effect that 'this
user is on OutLook/Exchange vs regular internet standards'.
Has there been a single appointment sent from a user on that Exchange
system to two of your users?
Andy Konecny
Konecny Consulting Inc. in Toronto
"Give more than others think is wise
Challenge yourself beyond what others think is right"
Michael 'Pinball' Clemens

Exchange 2010 - iPhone will work in Wifi but not ATT 3g

Hello Everyone,
This is my first time posting, but I'm desparate!
I have an Exchange 2010 environment at our CoLo (not on site). I can connect to it on my iPhone 4 on ANY wifi network (home, work, etc), but if I connect to it via ATT 3g - no dice. I'm pretty sure it's a DNS issue, but there's no way for me to see what ATT DNS servers are returning. Anyone else have this problem? Does anyone know how long ATT caches DNS queries? Thanks in advance!
EDIT: It's totally DNS. I cannot hit OWA in safari either while on ATT, but again it works on WIFI everywhere. I setup DNS a little less than 24 hours ago, so I'm surprised that ATT is still having issues with it... Now I wonder if I can call ATT and see if they can flush the cached queries >.<

EDIT 2: Of course ATT was useless. Tried to transfer me away from them (to Apple and even Microsoft lol). I guess it's just a waiting game to see if their DNS servers get with the program...

Exchange 2010 Unable to create new mailboxes through provisioning

Recently I started noticing that when attempting to create a new mailbox in Exchange 2010 I was receiving the error "Load balancing failed to find a valid mailbox database". I checked the provisioning by running the command "Get-MailboxDatabase
| ft Name,IsExcludedFromProvisioning". All my databases are set to "true". All I would have to do is run the command "get-mailboxdatabase | set-mailboxdatabase -isexcludedfromprovisioning $false" to enable the provisioning again. My
question is here, does this require any kind of reboot or setting the DAG into maintenance mode? These are prod servers and I would hate to run a command that might cause an unplanned downtime of any sort. I got a feeling that this is probably a quick simple
command and wont cause any issues, just want to confirm that this won't require any sort of planning before running.

No, you don;t have to restart the server or make any changes in DAG.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
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.

Exchange 2010 SP3 - RU3 RU4 Public Folders issues ( not refreshing ) when grouping by Categories for "(None)" Group

After installing Exchange 2010 SP3 RU3, I had an issue in Public Folders, once having group by categories in Outlook, the Group of "(None)" categories is not refreshing when changing flag... I also installed RU4 but nothing changed, any reason
Thx

Hi,
From your description, the group with none categories won’t fresh when changing flag in Category view. If I misunderstood, please point it out.
As you can in the View tab as below, there is Category as well as Flag: Start date or Due Date. It means that grouping per color categories is more or less different from that
grouping by flag.
Should you need more assistance, feel free to tell me.
Regards,
Rebecca Tu
TechNet Community Support

On-premise Exchange 2010 SMTP Relay to O365 mailboxes does not resolve Display Name

Similar Messages

Maybe you are looking for