Applying CU4 for Exchange 2013 SP1 in a mixed 2010 / 2013 Environment

We're planning to apply Exchange 2013 SP1 CU in our mixed 2010 / 2013 environment. We'd also like to apply Exchange 2010 SP3 Rollup 5 as well. Are there any gotchas or best practices on what update to apply first?
Orange County District Attorney

We are planning to update our 2013 from CU5 to CU8
and 2010 SP3 to Rollup 9
I cant find any official documentation from MS concerning the upgrade path. Example.
Exchange 2013 first, then 2010. Like the above post outline.
I see 2010 being upgraded first thus bring version numbers closer together, reducing incompatibilities.
Do you still feel this is the appropriate install procedure?
Have you done this?
Djoe

Similar Messages

BPA shows domain prepped for Exchange 2007 SP1 after SP3 install

Hello,
I have a Client with a domain that is at 2003 domain functional level and 2000 forest level.
The client had Exchange 2007 SP1 and I have just upgraded it to SP3. There is one CAS, one Hub Transport, and one Mailbox Server (All three had Exchange 2007 SP1).
The domain and forest were prepped earlier by someone else and when I ran the installation program, it didn't pop up any errors on any of the servers.
The upgrade to SP3 is in preperation to Exchange 2010. Everything is working ok. I have checked:
1) In ADSIEdit, Exchange System Objects properties: Object Version =11221.
2) In ADSIEdit, Services>Microsoft Exchange>Organization: Object Version =11222
3) In ADSIEdit, RangeUpper value of ms-Exch-Schema-Version-Pt object = 14625
However, When I run the Exchange BPA, it reports that the domain is prepped for Exchange Server 2007 Service Pack 1 (In informational items). This is an informational item and not a warning or alert. However, I am concerned. Is this normal, and will it affect
the migration to Exchange 2010?
Thanks,
HA

Hello Ha20,
Based on my experience, it will not affect the migration. However, it’s recommended to prepare the schema again to avoid any potential issues.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange AutoDiscover not working correctly in 2010/2013 environment

Here's my setup:
Mixed environment transitioning:
Exchange 2010 running on Server 2008 in a VM
Exchange 2013 running on Server 2012 in a VM
I have split dns so that autodiscover.domain.com points to my 2013 server internally and my 2010 server externally. When setting up new profiles in outlook internally, autodiscover seems to work fine. However, when I try moving the public autodiscover.domain.com
DNS record over to the 2013, things stop working (like auto profile setup).
I know that the 2013 server is reachable from the outside because mail.domain.com will to go owa and ecp without a problem. I can log in to both without an issue.
If I point public DNS back to my 2010 server, then all is well again with outlook anywhere and mobile connectivity.
I'm not really sure what needs to be tweaked for the 2013 server to be ready to take over the day to day communications so that I can decommission my 2010 server.
Here are the results of the connectivity analyzer:
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for me.
Testing Autodiscover failed.
Additional Details
Elapsed Time: 1774 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method.
Additional Details
Elapsed Time: 1773 ms.
Test Steps
Attempting to test potential Autodiscover URL https://domain.com:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 489 ms.
Test Steps
Attempting to resolve the host name domain.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 98.129.228.152
Elapsed Time: 165 ms.
Testing TCP port 443 on host domain.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 97 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 225 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server domain.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=www.domain.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)09, OU=2150198723, O=www.domain.com, C=US, Issuer: CN=Equifax Secure Global eBusiness CA-1, O=Equifax Secure Inc., C=US.
Elapsed Time: 170 ms.
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Host name domain.com doesn't match any name found on the server certificate CN=www.domain.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)09, OU=2150198723, O=www.domain.com, C=US.
Elapsed Time: 1 ms.
Attempting to test potential Autodiscover URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 1009 ms.
Test Steps
Attempting to resolve the host name autodiscover.domain.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: x.x.x.x
Elapsed Time: 70 ms.
Testing TCP port 443 on host autodiscover.domain.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 189 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 300 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.domain.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=mail.domain.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated, Issuer: CN=PositiveSSL CA 2, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.
Elapsed Time: 220 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name autodiscover.domain.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 1 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.domain.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE.
Elapsed Time: 34 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 5 ms.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 5/19/2014 12:00:00 AM, NotAfter = 5/18/2016 11:59:59 PM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 276 ms.
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
Additional Details
Elapsed Time: 172 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user [email protected].
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.HTTP Response Headers:
Connection: close
Content-Length: 315
Content-Type: text/html; charset=us-ascii
Date: Sat, 19 Jul 2014 03:44:42 GMT
Server: Microsoft-HTTPAPI/2.0
Elapsed Time: 171 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method.
The attempt to contact Autodiscover using the HTTP Redirect method failed.
Additional Details
Elapsed Time: 207 ms.
Test Steps
Attempting to resolve the host name autodiscover.domain.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: x.x.x.x
Elapsed Time: 15 ms.
Testing TCP port 80 on host autodiscover.domain.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 76 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.domain.com for an HTTP redirect to the Autodiscover service.
The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.
Additional Details
An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: HTTP Response Headers:
X-FEServer: SMSE2013
Content-Length: 0
Date: Sat, 19 Jul 2014 03:44:42 GMT
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET
Elapsed Time: 115 ms.
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
Additional Details
Elapsed Time: 39 ms.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.domain.com in DNS.
The Autodiscover SRV record wasn't found in DNS.
Tell me more about this issue and how to resolve it
Additional Details
Elapsed Time: 39 ms.
Checking if there is an autodiscover CNAME record in DNS for your domain 'domain.com' for Office 365.
Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning.
Tell me more about this issue and how to resolve it
Additional Details
There is no Autodiscover CNAME record for your domain 'domain.com'.
Elapsed Time: 28 ms.
I just double checked my SSL cert and it has the three typical entries:
DNS Name=mail.domain.com
DNS Name=AutoDiscover.domian.com
DNS Name=domain.com
I have assembled the output for the following commands
HERE
Get-OutlookProvider | fl
Get-OutlookAnywhere | fl
Get-ActiveSyncVirtualDirectory | fl
Get-AutodiscoverVirtualDirectory | fl
Get-EcpVirtualDirectory | fl
Get-OabVirtualDirectory | fl
Get-OwaVirtualDirectory | fl
Get-PowerShellVirtualDirectory | fl
Get-WebServicesVirtualDirectory | fl
Text
I have gone through the Exchange Server Deployment Assistant. Almost everything was as it should have been. I made some changes in the "Enable and configure Outlook Anywhere" and "Configure
service connection point."
I have switched external DNS over to my 2013 server, and the connectivity test is still failing. It is also not proxying the 2010 mailboxes through 2013 as it should (according to the Deployment Assistant).
I have a 2010 test account and a 2013 test account. Both work fine in their respective WebMail's, but the 2010 mailbox will not pull up through the 2013 WebMail.
Just for the heck of it, I have checked my SonicWall and it is configured the same for the 2010 host and the 2013 host. I knew that ports 80 and 443 were passing on both hosts anyway because the port 80 redirect works and https webmail works
on both hosts.
If I try to access the xml file directly on both hosts:
https://mail.domain.com/Autodiscover/Autodiscover.xml (2013)
https://webmail.domain.com/Autodiscover/Autodiscover.xml
(2010)
I do get an xml response from both of them after authenticating like this:
<Autodiscover>
<Response>
<Error Time="18:17:41.0173284" Id="2526055628">
ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
Sooo...I'm stuck.

Update since my last post.
I have all mailboxes migrated off of 2010 and onto 2013. I'm ready to turn 2010 off as soon as I can figure out this autodiscover problem and get mail flow going in and out of the 2013 server instead of the 2010 one.
Brian, I had a http redirect enabled in 2013. I disabled that redirect and checked for any others. There is currently no redirect in place anywhere under the default web site (the root site now goes to an IIS 8 page). AutoDiscover is still
failing according to the Exchange Connectivity site.
When I switch autodiscover.domain.com over to the 2013 server I still get failures:
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
Additional Details
Elapsed Time: 146 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user [email protected].
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.HTTP Response Headers:
Connection: close
Content-Length: 315
Content-Type: text/html; charset=us-ascii
Date: Mon, 11 Aug 2014 16:50:27 GMT
Server: Microsoft-HTTPAPI/2.0
Elapsed Time: 145 ms.
If I try to hit the xml manually, I get the expected 600 error after providing a username and password. Should IIS be prompting for credentials when hitting the path for AutoDiscover.xml directly?
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response>
<Error Time="10:53:38.3228589" Id="36607859">
<ErrorCode>600</ErrorCode>
<Message>Invalid
Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
If I switch autodiscover.domain.com back over to my 2010 server the test passes:
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
Additional Details
Elapsed Time: 444 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user [email protected].
The Autodiscover XML response was successfully retrieved.
Additional Details
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006">
<Culture>en:us</Culture>
<User>
<DisplayName>Exchange 2013. Test</DisplayName>
<EMailAddress>[email protected]</EMailAddress>
</User>
<Action>
<Settings>
<Server>
<Type>MobileSync</Type>
<Name>https://mail.domain.com/Microsoft-Server-ActiveSync</Name>
</Server>
</Settings>
</Action>
</Response>
</Autodiscover>HTTP Response Headers:
Persistent-Auth: true
Content-Length: 736
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Date: Mon, 11 Aug 2014 17:08:12 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
Elapsed Time: 444 ms.
One interesting thing to note, is that <Url>https://mail.domain.com/Microsoft-Server-ActiveSync</Url>
is my 2013 server, not my 2010 server

Como instalar Labview 2013 SP1 si tengo instalado Labview 2013

Buenos Días,
tengo Instalado Labview 2013 y quisiera saber si tengo que desinstalarlo para instalar labview 2013 SP1
Espero sus respuestas
Gracias!
Solved!
Go to Solution.

* Yo no hablo español. He utilizado Google Traductor.
No. Usted debe ser capaz de instalar LabVIEW 2013 SP1 en la parte superior de la original de LabVIEW 2013. No debería haber necesidad de desinstalar. Sólo asegúrese de que usted tiene el Programa de Servicio Estándar (SSP). LabVIEW 2013 Service Pack 1 es una actualización exclusiva para LabVIEW 2013 para el Programa de Servicio Estándar (SSP) a los clientes.
descargar
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*I do not speak Spanish. I used Google Translator.
No. You should be able to install LabVIEW 2013 SP1 on top of the original LabVIEW 2013. There should not be a need to uninstall. Just make sure you have NI Standard Service Program (SSP). LabVIEW 2013 Service Pack 1 is an exclusive update to LabVIEW 2013 for NI Standard Service Program (SSP) customers.
Download
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If someone helped you out, please select their post as the solution and/or give them Kudos!

Forefront Server Protection 2010 for Exchange: Notifications behaving differently on E2007/2010

Hi all and happy holidays:
I have this particular situation with two client FSPE implementations recently.
I got one one client with a single E2007 server with FSPE v.11.0.713.0 and another one with a single E2010 server with FSPE v.11.0.713.0. I configured 'Keyword Filter Match' email notifications to Administrators and, to Internal Senders notifying them
not to use certain keywords in the future. The configuration of the notifications is exaclty the same and is using the following fields in the body of the message:
%Product% has detected a blocked keyword match on a message you sent.
      Filter Name: "%Filter%"
      State: "%State%"
      Subject line: "%Message%"
      Sender: "%ISAddress%%ESAddress%"
      Recipients: "%IRAddresses%%ERAddresses%"
      Scan job: "%ScanJob%"
      Location: "%Company%/%Site%/%Server% (%Folder%)"
Certain kewords are not allowed through this mail system as they may be offensive to others. Please refrain from using this word(s) in the future. If you believe you received this in error, contact your system administrator.
Notifications are working great, detecting when a user is Internal Sender and delivering the message correctly but here's the issue:
1. On the E2007 system, when the user/administrator get the notification from FSPE, the %Filter% field it displays the actual keyword that that was used:
Microsoft Forefront Protection for Exchange Server has detected a keyword filter match.
Filter name: "English Profanity: <RealUglyWord>;English Profanity: <RealUglyWord>"
2. On the E2010 system however, when the user/administrator get the email notifications, the %Filter% field only displays the name of the keyword list:
Microsoft Forefront Protection for Exchange Server has detected a keyword filter match.
      Filter Name: "English Profanity"
No biggie you may think but, the issue is that the user has no way to know for sure which words should not use. Of course they can call the Administrator but this will cause uneeded calls to the helpdesk IMO. In the case of English profanity, it may
be obvious but, in the case of other keyword lists, it may not be so obvious. For example, I also have another keyword list blocking racist terms. To some people the word 'gringo' may be offensive, but not to others. IMO, it should not be used
at all, and I am hispanic. In any case, the user needs to know for sure which words are being blocked and not to use it IAW company policy and know that the message was not delivered. Similar keyword lists are in use on both clients for "Spam-like
language', 'Sexual harassment', etc, etc so, this is an important client requierement and part of their 'Suitable Working Envrionment' policy and enforcement.
Hope anybody has any ideas on how to fix it.
Regards,
Fred Larracuente

Remove filter name from the notification area

Setup a simple sales funnel with exchange 2013 public folders and outlook 2010 -2013

BCM for Outlook is big and has too many choices. What we want is a combination of contacts and tasks within a public folder so we can see what others are doing. If possible I want
to make a connection between an contact and a task. The task should have some extra fields like branches responsible organization members status etc. Does anyone have a simple solution which is easy to implement in a small organization of 10 people?

Hello,
First of all thank you for your answer. The Outlook version I'm using is 14.0.7113.5005 and the Exchange versuin is CU3. As I'm testing it on XP client it is probably the issue in the PS. I'll try it with Win7 client probably tomorrow. I wonder if there
exists any kind of workaround for XP clients.
Thank you in advance,
Peter

Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
Error look like - cannot find exchange server.
I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
Someone have the same problem with migrated mailbox? How to solve it?
Truly, Valery Tyurin

You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
Moreover, you can try this utility (
http://www.exchangemigrationtool.com/ ) to accomplish this task.

DPM 2012 sp1 Exchange 2013 sp1

Hello
Is DPM 2012 sp1 supported to backup Exchange 2013 sp1?
Bulls on Parade

Hello,
At present, there are no official articles or Exchange Team Blogs to verify whether DPM 2012 sp1 supported to backup Exchange 2013 sp1.
Before you use DPM 2012 sp1 to back up exchange 2013 sp1, please test it in lab environment. If there is any error, please free let me know.
Cara Chen
TechNet Community Support

Exchange 2010/2013 co-existence and Lync integration

Hello,
I'm looking at integrating Lync Server 2013 into my lab environment, which consists of a mixed 2010/2013 Exchange environment.
UM - Exchange 2010
CAS - Exchange 2013
MBX - Exchange 2010
MBX - Exchange 2013
I've been reading about associating CAS and MBX servers with UM dial plans, when integrating with Lync.
The Technet articles, and MS Press documentation I've read suggests that
all CAS and MBX servers need to be associated with the dial plan.
Does this include the 2010 MBX servers?
As far as I was aware, in a co-existence environment between 2010/2013 all traffic is proxied to the MBX servers via the CAS 2013 role?
Does this rule still apply when UM and Lync exist in the environment?
Also, does the 2010 UM server need to be associated with the Lync UM dial plan, or does the 2013 CAS server handle this traffic as well?
Thanks
Matt

So, just the UM server in 2010 would be associated with the dialplan, you won't even have the option to add a 2010 MBX server.
The traffic isn't proxied by the 2013 CAS, it's more of a redirect, and yes this happens. A lot of what will happen under the hood will be somewhat transparent, Lync will determine where it wants to send the UM traffic. You can
watch this in the Lync logger by watching SIPStack.
The 2010 UM server can be associated with the dial plan, but you might not need it unless you're trying to recreate that specifically in your lab. Exchange 2013 UM can serve mailboxes on an Exchange 2010 server.
I would suggest just deploying it in your lab and watching what happens, that's half the fun. :)
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Exchange 2013 SP1: Fix for failing MSExchangeTransport service

We had a newly updated Exchange 2013 SP1 that would not start the Transport service
"Netstat -b" showed that a service was listening to port 25 on all IP's (0.0.0.0:25) and when the service could not get the port, it would die, and Exchange would attempt to restart it over and over.
After many tears, I found this solution:
Through the console or the ECP, check the Frontend receive connectors and find the one that is listening on 0.0.0.0:25, which is probably the Default Frontend Receive. Disable it.
Restart the MSExchangeTransport and MSExchangeTransportFrontEnd services.
If both services restart normally, troubleshooting is complete.
We use several custom connectors carried forward from the previous installation, which was SBS 2008. If this applies to you, take notice.

Normally, the Default Frontend Receive Connector (0.0.0.0:25) is the messaging entry point for your organization (I am assuming that you have a single MBX/CAS server).
1. If you disable the Default Frontend Receive Connector (0.0.0.0:25), you block inbound email.
2. Most probably, the cause for your problem are the Custom Receive Connectors. Check their type, and if it is Hub Transport, delete and re-create them as Front End Receive connectors.
Step by Step Screencasts and Video Tutorials

Unable to open delivery reports in Exchange 2013 SP1. Gives warning "The status for the recipient can't be determined because of a temporary error. Please try again later."

This seems to be occurring with all users (have tested a few, all display the same exact error message).
When I click on "Message Delivery Report" in Outlook 2010 or 2013, it points me to the ECP and displays this message "Warning The status for the recipient can't be determined because of a temporary error. Please try again later." I'm
not sure which log files to look at. The last time I remember it worked was before I applied SP1, I think CU3.
Our environment is two servers running Exchange Server 2013 Std. SP1 (847.32) in a DAG.
Thanks.

Hi,
From the error description, I would like to clarify the following thing:
Delivery Reports is a message tracking tool that you can use to search for delivery status on email messages sent to or from users in your organization's address book, with a certain subject. In Exchange 2013, you can track messages for up to 14 days after
they were sent or received. Please make sure the message you are tracking isn't older than 14 days.
Here is an article for your reference:
Track messages with delivery reports
http://technet.microsoft.com/en-us/library/jj150554(v=exchg.150).aspx
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Send Issues with Outlook for Mac (2011 / V15) and Exchange 2013 SP1

Hi all,
we have a strange issue with only with Outlook for Mac Users (version 2011 and the newest Outlook Version (V15) from Office 365) connected to our Exchange Server 2013 SP1. Some emails which we send out to the exactly same recipient are not sent through our
Exchange Server.
We have sent 8 emails with subject "test1, test2, test3...". Only test 3-6 was arriving to the recipient. The other emails are in the "sent" folder but it was not sent out through the Exchange.
What we can see with "Get-MessageTrackingLog" is, that the Recipients and MessageSubject are empty for these emails:
Timestamp Sender Recipients MessageSubject
25.02.2015 16:48:52 [email protected].. {}
25.02.2015 17:04:43 [email protected].. {}
25.02.2015 17:08:25 [email protected].. {[email protected]} test 3
25.02.2015 17:08:56 [email protected].. {[email protected]} test 4
25.02.2015 17:09:38 [email protected].. {[email protected]} test 5
25.02.2015 17:09:38 [email protected].. {[email protected]} test 6
25.02.2015 17:13:45 [email protected].. {}
25.02.2015 17:13:55 [email protected].. {}
We can still reproduce the issue on different Mac computers.
Thanks for any help in advance!
Thanks and best regards
Reto

Here is the mailheader form the successfully sent email:
Date: Wed, 25 Feb 2015 17:08:25 +0100
Subject: test 3
From: sender <[email protected]>
To: "'[email protected]'" <[email protected]>
This mailheader is from an email which was not sent out:
User-Agent: Microsoft-MacOutlook/15.6.0.150113
Date: Wed, 25 Feb 2015 16:48:52 +0100
Subject: test 1
From: sender <[email protected]>
To: [email protected] <[email protected]>
Interesting: Only the not received messages contains User-Agent string and have some quotation marks missing in the To field.

Exchange Admin Center 2013 SP1 worked for a day and then stopped working, possible OAB problems

Here is a problem that has me confused. On a fresh Windows Server 2012 R2, I installed Exchange 2013 SP1. It was successful and for the first day everything was working well. I then installed all security updates. The next day, I could no longer log in to
the Outlook Web App or Exchange Admin Center. I get the generic "something went wrong" message, and the only details are X-FEServer: LAKEVIEW-SERVER (our server name). Nothing else. In the event viewer, I have the logs below every time I try to log
in. This is repeatable. Every time I attempt to log in the same 3 things appear in the Application Log.
Event 1003, MSExchange Front End HTTP Proxy [Oab] An internal server error occurred. The unhandled exception was: System.Configuration.ConfigurationErrorsException: Microsoft.Exchange.HttpProxy.ProxyModule,Microsoft.Exchange.FrontEndHttpProxy
does not implement IHttpHandlerFactory or IHttpHandler.    at System.Web.Configuration.HandlerFactoryCache.GetHandlerType(String type)    at System.Web.Configuration.HandlerFactoryCache..ctor(String type)    at System.Web.HttpApplication.GetFactory(String
type)    at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Event 4999, MSExchange Common Watson report about to be sent for process id: 2460 (IIS Worker Process, w3wp.exe), with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, w3wp#MSExchangeOABAppPool, System.Web, S.W.C.HandlerFactoryCache.GetHandlerType,
S.Configuration.ConfigurationErrorsException, e0bc, 04.00.30319.34009. ErrorReportingEnabled: True
Event 1310, ASP.NET 4.0.30319.0 Event code: 3008 Event message: A configuration error has occurred. Event time: 5/8/2014 9:46:45 AM Event time (UTC): 5/8/2014 4:46:45 PM Event ID: 2c98a65728a7475db0212291e3934ab7
Event sequence: 19 Event occurrence: 9 Event detail code: 0 Application information:     Application domain: /LM/W3SVC/1/ROOT/OAB-1-130440407246522811     Trust level: Full     Application Virtual Path: /OAB
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\OAB\     Machine name: LAKEVIEW-SERVER Process information:     Process ID: 2460 (IIS Worker Process, w3wp.exe)
    Process name: w3wp.exe     Account name: NT AUTHORITY\SYSTEM Exception information:     Exception type: ConfigurationErrorsException     Exception message: Microsoft.Exchange.HttpProxy.ProxyModule,Microsoft.Exchange.FrontEndHttpProxy
does not implement IHttpHandlerFactory or IHttpHandler.    at System.Web.Configuration.HandlerFactoryCache.GetHandlerType(String type)    at System.Web.Configuration.HandlerFactoryCache..ctor(String type)    at System.Web.HttpApplication.GetFactory(String
type)    at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Request information:     Request URL: https://localhost:443/OAB/     Request path: /OAB/     User host address: ::1     User:     Is authenticated: False     Authentication
Type:     Thread account name: NT AUTHORITY\SYSTEM Thread information:     Thread ID: 18     Thread account name: NT AUTHORITY\SYSTEM     Is impersonating: False     Stack
trace:    at System.Web.Configuration.HandlerFactoryCache.GetHandlerType(String type)    at System.Web.Configuration.HandlerFactoryCache..ctor(String type)    at System.Web.HttpApplication.GetFactory(String type)
at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
My first guess is to reset the Outlook Address Book by using the Remove-OabVirtualDirectory Exchange commandlet. But I am not so sure this will work because Exchange worked for a day. Any help understanding what caused the problem (and thus help avoid it
happening again) and how to fix it are appreciated. Thanks.

hi,
If nothing works try resetting the Virtual Directories.
For owa
Open Exchange Management Shell (EMS), and then run the following cmdlet to change the authentication method of the "owa" virtual directory to Windows authentication:
set-Owavirtualdirectory -identity "MBX\owa (Exchange Back End)" -WindowsAuthentication $True -Basicauthentication $false
-Formsauthentication $false
Run the following command on both the Client Access and Mailbox servers to restart Internet Information Services (IIS):
iisreset /noforce
For ECP
Start Windows PowerShell.
Type the following commands, and then press Enter after each line:
Add-PSSnapin *exchange*
Set-EcpVirtualDirectory -Identity "MBX\ecp (Exchange Back End)" -WindowsAuthentication $true -FormsAuthentication $false
Run the following command on both the Client Access and Mailbox servers to restart Internet Information Services (IIS):
iisreset /noforce
For Ref: http://technet.microsoft.com/en-us/library/bb123752(v=exchg.150).aspx
I did those commands. But remember, the original error I gave was related to the OAB virtual directory, not ECP or OWA. I also did the Remove-EcpVirtualDirectory, Remove-OabVirtualDirectory, and Remove-OwaVirtualDirectory commandlets and the corresponding
EcpVirtualDirectoryOabOwaVirtualDirecoty ones. I still cannot log in to the Exchange Admin Center. And I still have the same original generic unhelpful error message.
However, there are some changes. After I removed and re-added the virtual directories I no longer received the original error logs given above. I now get this log in the event viewer:
Event 2001, MSExchange Front End HTTP Proxy
[Owa] Failed to load SSL certificate.
The first logs I gave above always appeared after attempting to log in. This log that I gave appears infrequently and is not connected to any log in events. This log occurs only
after a similar log given below:
Event 1001, MSExchange Front End HTTP Proxy
[Owa] Application Starting.

Exchange 2013 sp1 smtp NTLM auth for child domain users

i have exchange organization with exchange 2007 sp 3 & exchange 2013 sp1.
there are all users in Exchange 2013 server (mail flow is through Exchange 2013 server)
i have single forest, 2 site (site1, site2), root domain root.local and 1 child domain ch.root.local
DC for child domain is located in site2 (dc.ch.root.local)
multirole exchange 2013 server is installed in root domain.
i am traing to configure smtp receive connector with NTLM auth and have one problem.
when user in child domain try send email through this receive connector i see in log
<,AUTH NTLM,
>,334 <authentication response>,
*,SMTPSubmit SMTPAcceptAnyRecipient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
*,CH\user1,authenticated
*,,Setting up client proxy session failed with error: 535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user
*,,"Setting up client proxy session failed with error: 451 4.4.0 Primary target IP address responded with: ""535 5.7.3 Unable to proxy authenticated session because either
the backend does not support it or failed to resolve the user."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 192.168.1.15:465"
but authentication is succesfull for users from root domain.
why do it can be?
Thanks.

thanks for link
at smtp receive logs (Hub transport role) i've found the next:
Client Proxy EXMAIL2013,08D134DAF6CE1C51,49,192.168.1.15:465,
*,NT AUTHORITY\SYSTEM,authenticated
>,235 <authentication response>,
<,XPROXY SID=08D130D354F520D1 IP=192.168.1.21 PORT=57085 DOMAIN=[192.168.1.21] CAPABILITIES=0 SECID=Uy0xxx...
*,,Error while looking up SamAccountName chuser: The user name or password is incorrect.\r\n
*,None,Set Session Permissions
>,250 XProxy accepted but user identity could not be obtained,

Exchange Server 2013 SP1 - Optimize for Single Server Use

Hello,
i've set up Exchange 2013 SP1 with at last CU6 - get exchangeserver says:
AdminDisplayVersion             : Version 15.0 (Build 995.29)
ExchangeVersion                 : 0.1 (8.0.535.0)    - - - funny number ;-) (is this an early version???)
Yes, the annoying 16028 in the application log are running every five minutes, but thats not the main question.
Which services are needed in a SINGLE-SERVER Environment, without DAG and unified messaging?
Can the Self-Checking, Health- and Self-Probing be put down?
These services are started automatic:
   Microsoft Exchange Active Directory Topology
   Microsoft Exchange Anti-spam Update
   Microsoft Exchange DAG Management
   Microsoft Exchange Diagnostics
   Microsoft Exchange EdgeSync
   Microsoft Exchange Frontend Transport
   Microsoft Exchange Health Manager
   Microsoft Exchange Mailbox Assistants
   Microsoft Exchange Mailbox Replication
   Microsoft Exchange Mailbox Transport Delivery
   Microsoft Exchange Mailbox Transport Submission
   Microsoft Exchange Migration Workflow
   Microsoft Exchange Replication
   Microsoft Exchange RPC Client Access
   Microsoft Exchange Search
   Microsoft Exchange Search Host Controller
   Microsoft Exchange Service Host
   Microsoft Exchange Throttling
   Microsoft Exchange Transport
   Microsoft Exchange Transport Log Search
   Microsoft Exchange Unified Messaging
   Microsoft Exchange Unified Messaging Call Router
   Microsoft Exchange-Informationsspeicher
   Microsoft Filtering Management Service
   Microsoft Online Services Sign-in Assistant
And with C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue\mail.que about 512 MBytes size (which may may be a designed default size)...
Have set up about 6 users mailboxes, 3 public folder in a mailbox for public folders. Only for testing purposes sent some (small) mails, no external mails received (only testing receive with 'popcon' for mail delivery to the internal boxes).
The server (2012 R2) is running only in the internal network (yes, with internet connection for updates).
No virus scanners, not third party receive or send connectors, only the 5 default (3 Frontend, 2 Hub) receive Connectors and one Send Connector to our mail provider set up and no user activity (only sometimes from me for testing).
It seems like it's doing only with itself, logging file sizes of above 11 GB (in 4 weeks), with huge amounts of probing, health checking, internal testing, internal updating etc.
Can this logging be set up to a lower level, can services be deactivated (for single server configuration),
the logging volume should be in a useful relation to the mail use of the server, a message for every self test, internal health check etc. in the log-files normally isn't useful, only when problems occur there is a need...
Thanks in advance
Andreas

Between Exchange protocol-based log files, PerfMon .blg files used by Managed Availability, IIS logs, etc., the total footprint can add up quickly and these logs are not purged automatically. You can take a look at this site below and use the powershell
script to clean it up.
http://www.c7solutions.com/2013/04/removing-old-exchange-2013-log-files-html

Applying CU4 for Exchange 2013 SP1 in a mixed 2010 / 2013 Environment

Similar Messages

Maybe you are looking for