Q10 on Exchange 2013 AS issues

Hello Gents,
So we have moved over to exchange 2013 and we are having issues with the Q10 using active sync. When the phone is setup initially it works perfect, everythings syncs and updates as it should. After a day or so, there is alot of intermittent connectivity.
For instance, calendar appointments updated on outlook will not reflect on the phone and vice versa. Yesterday it just stopped receiving emails as a whole for a while. It is not the users account because he also has a Galaxy note 3 using active sync and everything works just fine both ways.
Is there a known issue on the Q10's with active sync?
Any work arounds?
Please advise,

Hi I have the same problem and I can't understand why.....

Similar Messages

Exchange 2013 Install Issues

Hi everyone -
I'm having BIG issues with my Exchange setup. First off, I walked into a nightmare of a situation here and it seems everything is completely jacked up in terms of network and servers... I'm actually contemplating starting over 100% with everything,
but when I bring that up to upper management, they say it's not feasible.
We currently have Exchange 2007 SP3 with RU11. I found out that when SP3 was installed, whoever did it never updated AD or the schema. Now I can't do that because i'm on RU11 and it's giving me a version mismatch error. So I've decided
to move on to just upgrade to Exchange 2013.
I am on the beginning steps of doing this and I just ran: setup /PrepareAD /IAcceptExchangeServerLicenseTerms. When doing this I get the following nasty little error:
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
FAILED
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
Cannot find the Recipient Update Service responsible for domain 'DC=kuder,DC=local'. New and existing users may not be
properly Exchange-enabled.
     One or more servers in the existing organization are running Exchange 2000 Server or Exchange Server 2003. Installa
tion can't proceed until all Exchange 2000 or Exchange 2003 servers are removed.
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
A couple of notes about this error:
1. I swear I've gotten some errors about the Recipient Update Service with Exchange 2007. I'm think that might have lead me to the schema upgrade issue I talked about earlier.
2. We DO NOT have Exchange 2000 or 2003 in our environment!!! Not sure where to even begin to remove the remnants of this!
Any help would be greatly appreciated.
Thanks,
Jeff

Thanks for the reply Cara... After further investigation last night it is clear to me that whoever upgraded us from Exchange 2003 to Exchange 2007, definitely didn't decommission the 2003 box correctly. (this was all done WELL before I came around).
I've checked into a few things that you asked about:
1. In ADSI Edit, I have 2 Administrative groups.  the first one (Exchange Administrative Group (FYDIBOHF23SPDLT)) shows the correct 2007 server in the CN=Servers, the other one (first administrative group) shows the old 2003 box
under CN=Servers.
2. I did get the schema update for 2007 SP3 to finally go. so when I looked in ADSI Edit, the Exchange Schema version is 14625 which according to that article is Exchange Server 2007 SP3, which is correct. Last time I looked, it was 14622,
which was for SP2. So we should be good there now.
3. The error with the RUS, was in Exchange 2007 BPA. After investigating this further last night, this is again because of failure to properly decommission the old 2003 box. Looks like I maybe need to remove any entries for Recipient Update
Service under ADSI Edit: CN=Configuration,DC=domainname -> CN=Services -> CN=Microsoft Exchange -> CN=First Organization -> CN=Address List Container -> CN=Recipient Update Services. There are two items in that location now, CN=Recipient
Update Service (domain) and CN=Recipient Update Service (Enterprise Configuration). From what I've read I can delete both of these since 2007 no longer uses this service.
4. No errors in the Application Log currently.
Other Notes:
1. Everything with 2007 appears to be working fine. No major issues.. I just want to upgrade us to Exchange 2013.
2. From the 2007 EMS, I ran: exchangeserver | ft name,admindisplayversion,exchangeversion. This showed me the following:
Name                       AdminDisplayVersion        ExchangeVersion
ADELSB01                   Version 6.5 (Build 7638... 0.0 (6.5.6500.0)
K01SIT003                  Version 8.3 (Build 83.6)   0.1 (8.0.535.0)
Definitely still showing the old 2003 Exchange box in there.
Thanks!

Exchange 2013 backscatter issue - recipient validation without Edge

Hello all,
It looks like there is a flaw by design in Exchange 2013 recipient validation, which in turn causes backscatter issues. I failed to find a way around it, maybe someone could help.
The Design: 2 x Exchange 2013 CAS + MBX servers (hardware NLB & DAG)
Version: Exchange Server 2013 Cumulative Update 3 (CU3) (Version
15.0 (Build 775.38) )
The issue:
Recipient validation has a flaw, which is documented (probably that should make it a "feature", but it doesn't):
In short - Recipient validation on Mailbox servers blocks message to all recipients, if at least one of them is non-existent.
http://social.technet.microsoft.com/Forums/office/en-US/12181f43-7173-44dd-998a-9307f92ffc5d/exchange-2013-casmbx-recipient-validation-rejects-entire-message-if-any-of-recipients-are-invalid
As there is no way to explain the logic of blocking e-mails to valid recipients if at least one of them is invalid to a customer, the Recipient validation on Mailbox servers becomes unusable and is disabled.
But if the recipient validation is disabled, the Exchange design without Edge servers or other perimeter SMTP servers that could block e-mails to non-existent recipients, becomes vulnerable to backscatter SPAM attacks, since Exchange will always send out
NDR to the FROM address.
According to the answer in the thread mentioned above, other antispam features should prevent it, but as always with antispam - it's not even close to 100% effective, as recipient validation would be. The result - an entry in backscatterer.org.
Question: How to prevent backscatter in Exchange 2013 without Edge servers, and without loosing valid e-mails due to recipient validation bug ("feature")?
Thank You for Your help.
Sincerely,
Vince

Hello,
Thank you for your question.
I am trying to involve someone familiar with this topic to further look at this issue.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Migrating public folders to exchange 2013 hebrew issue

I am migrating public folders to exchange 2013. half of them a named in hebrew.
The migration fails, the error is character related.
Is it possible at all to migrate hebrew named public folders?

Hi,
Did you got the error message mentioned in the following thread?
http://social.technet.microsoft.com/Forums/exchange/en-US/8b383a46-b710-4fc0-aa0b-e52f288cf93d/e2010-to-e2013-public-folders-migration-failed?forum=exchangesvrdeploy
If so, please check if they are mail-enabled public folders. If they are mail-enabled public folders, please make sure there are no invalid characters in alias.
Based on the description, you couldn't migrate public folders named in Hebrew, other public folders could be moved successfully. If I misunderstood your concern, please let me know.
If the issue persists, I'm afraid you need to rename these public folders in English.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 mailflow issues & transport latency

Hi,
we have more then 50 Exchange Server 2013 deployed and every single Exchange has transport issues.
-the transport Service do not respond for 30 min or more.
-RAM consumption
-the e-mail are stock in outlook for long time
-we have Exchaneg 2013 with all CUs / SP1 version installed and i cannot see any improvement.
I m disappointed and i hope that someone can help me to understand the Exchange 2013 Mailflow
Best regard

@ 1 i want to say thanks all of you for the Replays and for helpful information.
Yes i have a Transport Agent on the Computer for Archiving S.Nithyanandham
I fix the Problem with the Microsoft Script and now i will wait to see any improvement.
After i set the eventlog to high i can see
event id 12028
The process with process ID 11596 is holding the performance counter connections current Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 11596 StartupTime: 130566455797932178 from instance _total(CFBEE918) RefCount=0 SpinLock=0 Offset=32 and category MSExchangeTransport
SmtpSend while running processes are: Processes running are:
5908 w3wp
8468 msdtc
13736 powershell
1964 sftracing
20864 UMWorkerProcess
4128 MSExchangeDagMgmt
3468 Microsoft.Exchange.Diagnostics.Service
1368 mqsvc
4912 w3wp
12988 RuntimeBroker
2152 Microsoft.Exchange.Directory.TopologyService
388 svchost
6876 MSExchangeMailboxReplication
3132 MSExchangeSubmission
2540 MSExchangeMigrationWorkflow
19284 iexplore
2932 noderunner
10416 w3wp
16136 conhost
564 svchost
20352 conhost
1144 Internal.Exchange.CADNArchivingService
2132 WMSvc
12828 ParserServer
4296 scanningprocess
4688 GXHSMService
19244 conhost
17096 Microsoft.Exchange.Imap4Service
22020 vmtoolsd
4092 Microsoft.Exchange.UM.CallRouter
3696 MSExchangeThrottling
5664 Microsoft.Exchange.EdgeSyncSvc
344 csrss
736 svchost
14328 ParserServer
1128 svchost
19660 WmiPrvSE
5904 Microsoft.Exchange.Imap4
2108 svchost
21412 mmc
3464 w3wp
1316 cvd
6040 MSExchangeFrontendTransport
15560 iexplore
916 svchost
1504 hostcontrollerservice
16672 taskhostex
16868 explorer
9972 w3wp
712 svchost
4060 umservice
6620 svchost
6616 w3wp
13116 svchost
704 dwm
7204 Microsoft.Exchange.Store.Worker
15900 iexplore
108 winlogon
24732 conhost
500 lsass
696 Microsoft.Exchange.Store.Service
5816 Microsoft.Exchange.Search.Service
1480 svchost
1280 fms
7976 dllhost
1080 spoolsv
684 LogonUI
22248 mmc
20040 rundll32
10924 w3wp
13612 conhost
6588 MSExchangeMailboxAssistants
21952 conhost
1464 SMSvcHost
23816 mmc
16828 mmc
2640 noderunner
2836 noderunner
4608 EvMgrC
16700 Microsoft.Exchange.SharedCache
5196 w3wp
15636 MSExchangeHMWorker
6396 mmc
9044 Microsoft.Exchange.Imap4Service
4400 SMSvcHost
1836 nsclient++
3016 Microsoft.Exchange.RpcClientAccess.Service
1636 inetinfo
15424 csrss
1436 vmtoolsd
1828 ForefrontActiveDirectoryConnector
9384 w3wp
24148 MSExchangeTransport
6552 w3wp
4384 scanningprocess
4972 Microsoft.Exchange.AntispamUpdateSvc
3788 MSExchangeTransportLogSearch
14644 rundll32
19348 Microsoft.Exchange.Imap4
432 winlogon
22692 conhost
23676 rdpclip
2792 noderunner
4564 scanningprocess
228 smss
5152 MSExchangeDelivery
620 Microsoft.Exchange.ServiceHost
9484 w3wp
22216 ParserServer
5736 MSExchangeHMHost
1992 updateservice
21296 iexplore
21004 dwm
8292 WUDFHost
608 svchost
16768 conhost
396 csrss
5136 Microsoft.Exchange.Store.Worker
800 svchost
11240 w3wp
404 wininit
7692 svchost
9716 w3wp
492 services
4 System
24748 ParserServer
2760 msexchangerepl
0 Idle
event 2006
Send connector Inbound Proxy Internal Send Connector: the connection to xxx.xxx.xxx.x:2525 was disconnected by the remote server.
event 2128
Process w3wp.exe (ECP) (PID=10924). Object CN=HealthMailbox526969de2c35417c8a01222265520c3e,CN=Monitoring Mailboxes,CN=Microsoft Exchange System Objects,DC=domain,DC=dc was not found on the Domain Controller %hostname%. This may indicate a replication or
permission issue.
event 1012
The store driver failed to submit event 18522569 mailbox d57dd45b-f3e9-492d-b23c-0fea92c8dd85 MDB 7b71f84c-1bd3-4b16-a8a9-dca18f50fbb5 and couldn't generate an NDR due to exception Microsoft.Exchange.MailboxTransport.StoreDriverCommon.InvalidSenderException
   at Microsoft.Exchange.MailboxTransport.Shared.SubmissionItem.SubmissionItemUtils.CopySenderTo(SubmissionItemBase submissionItem, TransportMailItem message)
   at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.GenerateNdrMailItem()
   at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.<>c__DisplayClass1.<FailedSubmissionNdrWorker>b__0()
   at Microsoft.Exchange.MailboxTransport.StoreDriverCommon.StorageExceptionHandler.RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction).
event id 1023
Windows cannot load the extensible counter DLL ASP.NET_2.0.50727. The first four bytes (DWORD) of the Data section contains the Windows error code.

Exchange 2013 SPAM issues

I have a new install of Exchange 2013, I enabled the anti-spam features. From day one, my server has been sending out NDR spam from "Sender" <> (no sender just the two "<>") to user.ru, user.ro, user.gr, etc.
This issues is driving me crazy and there is almost zero info on the net with this issue. I find it hard to believe a clean install does this right out of the box. In Exchange 2007/10, I just have to tic a box in the transport agent.
Can someone help me please, I'm lost. Hell I even installed GFI this morning just to see if that would make a difference and even GFI is letting the SPAM <> mail through without any issues. It's just a matter of time before my server is
blacklisted...
Thanks you,
TCMagic

Well that did not fix the problem. My server is still sending spam. Here's what one of the messages look like (I removed my actual domain):
Identity: mail\71\627065225217
Subject: Undeliverable: Never lose a food storage container again
Internet Message ID: <[email protected]>
From Address: <>
Status: Ready
Size (KB): 212
Message Source Name: DSN
Source IP: 255.255.255.255
SCL: -1
Date Received: 4/13/2013 1:00:13 PM
Expiration Time: 4/15/2013 1:00:13 PM
Last Error:
Queue ID: mail\71
Recipients: [email protected];2;2;;0;CN=InternetConnector,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group
As I look at this the SCL rating is -1 so the server thinks is good mail. Can someone help me here?
Thank you

Exchange 2013 Search Issues

We are having many issues with users being able to search old emails since migrating to Exchange 2013. We have renamed the search index files and rebuilt multiple times and they all state healthy at this time but users are still having issues finding
old emails. Trying to see if this is a product issue or a server issue and if so what needs to be done. Using Standard edition with 5 databases at this time.

Hi,
Thank you for your question.
Is there any error when we search email in outlook or OWA? I suggest we could post error to
[email protected] for our troubleshooting.
Did user search email within a week? Because we want to know if those emails were deleted by Retention Policy.
Are there relevant event id or application log?
We could make sure the service of “Microsoft Exchange Search” is running on all Exchange mailbox server. if the service of “Microsoft Exchange Search” is running on all Exchange mailbox server. we could restart it to check if the issue persist.
If OWA could search email, we could rebuild the outlook profile to check if the issue persist.
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

Tricky Exchange 2013 send issue - im stumped...

Hi everyone,
I ran into an issue this morning in my Exchange 2013 SP1 environment today that has me stumped. Like most issues, it just happens. No changes, patches or updates to the system were applied and the system was normal until now. Here is my problem –
My Outlook users have their own mailboxes, and my company has a Help Desk email box that has its own user account. My users are set up via Exchange / Outlook to have their own mailboxes and full access to Help Desk mailbox in their Outlook .
Each Outlook client in configured with the users account, and the Help Desk account because users want to be able to hit the FROM button in Outlook and chose whether a reply comes from them personally or the Help Desk mailbox. This has worked great,
up until now.
All of a sudden, you cannot send from the Help Desk account anymore. The mailbox opens up, a user can see and access all the mail and it is receiving email fine. But if a user wants to reply or create NEW email, choses FROM and uses the Help Desk account
they get this error on sending
Sending reported error (0x8004010F) Outlook data file cannot be accessed.
The users regular account works fine.
I recreated the mail profile, didn’t help the issue. I checked on OWA and if you access the Help Desk account on its own it sends fine.
If you create an email from your own email account and CC the Help Desk, it sends fine.
All users have Full Access permission and Send As permission on the server.
Nothing has changed that I know of and this worked totally fine for almost a year until today, it just stops working.
Any ideas, I’m totally stumped… I have to apply CU7 still this weekend, maybe that will do something. But as of now I cant even see any real errors as to whats going on here.
Ric

Hi,
In your case, please check the autodiscover and OAB by using "Test E-mail AutoConfiguration".
If autodiscover fails, please troubleshoot the autodiscover by directly accessing the autodiscover url via IE and let me know the error code. If autodiscover works, you need to troubleshoot the OAB generation, publishing and downloading issues.
For OAB generation and publishing issues, you can check the application logs on the CAS and Mailbox servers. For the OAB downloading issue, you can manually access the OAB url via IE and see if there is any error code.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 Installation Issues

Let's document my frustrations with installing and setting up Exchange 2013 on my Server 2012 Standard Edition Server.Steps taken before hitting install:Installed Server 2012 Standard and rebootedCreated a VSS for posterity sake.Downloaded CU2 fromhereInstalled Server Roles in PowerShell: Install-WindowsFeature RSAT-ADDSInstall-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,...
This topic first appeared in the Spiceworks Community

Hi,
As additional, I want to double confirm whether external user cannot receive message send from your environment and contain attachment, or cannot send message with attachment for external mail flow.
If it’s the former, it means mail flow works fine in your environment. You can contact administrator for destination forest to check attachment filter and transport rule.
If it’s the latter, this issue may be caused in your own configuration. We can check anti-spam filter, transport rule and send connector, run message track log and protocol log to find out the node for this issue.
More details about Anti-Spam and Antivirus Mail Flow, for your reference:
https://technet.microsoft.com/en-us/library/aa997242(v=exchg.141).aspx
Thanks
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]
Allen Wang
TechNet Community Support

Exchange 2013 ECP issues

I have 4 Exchange server, 2 CAS and 2 MBX. Migrated from 2010.
Everything works perfectly, but sometimes users can't change their password. If I move them to another database, sometimes it works, sometimes it doesn't. Then opening from a different computer, works or doesn't. I can't seem to find a way for it to always
work or never work....driving me nuts.
Both CAS servers seem to have the problem, no mailboxes are hosted on Exchange 2010 anymore.
Already tried to reset the ECP virtualdirectory, nothing changes.
When I change the web.config file, it gives a different error messages, but still weird.
Error is:
Server Error in '/ecp' Application.
Runtime Error
Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.

Hi,
Is there any error message when users couldn't change their password?
Please use EXBPA to check the health of Exchange 2013 server.
Besides, please check if there is any error in the application log.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 Relay issue (SMTP Authenticated)

Hi,
I installed Exch 2013 and is working great - both incoming mail and outgoing mail work fine in OWA and outlook.
Problem we are having is SMTP authenticated relay. We install application on all client computers which sends emails externally/internally.
Though we had authenticated in application, we are not able to send emails externally. Internally it works fine from application.
Our backup software stopped sending notifications on failures. Literally we are logging into each and every server and making sure backups are successful.
We never had a problem with Exchange 2010
I don't want to create relay and allow my whole ipaddress range (I think that's stupid)
Can anyone please help?

Hi,
You could create a Receive connector on the 2013 Mailbox server, and then configure the Receive connector with the following properties:
Create/configure a service account for the applications/copier to use.
Create a new Receive connector with the Usage value 'Custom', and don't assign any permission groups to the connector.
Specify the IP address(es) of the application servers/copiers as the only remote IP addresses that are allowed to use this Receive connector.
Use the Add-AdPermission cmdlet to add the ms-Exch-SMTP-Submit permission to the Receive connector for the service account.
The combination of restricting the IP addresses that the Receive connector listens to, and restricting permissions on the connector so that only the service account can send messages should do the trick.
For more information, see these topics:
Add-ADPermission
Receive Connectors
Receive Connector Permissions
Link
Deepak Kotian.
MCP, MCTS, MCITP Server / Exchange 2010 Ent. Administrator
Disclaimer:
Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!
All the opinions expressed here is mine. This posting is provided "AS IS" with no
warranties or guarantees and confers no rights.

Exchange 2007 to 2013 Migration issues. Prompt for credentials, Public Folders inaccessible, Apps not working

Exchange 2013 Migration issues
I have three issues and decided to list them here. Please pick and choose to assist. Thanks in advance.
Environment:
Mixed 2007 SP3 R12 and 2013 CU3. 2007 Environment was webmail.domain.com. I installed new Exchange 2013 (1 CAS, 1 Mailbox) according to:
http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx. Exchange 2007 is now legacy.domain.com and Exchange 2013 CAS is webmail.domain.com.
Machine 1: Windows 8.1, not domain joined, using Outlook Anywhere external. Outlook 2013
Machine 2: Windows 7, domain joined, using Outlook Anywhere internal. Outlook 2010 SP2
I have migrated 1 user so far to Exchange 2013. This user was a Domain Admin. I have removed that membership. I checked the box to inherit permissions of the security of the object and reset the AdminCount attribute in ADSIedit to 0 and verified this replicated
to all domain controllers. ( I originally thought this to be the issue with it prompting for the password. )
Here is a Get-OutlookAnywhere cmdlet...
ServerName                         : EXCHANGE2007SVR
SSLOffloading                      : False
ExternalHostname                   : legacy.domain.com
InternalHostname                   :
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Basic
IISAuthenticationMethods           : {Basic}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
MetabasePath                       : IIS://EXCHANGE2007SVR.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\WINDOWS\System32\RpcProxy
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 8.3 (Build 83.6)
Server                             :
EXCHANGE2007SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.1 (8.0.535.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2007SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2007SVR\Rpc (Default Web Site)
Guid                               : 4901bb14-ab81-4ded-8bab-d5ee57785416
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 12/31/2013 4:08:04 PM
WhenCreated                        : 7/18/2008 10:56:46 AM
WhenChangedUTC                     : 12/31/2013 9:08:04 PM
WhenCreatedUTC                     : 7/18/2008 2:56:46 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ServerName                         :
EXCHANGE2013SVR
SSLOffloading                      : True
ExternalHostname                   : webmail.domain.com
InternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://EXCHANGE2013SVR.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 775.38)
Server                             : EXCHANGE2013SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2013SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2013SVR\Rpc (Default Web Site)
Guid                               : d983a4b1-6921-4a7f-af37-51de4a61b003
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 1/7/2014 11:29:05 AM
WhenCreated                        : 12/31/2013 1:17:42 PM
WhenChangedUTC                     : 1/7/2014 4:29:05 PM
WhenCreatedUTC                     : 12/31/2013 6:17:42 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ISSUE 1
Issue: On Machine 1 (reference above) Windows Security prompt that says "Connecting to
[email protected]". Almost always prompts when Outlook is first opened. Afterwards (if it goes away) seemingly random on when it asks for it. I put in the credentials (absolutely correct) and it fails and prompts again.
I always check the box for it to save the password. To get rid of it, I click the Cancel button at which Outlook reports "NEED PASSWORD", but still acts fine sending and receiving emails. Eventually the "NEED PASSWORD" sometimes changes
to say "CONNECTED", but it works regardless.
No issues on Machine 2 so I don't know where the problem might be as there are a lot of variables in play here.
ISSUE 2
Migrated user is unable to open Public folders from Exchange 2007.
Cannot expan the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance. (/o=...).
This error occurs on Machine 1, Machine 2 and from OWA, same error each time.
ISSUE 3
Apps. Installed by default are 4 apps (Bing Maps, Suggested Meetings, Unsubscribe, Action Items). I have made sure the apps are enabled in OWA and they show up in mail items on both Machine 1 (Outlook 2013) and OWA. They do not show up in Machine 2 (Outlook
2010). I'm assuming that isn't supported.
In OWA, when I go to the installed apps listing it shows all of the apps but has a broken link on the image describing the app.
When I click the app in either Outlook 2013 or in OWA, I get "APP ERROR, Sorry we can't load the app. Please make sure you have network and/or internet connectivity. Click "Retry" once you're back online.
Current workaround is just disabling them through OWA.

Hello,
In order to avoid confusion, we troubleshoot a issue per thread usually.
For your first isue, I agree with Ed's suggestion to check if your certificate name is correct.
Besides, I recommend you change ExternalClientAuthenticationMethod from Basic authentication to Negotiate authentication to check the result.
For the second issue and third issue, please create a new post.
If you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Unable to send to external email recipients - Multi Tenant Exchange 2013 - MultiRole servers in DAG

Greetings all, I hope someone can help.
I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
Internal mail flow is fine (external email addresses can send to the domain).
External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
There are two multi-role Exchange servers that are members of the DAG.
I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
No SSL certificates have been purchased or installed yet.
Exchange URLs have not been changed since default configuration at install.
OWA and ECP works both internal and external.
External DNS works with SPF and PTR records correctly configured
Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
Send Connectors are the default ones created during install. Receive connector is standard configuration with - * -
When sending email to an external address, I receive a failure notice
ServerName.test.corp.int gave this error:
Unable to relay
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
More Info -
ServerName.test.corp.int
Remote Server returned '550 5.7.1 Unable to relay'
I have been troubleshooting this for many hours with no progress.
I have created new Send Connectors for the server that is advising that it is unable to relay, but they have all failed.
I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
I am at a loss as to why I can't send out with the default configuration. I would assume that email would flow out without any changes, but this does not happen.
Can someone please assist before I lose my sanity.
Thanks in advance,
Terry

Greetings all, I hope someone can help.
I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
Internal mail flow is fine.
Incoming mail from external senders is also fine. -
external email addresses can send to the domain).
External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
There are two multi-role Exchange servers that are members of the DAG.
I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
No SSL certificates have been purchased or installed yet.
Exchange URLs have not been changed since default configuration at install.
OWA and ECP works both internal and external.
External DNS works with SPF and PTR records correctly configured
Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
Receive Connectors are the default ones created during install. Send connector is standard configuration with - * -
When sending email to an external address, I receive a failure notice
ServerName.test.corp.int gave this error:
Unable to relay
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
More Info -
ServerName.test.corp.int
Remote Server returned '550 5.7.1 Unable to relay'
I have been troubleshooting this for several days with no progress.
I have created new Receive Connectors for the server that is advising that it is unable to relay, but they have all failed.
I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
Even more info - Further troubleshooting -
I found my one of my Exchange servers had an extra NIC. I have since added a second NIC to the other server, so now both Exchange servers have dual NICs. I removed the DAG cleanly and recreated the DAG from scratch, using this link -
hxxp://careexchange.in/how-to-create-a-database-availability-group-in-exchange-2013/
The issue still exists, even with a newly created DAG. I also found that the Tenant Address Books were not 'applied'. I applied them but still no resolution
I think the issue is related to multi-tenant configuration even though the error says that it can't relay. The unable to relay message can appear when sending from a domain that the Organization does not support. Like trying to email as [email protected]
when you domain name is apple.com - But through extensive research I still can't resolve the issue.
Can someone please assist before I lose my sanity.
Thanks in advance,
Terry

Unable to prevent backscatter with Exchange 2013

Hi,
From my research, it seems that Exchange 2013 might have an inherent flaw (although I hope I am wrong).
Unlike all previous versions of Exchange, the 'Filter recipients who are not in the Directory' feature doesn't work the same.
Exchange 2013 seems to check the recipient only after getting the message.
mail from:<[email protected]>
250 2.1.0 Sender OK
rcpt to:<[email protected]>
250 2.1.5 Recipient OK
data
354 Start mail input; end with <CRLF>.<CRLF>
Write some Text Here
550 5.1.1 User unknown
And here is Exchange 2010 for example:
mail from:<[email protected]>
250 2.1.0 Sender OK
rcpt to:<[email protected]>
550 5.1.1 User unknown
This is rather a big problem, because it means that every Exchange 2013 installation is just sitting and waiting to be abused with backscatter spam, and unlike previous incarnations of Exchange, there is nothing that can be done about it. Once an Exchange 2013
server has been abused with backscatter spam, its outgoing IP addresses will become blacklisted very quickly.
The only possible solutions I've found seem to require multiple server configurations and big complexity.
What can be done about this?

Hi Chukee1,
This is a known issue in Exchange 2013, as a workaround for this issue, you can enable recipient filter on Edge server.
http://technet.microsoft.com/en-gb/library/bb123891%28v=exchg.150%29.aspx
Here is a similar thread for your reference.
http://social.technet.microsoft.com/Forums/en-US/75bb174e-a4b9-4d8e-9d8e-5d4d5bc32dc3/exchange-2013-backscatter-issue-recipient-validation-without-edge?forum=exchangesvrsecuremessaging
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 mailflow and the Hosts file

Hello!
Recently I expirienced the issue with missing messages ( http://social.technet.microsoft.com/Forums/en-US/20745ec5-e311-4bc0-b1bd-aff3f7c82fd1/missing-messages?forum=exchangesvradmin ) and although that thread is not answered yet I would like
to clarify the following:
1) Exchange Server is working properly for day1 and day2
2) Day3: Sent messages begin to disappear
Resolution: I add my Exchange Server to the hosts file (on the Exchange Server machine), restarted the server and the mailflow was restored.
192.168.1.2 Mail
192.168.1.2 Mail.Test.Local
Test: Right after deleting Exchange Server records from Hosts and restarting the server the mailflow gets disrupted again.
Q1: Is it a bug?
Q2: If it's a bug why my Exchange has been working fine for day1 and day2?
Thank you in advance,
Michael

Hello all!
Here's my post that describes the issue:
http://social.technet.microsoft.com/Forums/exchange/en-US/20745ec5-e311-4bc0-b1bd-aff3f7c82fd1/missing-messages?forum=exchangesvradmin
There're two servers (VMs): Domain Controller and Exchange 2013. As I have no internet connection in my test environment only internal mail go missing.
Regarding Hosts file: as those post is still not answered I just did what MS support recomended for resolving Exchange 2013 DNS issue (there're a lot of posts regarding it here on technet) and it helped...
But it's nonsense - my DNS is up and running, it was running on Day1, Day2 and Exchange could use it successully, but starting with the Day3 Exchange Server can't use the same DNS server? Why???
Regards,
Michael

Q10 on Exchange 2013 AS issues

Similar Messages

Maybe you are looking for