Namespace for Exchange 2003 == 2010 == 2013 Migration

Hi
Hope someone can help. I am working on an Exchange 2003 to 2010 migration, which will then quickly move onto a 2010 to 2013 migration and need some clarification on the namespaces to use. I am aware that if I do not do this right at the 2003
to 2010 migration, this will cause a headache at the 2010 to 2013 migration.
Some background:
2003 Functional Level Domain - 2 x 2008 DC's
Currently users are on a 2003 exchange cluster with a mix of RPC (internal users) and RPC over HTTP connections (roaming users)
We will be installing Exchange 2010 on a single server, with CAS, HUB and Mailbox roles and no load balancer, as we will be moving quickly to 2013.
We have two Kemp load balancers ready for Exchange 2013.
Exchange 2010 is installed on a single server (exh2010.domain.local) and configured with an CAS array name (exh-cas.domain.local) which is resolvable internally only.
Currently we have multiple smtp namespaces e.g. @company.com, @company2.com.
Our main website etc is www.company.com
Our public facing services are at https://service.mycompany.com
Our 2003 RPC address is https://webmail.mycompany.com
I understand that the 2010 RPC CAS array name should be separated from the Outlook Anywhere (RPC over HTTPS) address so that when 2013 takes over the HTTPS address, the RPC connections are not broken.
Two Questions:
Do we have to use the HTTPS same namespace for 2013 as we do in 2010? Its just I would want to test the Kemp load balancers before making them live (slow careful transition), and giving them a different namespace, e.g.
https://mail.mycompany.com would allow a migration, rather then a cutover.
Can we use the *.mycompany.com address rather then the company.com address, even though we have no SMTP addresses at mycompany.com? Can autodiscover still work?
Thanks in advance for any guidance
Cheers
Steve

1. No, but you can. Exchange 2013 will proxy all services for Exchange 2010, so if you set up everything right, you should be able to simply swing the name from Exchange 2010 to 2013.
2. Your web services can be published with any domain as long as the hostname is in the certificate. Only Autodiscover needs to match the e-mail domain(s). So in your example, you could publish OWA, ECP, ActiveSync, Web Services and OAB
at owa.mycompany.com. You would need autodiscover.company.com, autodiscover.company2.com, etc., but if you don't have e-mail addresses with mycompany.com, you don't need autodiscover.mycompany.com. If all users have a company.com e-mail address,
the you only need autodiscover.company.com as long as users know to enter that e-mail address when configuring profiles on PCs or devices. If you're going to have to have Autodiscover for multiple domains, then you might consider using an SRV record
instead because it can greatly simplify your certificate requirements.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

Legacy Namespace for Exchange 2007 to 2013 co-existence

We are migrating from Exchange 2007 to 2013, during the co-existence phase, where is the legacy.{domain.com} namespace used? We are at the point now that we want to move all services over to the Exchange 2013 CAS servers, however... GPO settings
are used to point outlook clients to mail.{domain.com} for Outlook Anywhere. If DNS is updated to point mail.{domain.com} to the Exchange 2013 servers, will there be an issue with connectivity for people still on the Exchange 2007 servers? Do these people
need to point to legacy.{Domain.com} or will mail.{domain.com} proxy the connection to the legacy namespace? I would like to know if the GPO settings will interfer with the settings that Autodiscovery provide back.
I have read a bunch or articles on the approach, but I am still fuzzy on where legacy.{domain.com} comes into play.
Thanks in advance for your help.

In coexistence with exchange 2013 and legacy version the request happens in 2 types.
For Exchange 2010 –
Exchange 2013 does a Proxy for owa and ews requests for users in exchange 2010.
For Exchange 2007 –
Exchange 2013 does redirection for owa and ews requests for users in Exchange 2007.
Certificates:
All the required SAN entries for UM,webservices and activesync should be created.
Add external owa legacy URL to the public certificate and install it on both Exchange 2007 and
Exchange 2013 only then owa redirection will work.
You need to Include internal Legacy. Domain.com on Exchange 2007 Certificate for OWA co-
Existence.
Following change needs to be done in Firewall
External OWA URL should be directed to exchange 2013 Internet Facing CAS.
External EWS URL should be directed to exchange 2013 Internet Facing CAS.
External Autodiscover URL should should be directed to Exchange 2013 CAS.
External ActivesyncVirtualDirectory should be directed to Exchange 2013 CAS.
External UMvirtualDirectory should be directed to Exchange 2013 CAS.
Create new NAT rule on firewall for Legacy.domain.com to Exchange 2007 CAS. You can do this as well.By doing this users will be able to log on directly using the URL https://legacy.domain.com/owa with
a mailbox on Exchange 2007.
External and Internal DNS settings
Public DNS - Map all of your external public DNS records (ews,owa,activesync etc.,) to your
exchange 2013 public IP if you have dedicated one for 2013 or FQDN of your internet facing CAS server.
Example:
Current external owa URL (contoso.domain.com) – point it to dedicated exchange 2013 public ip or internet facing exchange 2013 CAS FQDN.
Current External Autodiscover – point it to dedicated exchange 2013 public ip or internet
facing exchange 2013 CAS FQDN
Internal DNS – Configure the Exchange 2007 to point SCP AutoDiscoverURI to Exchange 2013 Client
Access FQDN by changing DNS entry for Autodiscover.domain.com to exchange 2013 CAS sever Ip
address
The internal DNS records should point to the internal host name and IP address of your Exchange
2013 Client Access server
Make sure that legacy.contoso.com resolves to CAS2007 in internal and external DNS.
Authentication Settings:
This part is little bit tricky. You need to plan according to your organization. If you have FBA configured in TMG or ISA server then you need to configure accordingly.
Set the owa virtual directory authentication only to Basic in exchange 2007.
In exchange 2013 set owa virtual directory to only (Windows Authentication) or only (form-based authentication) or only (Basic, No redirection, SSL Enabled) depends according to your setup.
Things to check:
If you have redirection configured in IIS on the Exchange 2007 Server Make sure that the above
Virtual Directories doesn’t have it configured.
If you have FBA enabled on ISA or TMG then disable FBA on Exchange 2013 CAS else users will be prompted twice for authentication
For further references you can refer my article below
http://exchangequery.com/2014/09/24/owaews-configuration-in-exchange-20132007-coexistence/
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

Send As, Send on Behalf and Full Access for Exchange server 2010/2013

[This FAQ contains 2 parts]
Testing and watching the behavior of Send As, Send On Behalf and Full Access permission.
Common issue and Troubleshooting on the three permission.
[Testing and Watching]
Based on following blog, I decide to test on my lab:
Full Mailbox Access Rights + Send On Behalf = Send As ?
http://blogs.technet.com/b/ehlro/archive/2012/04/06/full-mailbox-access-rights-send-on-behalf-send-as.aspx
Description on my lab and test:
Exchange 2010 + Outlook 2010
Exchange 2013 + Outlook 2013
Senders: A01, A02, … , A07, A08
Recipient: A09
A01 grand permission to other senders.
Two methods:
a. Use A0x’s credential configure A01’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
b. Use A0x’s credential configure A0x’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
Result as following forms:
1. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A01’s mailbox, then send From both A01 and A0x
To A09.
2. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A0x’s mailbox, then send From both A01 and A0x
To A09.
[Common Issue]
1. [Issue]
Exchange 2010 + Outlook 2010. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
You can’t send a message on behalf of this user unless you have permission to do so. Please make sure you’re sending on behalf of the correct sender, or request the necessary permission. If the problem continues, please contact your helpdesk.
Details as following pic:
[Troubleshooting]
1) Based on the NDR, it seems a permission issue. Check Send As permission, however the Send As permission configured correctly. Pic as below:
2) ince the Send As permission configured correctly, it seems the permission hasn’t been replicated. Try to restart Microsoft Exchange Information Store service. It works.
Note: The Send As permission isn’t granted until after replication has occurred. Replication times depend on your Exchange and network configuration. To grant the permission immediately, stop and then restart the Microsoft Exchange Information
Store service.
2. [Issue]
Exchange 2013 + Outlook 2013. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
Your message did not reach some or all of the intended recipients.
Subject: xxx
Sent: xx/xx/2014 8:20 AM
The following recipient(s) cannot be reached: A09
This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000].
Details as below:
[Troubleshooting]
1) Also check the Send As permission configuration first.
2) Then try to use A03 send as A01 to A09 via OWA. If OWA works well, it seems and issue on the Outlook client side.
3) This behavior may occur if the OAB in Outlook isn’t updated. Try to download OAB manually.
4) If doesn’t work, please close Outlook and try to delete all the OAB folder on your computer. The path of OAB folder in Win7, Win8 as below:
\Users\<UserName>\AppData\Local\Microsoft\Outlook\Offline Address Books
5) Restart Outlook.
Note: Be aware that you cannot send e-mail messages on behalf of a mailbox if the mailbox is hidden from address list. When sending a message, Exchange requires that e-mail address is resolved in the
From field.
3. [Issue]
Exchange 2010. A01 grant A0x “Send As” or “Send on Behalf” permission. A0x send as/ send on behalf of A01. The message is only copied to the Sent Items folder in A0x’s mailbox (same as the result of my test). Also cannot configure Exchange 2010 so that the
message is copied to the Sent Items folder of both A01 and A0x.
[Troubleshooting]
This issue occurs because Exchange server 2010 was designed to copy message to the Sent Items folder of the sender only. This issue can be solved by installing Exchange 2010 SP2 UR4. More details in the following KB:
Messages that are sent by using the "Send As" and "Send on behalf" permissions are copied only to the Sent Items folder of the sender in an Exchange Server 2010 environment
http://support.microsoft.com/kb/2632409/en-us
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Nice guide Mavis, I recently explored the same topic. Few things you might want to add is the type of connectivity (Cached vs Online will produce different results) and to expand further on the methods of adding the other mailbox in Outlook (additional mailbox
vs additional account defaults to different methods). Check the screenshot:
And please post this somewhere more visible, like blog/wiki page.

Exchange 2003 /2010 Co-existence plus 2010 migration to new hardware

Hi,
Here is our current scenario;
Exchange 2003/2010 co-existence. This has been running perfectly for a couple of months now.
Exchange 2003 - exch1.domain.lan
Exchange 2010 (SP3) - exch2.domain.lan (local domain name) / mail.domain.com.au (external domain name)
ActiveSync, autodiscover, legacy etc are all working. Our UAC certificate from GoDaddy has all the required names for exch2 - except it doesn't have the local domain name as they don't allow certificates with that anymore. I've configured all the required
services to be the external domain name and am running split DNS.
The first Exchange 2010 server I installed was lower spec'd and only has about 25 users on it. I now need to install a second Exchange 2010 server (exch3.domain.local), which is properly spec'd and will host the entire company. I won't be running DAG as
I need to repurpose the first Exchange 2010 server once it's removed.
My high level questions are;
1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
OR does it matter which way I do it?
I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange
organisation.
1) Do I configure CAS to be externally facing right from the get go or do I do that later?
2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
Any guidance on the above is helpful.
Thanks.
Steve

Hi Steve I will try my best to answer each of these
My high level questions are;
1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
OR does it matter which way I do it?
doesn't matter at all. Since you want to move to a new hardware you can setup a new Server CASH/HUB/Mailbox. Once installed start migrating the mailboxes from Exchange 2003 to this mailbox server. This way you will not have to redo the migration from 2010
to new 2010 sever -- like you mentioned in 1) it will save you a lot of time and repeating procedure.
I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange organisation.
1) Do I configure CAS to be externally facing right from the get go or do I do that later?
Keep your existing 2010 internet facing for now. Once you finished migrating the mailboxes then you will need to do it.
2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
Mail will not flow to 2ndry server unless you add that server as a source serve in the transport.
In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
You can always export the certificate and then import it to the newly installed Exchange 2010.
OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
You will only need to setup the CAS array if you are going to use both the server which can be done later.
Hope that help
Where Technology Meets Talent

Converting a VBScript for Exchange 2003 to Function the same for Exchange 2010

Converting a VBScript for Exchange 2003 to Function the same for Exchange 2010
Afternoon;
I've run into a problem at this time. We are currently looking into migrating from Exchange 2003 into Exchange 2010 and I'm finding that my normal data collection method is no longer usable in Exchange 2010. I have the script posted below as of
what I'm currently using to collect my information, I just need to know of a means to continue the collection when we move to the new Exchange server. Any assistance in getting this to function with Exchange 2010 would be great.
++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++
On Error Resume Next
'Date Stamp for File Name
Function TIMESTAMP
strDate = CDate(Date)
strDay = DatePart("d", strDate)
strMonth = DatePart("m", strDate)
strYear = DatePart("yyyy", strDate)
If strDay < 10 Then
    strDay = "0" & strDay
End If
If strMonth < 10 Then
    strMonth = "0" & strMonth
End If
TIMESTAMP = strYear & strMonth & strDay
End Function
'Drop Location Vars Set
DRP01 = 1
DRP02 = 1
'Live Check SQL04
strVIC = "SQL04"
Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\.\root\cimv2")
Set colItems = objWMIService.ExecQuery ("Select * from Win32_PingStatus Where Address = '" & strVIC & "'")
For Each objItem in colItems
    DRP01 = objItem.StatusCode
Next
'Live Check FS02
strVIC = "FS02"
Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\.\root\cimv2")
Set colItems = objWMIService.ExecQuery ("Select * from Win32_PingStatus Where Address = '" & strVIC & "'")
For Each objItem in colItems
    DRP02 = objItem.StatusCode
Next
'Setup STOREDIR Location
If DRP01 = 0 Then
    STOREDIR = "\\SQL04\Email\Collected\" 'Primary Data Storage Location
    Else
    If DRP02 = 0 Then
        STOREDIR = "\\FS02\Shared\MIS\Daniel\" 'Secondary Data Storage Location
        Else
        STOREDIR = "C:\Scripts\Logs\" 'Tertiary Data Storage Location
    End If
End If
'STOREDIR Check for Availability
Set fso = CreateObject("Scripting.FileSystemObject")
If fso.FolderExists(STOREDIR) Then
    AVAIL = 1
    Else
    AVAIL = 0
End If
'Sets Failsafe STOREDIR
If AVAIL = 0 Then
    STOREDIR = "C:\Scripts\" 'Last Chance DIR for Data Files
End If
'Sets Filename
FILENAME = TIMESTAMP & ".csv"
'Testing Purposes Only
'wscript.echo TIMESTAMP
'wscript.echo STOREDIR & vbNewLine & FILENAME & vbnewline & vbnewline & AVAIL
'Sets Process Variables
cComputerName = "EXCH02" ' Exchange Server Name or IP Address
DIM fso, ObjFile
Set fso = CreateObject("Scripting.FileSystemObject")
Set ObjFile = fso.CreateTextFile(STOREDIR & FILENAME, True)
'ObjFile.WriteLine("Date,Display Name,Size(KB)")
Const cWMINameSpace = "root/MicrosoftExchangeV2"
Const cWMIInstance = "Exchange_Mailbox"
Dim strWinMgmts
Dim objWMIExchange
Dim listExchange_Mailboxs
Dim objExchange_Mailbox
strWinMgmts = "winmgmts:{impersonationLevel=impersonate}!//" & cComputerName &"/" & cWMINameSpace
Set objWMIExchange = GetObject(strWinMgmts)
'Checks for Email Record and Records to File
If Err.Number <> 0 Then
ObjFile.WriteLine("ERROR:" & VBNEWLINE & Err.Number & VBNEWLINE & Err.Description)
Else
Set listExchange_Mailboxs = objWMIExchange.InstancesOf(cWMIInstance)
If (listExchange_Mailboxs.count > 0) Then
    For Each objExchange_Mailbox in listExchange_Mailboxs
       ObjFile.WriteLine(TIMESTAMP & "," & objExchange_Mailbox.MailboxDisplayName & "," & objExchange_Mailbox.Size)
    Next
Else
    ObjFile.WriteLine("WARNING: No Exchange_Mailbox instances were returned.")
End If
End If
ObjFile.Close
VBScript is what I prefer. All scripts must have a kill switch to manage them from a primary location. Mine, is an updater method.
VBScript is what I prefer. All scripts must have a kill switch to manage them from a primary location. Mine, is an updater method.

Okay, then what about an alternative for getting the same result. The file associated in the article is too much. All we need is something simple for a single exchange server with 180 users. We only need to pull UserName and DataSize(KB).
I only need to collect two pieces of information from the exchange server and the third piece is forced due to the date of when the information was collected. This way I can sort and filter by Date and Name to see a trend of the users mailbox usage
size.
Every day this runs, it determines the date of the file which is also the first piece, then pulls from the exchange server the entire list of users (the second piece), and then the respective user's mailbox size in KB (the third piece). This all is
dropped into a CSV file later used to import into a database before being archived, done by a second task on the server. Later used by a shared Excel PowerPivot document among the department.
Those of us in the server admin group use this to, at a glance, see the collective size of email usage on the server. Mainly used as a means of catching an incident before it happens. We are currently keeping our users around a collective 80GB
of use out of the well received limit of 110GB on Exchange 2003 and limiting the user's ability to send and receive email by email quota is apparently not accepted for us to do. So we use this to determine who we need to visit and force archive their
email so the server doesn't fail due to the size limit.
VBScript is what I prefer. All scripts must have a kill switch to manage them from a primary location. Mine, is an updater method.

Exchange 2003 -2010 cross forest (NDR 5.4.6)

Hi.
Have: Exchange 2003+2010 in source forest. Exchange 2010 in target forest.
Successful migrate mailbox to target forest (in source forest this mailbox convert to mailuser).
When try send e-mail to this mailbox (it`s in target forest) from Exchange 2003 mailbox get this:
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients.
If send from Exchange 2010 (source/target) - all mail ok.
If delete this mailuser (in source forest) - all set to ok.
x500?
Please, help.
Thanks.

Hi,
In the error event, 5.4.6 means "Routing loop detected" (RFC1893).
This issue occurs if the source Exchange organization is authoritative for the target domain. Because the source Exchange organization is responsible for mail delivery to target, the categorizer tries to find locally a recipient for
that message. The categorizer does not succeed, and then you receive the NDR.
More details in the following KB:
You receive an NDR with a 5.4.6 status code when you send a message to a specific domain in Exchange
http://support.microsoft.com/kb/324732/en-us
Hope it is the solution.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Microsoft Exchange Server 2010 SP3 update to Update Rollup 8-v2 for Exchange Server 2010 SP3

i have Microsoft Exchange Server 2010 SP3 and i would like to update to Update Rollup 8-v2 for Exchange Server 2010 SP3.
what is the best way to do so?
my current env:
Name : xxxxxxxx
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, HubTransport
Site : domain/Configuration/Sites/xxx
Name : yyyyyyyy
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, ClientAccess, HubTransport
Site : domain/Configuration/Sites/yyy
Name : cccccccc
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, ClientAccess, HubTransport
Site : domain/Configuration/Sites/ccc
Name : dddddddd
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : ClientAccess
Site : domain/Configuration/Sites/ddd
Name : iiiiiiii
Edition : Standard
AdminDisplayVersion : Version 14.3 (Build 123.4)
ServerRole : Mailbox, ClientAccess, HubTransport
Site : domain/Configuration/Sites/iii
thanks
Mayson

Consider referring to the articles below and that explains it all.
Install the Latest Update Rollup for Exchange 2010 - https://technet.microsoft.com/en-us/library/ff637981.aspx
Applying Service Pack and Rollup Updates on Exchange Server 2010 (Part 1) - http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/applying-service-pack-and-rollup-updates-exchange-server-2010-part1.html
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

Uninstall Rollup 4 for Exchange Server 2010

When one of our CAS servers got patched they installed Rollup 4 for Exchange Server 2010 SP3.
Is it ok to unintall the Rollup 4 update? I am not able to update other servers for another month and I need all servers to have the same build.

Hi dirkbucket,
Yes you can go ahead and uninstall the rollup from the exchange server that got installed. This will not result any impact. Once uninstalled please perform complete reboot.
As uninstallation of patches is applicable till Exchange 2010 version on getting them reverted.
"To remove Update Rollup 3 for Exchange Server 2010 RTM, use Add or Remove Programs in
Control Panel. Then, remove update 981401."
Find the url for ref: http://support.microsoft.com/kb/981401/en-us
In Exchange 2013 you will not able to perform reverting of CU other than rebuilding it :(
Exchange Queries

Does anyone know if iOS 7 has support for Exchange 2003?

Does anyone know if iOS 7 has support for Exchange 2003?

All previous versions of iOS have had support for Exchange 2003. Of course, more functionality is available with Exchange 2007/2010 support than 2003, but that's due to limitations in what the protocols support.

Any known issue reported for "Rollup 8 for Exchange Server 2010 Service Pack 2"

Hello,
Currently our servers are running with "Exchange 2010 SP2 RU7", we are planning to update the Rollup version to RU8 for SP2.
Is there any knows issues reported for "Rollup 8 for Exchange Server 2010 Service Pack 2" till now ? is it safe to update the RU8 ?
http://www.microsoft.com/en-us/download/details.aspx?id=41394

(1) I had to roll it back:
The rollup released Tuesday the 9th caused random problems with systems ranging from general slow down to operation failed errors. It didn’t impact everyone at once and seemed to take 48hrs for everyone to have a problem. Rolling
back the update and rebooting the server seemed to resolve the issue.
Issues reported before the general mailflow stopping for everyone:
Nothing major … an occasional operation failed when I hit send but, it will go thru after I hit the send button a couple of times.
A MICROSOFT OUTLOOK BOX APPEARS WITH A TRIANGLE WITH A ! INSIDE IT. THE MESSAGE SAYS THE OPERATION FAILED.
(2)
ANOTHER CODE APPEARED WHEN I TRIED TO SEND THIS E-MAIL SO I CLOSED OUTLOOK AND RE-STARTED OUTLOOK. THE MESSAGE READ, CANNOT CREATE THE E-MAIL MESSAGE BECAUSE A DATA FILE TO SEND AND RECEIVE MESSAGE CANNOT BE FOUND. CHECK YOUR SETTINGS IN THIS MICROSOFT
OUTLOOK PROFILE. IN MICROSOFT WINDOWS, CLICK CONTROL PANEL.CLICK USER ACCOUNTS AND THEN CLICK MAIL. CLICK SHOW PROFILE, AND THEN CLICK PROPERTIES.
When he tries to open an e-mail, he gets an error message.
If he tries to mark an e-mail unread, he gets a different message.
Thanks Ben

Exchange 2010 Mailbox automapping issues after updated to Rollup 5 for Exchange Server 2010 SP3

Hi,
i have problem with Outlook Uses who have Full Access on other mailbox.
An authentication window pop up very time a user start Outlook.
If i remove the access everything is ok.
if i insert manual the mailbox everything is ok
The System was for 3 days ago updated to Rollup 5 for Exchange Server 2010 SP3
Before the update, was no issue.
i will appreciated any help
Thanks

Same issue here. Ever since we installed Update Rollup 5 for SP3 Exchange 2010 mailboxes that were auto mapped are not accessible. They all get the same error.
Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to the Microsoft Exchange has failed.
What I have been doing is removing the users permission, then adding them back using the noautomap switch in Powershell. After doing that, the user manually adds the mailbox and all is well.
Just a note here, I suspect it may have something to do with the version of Outlook 2010. We are running an older version here. I think only SP1 with no other incremental updates. Office is up to SP2. Also, one of the users I was working with could not access
the mailbox no matter what we tried but she can walk over to another workstation and open Outlook and access the very same mailbox so that pretty much proves its software related particularly with Outlook.
I cannot reproduce the problem on a workstation (XP) with a newer version of Outlook.
This has been wearing me out and I suspected the Update Rollup all long. Now I am confident as others are having the same problem. If you find out anything on how to fix this other than the steps above, let me know.

Exchange 2003-2010 co-existence environment

i have exchange 2003 -2010 co-existence environment .
Everything works fine accept below;weird issue,i tried to re-create routing group connector but issue is same.
My issue is very simple,The mail flow as below:
exchange 2003 to outside............
exchange 2010 to outside ...........works
exchange 2010 to 2003 ...............works
exchange 2003 to 2010................is not

Hi Huzefa,
Can you try creating a new bidirectional RGConnector and check?
New-RoutingGroupConnector -Name "NameOfRG" -SourceTransportServers "Ex2010.contoso.com" -TargetTransportServers "Ex2003.contoso.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $true
http://technet.microsoft.com/en-us/library/aa997292(v=exchg.141).aspx
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Installing Update Rollup 7 for Exchange Server 2010 SP3

Hi,
I have 4 Exchange servers. Two CAS and two DAG. I am currently on Rollup 2 for Exchange Server 3010 SP 3. Can I install Update Rollup 7 for Exchange Server 2010 SP3 or do I need to install a previous one first?
Thannks!
Wave~Chaser

Hi,
When I try to install Exchange 2010 SP3 roll up 7, am getting the below error:
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may
be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
and please find below event log:
Product: Microsoft Exchange Server - Update '{A93DA06F-A5B8-4DF8-8B3F-B285E014C659}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions
on turning on logging support.
Can you please help me with this error.
Thanks

Exchange 2010 update after Update Rollup 5 for Exchange Server 2010 (KB2407113)

Mine exchange server 2010 standard has Update Rollup 5 for Exchange Server 2010 (KB2407113) as latest update.
Can someone help me which update i can install after this, can i start with
Update Rollup 1 for Exchange Server 2010 SP1.
Many thanks in advance

My recommendation will be:
Remove update roll-up 5
Install SP1 check that everything is working
Install SP2 check that everything is working
Install SP3 check that everything is working
I think it will be risky for you to go straight to SP3.
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Exchange 2003 - 2010 Co-existence Migration Autodiscover & OAB Issue

Hi,
I am in the middle of a Ex2003 to Ex2010 Migration initially through co-existence. Everything has been working perfectly for the last couple of months.
The first Ex2010 server I installed (EX01.domain.local) was just a temporary server that hosted a handful of users that were imported from another company.
I have since installed a second Ex2010 server (EX02.domain.local), which will be the permanent 2010 server. The end result will be 1 Ex2010 server only, after I have migrated everyone off EX01 and the 2003 server.
EX01 and EX02 both have the Mailbox, CAS, & HT roles installed.
I created the mailbox and Public Folder databases on EX02. I have assigned the Public Folder database to the mailbox database.
I added EX02 as a Source Server within Hub Transport.
I've exported the UC/SAN certificate from EX01 and imported it into EX02 and assigned the SMTP, IIS, POP & IMAP services to it.
I setup the legacy URL for OWA.
I changed the relevant settings on EX02, eg OWA, ECP, ActiveSync, OAB, AutoDiscoverServiceInternalUri etc to be external domain name that is listed on the certificate, eg mail.domain.com.au. (The SSL certificate is through GoDaddy and they do not allow you
to put any internal domain names on the certificate).
So before I installed the second Ex2010 server, everything was working correctly.
After I installed the second Ex2010 server and performed the steps above, I have noticed a couple of things;
1) The Autodiscovery test within Outlook works for mailboxes that have been migrated to either of the Ex2010 servers, but fails for mailboxes that are still on the Ex2003 server. It finds the correct URL, https://mail.domain.com.au/Autodiscover/Autodiscover.xml,
and brings back an HTTP status of 200. However, it says it then fails with (0x800C8203). I tested with Outlook 2003 and 2010. They both fail.
2) OAB fails to download for clients whose mailbox is still on the Ex2003 server. It fails with (0x8004010F - The operation failed. An object cannot be found). It works for clients with mailboxes on either of the 2010 servers.
I'm going around in circles reading numerous articles on trying to fix autodiscover. Using Microsoft's MRCA site, autodiscovery works externally for clients on the Ex2010 servers, but not on the 2003 servers, (which I thought was how it worked anyway as
autodiscovery doesn't work on Ex2003).
Is this the same for internal users. I'm not sure if I'm chasing my tail by trying to fix something that doesn't need fixing, but obviously the OAB should work.
Any suggestions are grateful.
Thanks.
Steve

Output from get-webservicesvirtualdirectory | fl
RunspaceId
: 12158f4a-101e-45c7-b35a-02c6b5652e41
CertificateAuthentication :
InternalNLBBypassUrl
: https://ex01.domain.local/ews/exchange.asmx
GzipLevel
: High
MRSProxyEnabled
: False
MRSProxyMaxConnections : 100
Name
: EWS (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication
: True
LiveIdBasicAuthentication : False
BasicAuthentication
: True
DigestAuthentication
: False
WindowsAuthentication
: True
MetabasePath
: IIS://EX01.domain.local/W3SVC/1/ROOT/EWS
Path
: C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags
ExtendedProtectionSPNList : {}
Server
: EX01
InternalUrl
: https://mail.domain.com.au/ews/exchange.asmx
ExternalUrl
: https://mail.domain.com.au/EWS/Exchange.asmx
AdminDisplayName
ExchangeVersion
: 0.10 (14.0.100.0)
DistinguishedName
: CN=EWS (DefaultWebSite), CN=HTTP, CN=Protocols, CN=EX01, CN=Servers, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Administrative Groups,CN=CompanyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Identity
: EX01\EWS (Default Web Site)
Guid
: fd59fcca-87aa-4c7c-87d9-6ddeef4ca9e9
ObjectCategory
: next.lan/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass
: {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged
: 28/03/2014 11:25:50 AM
WhenCreated
: 29/12/2013 9:42:33 AM
WhenChangedUTC
: 28/03/2014 12:25:50 AM
WhenCreatedUTC
: 28/12/2013 10:42:33 PM
OrganizationId
OriginatingServer
: DC2.domain.local
IsValid
: True
RunspaceId
: 12158f4a-101e-45c7-b35a-02c6b5652e41
CertificateAuthentication :
InternalNLBBypassUrl
: https://ex02.domain.local/ews/exchange.asmx
GzipLevel
: High
MRSProxyEnabled
: False
MRSProxyMaxConnections : 100
Name
: EWS (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication
: True
LiveIdBasicAuthentication : False
BasicAuthentication
: True
DigestAuthentication
: False
WindowsAuthentication
: True
MetabasePath
: IIS://EX02.domain.local/W3SVC/1/ROOT/EWS
Path
: C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags
ExtendedProtectionSPNList : {}
Server
: EX02
InternalUrl
: https://mail.domain.com.au/EWS/Exchange.asmx
ExternalUrl
: https://mail.domain.com.au/ews/exchange.asmx
AdminDisplayName
ExchangeVersion
: 0.10 (14.0.100.0)
DistinguishedName
: CN=EWS (Default Web Site), CN=HTTP, CN=Protocols, CN=EX02, CN=Servers, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Administrative Groups,CN=CompanyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Identity
: EX02\EWS (Default Web Site)
Guid
: e592adcd-18c2-4c4b-bd89-fca95e9e9622
ObjectCategory
: next.lan/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass
: {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged
: 28/03/2014 10:50:54 AM
WhenCreated
: 27/03/2014 10:34:27 AM
WhenChangedUTC
: 27/03/2014 11:50:54 PM
WhenCreatedUTC
: 26/03/2014 11:34:27 PM
OrganizationId
OriginatingServer
: DC2.domain.local
IsValid
: True

Namespace for Exchange 2003 == 2010 == 2013 Migration

Similar Messages

Maybe you are looking for