EXCH 2003 2010 Transition, /PrepareLegacyExchangePermissions failure.

I've searched and searched and cannot find the same scenario with a resolution to this problem.
We have planned the transition of Exch 2003 to 2010 but have not accounted for a scenario during test, now we are supposed to be beginning the role out and it has bitten us in the rear!
We have a Single Forest, multi domain setup (almost 50 domains), with an existing 2003 Exch Org. These domains are worldwide and are not online all the time, in fact the possibility to bring them online together is almost 0 due to the nature of the organisation
I work for.
When running Setup /p and setup starts the PrepareLegacyExchangePermissions we receive several errors about being unable to contact the domains that are offline. We cannot continue with these errors. However, there is no way we can bring all Domain online
at the same time to complete the AD Prep.
We are running the stup on a W2K8 R2 member server in the same site as the Exchange Root as you would expect.
Does anyone know of a workaround for this, can we specify to ignore the offline nodes when running setup /p? Then carry out the /PrepareLegacyExchangePermissions on these nodes when they are available? I would rather not publish the logs as it would
take me ages to saitise them.
Just to clarify, there is nothing wrong with the steps being completed or how we are doing it, this error is related purely to the fact that not all domains can be contacted.
Thanks in advance for your responses.

Hi,
I would like to clarify the following things to answer your questions:
1. The server where you run setup /PrepareLegacyExchangePermissions contacts the local global catalog to locate the domains in which you have run Exchange Server DomainPrep by checking for the EES and Exchange Domain Servers groups.
2. The server should be able to communicate with every domain in the forest in which you ran Exchange Server DomainPrep.
3. The account that you use to run setup /PrepareLegacyExchangePermissions must have the permissions assigned to the Enterprise Admins universal security group so that it can set the ACEs in each domain and in the Exchange organization.
Hope my clarification is helpful.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Similar Messages

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

Shared smtp namespace in mixed environment (2003 & 2010)

Hi,
I have a mixed exchange enviornmnement (2003+2010).
As far as I know in exchange 2010 we use internal relay for shared namespaces. And "This Exchange Organization is responsible for all mail delivery to this address" in ex 2003 recipient policies.
My question is : when set the option on one side (2003 or 2010) will it be applied to the other side(other version) automatically?
Thanks

Hi,
Yes. Based on my knowledge, it will trust each other automatically.
Thanks
Mavis
Mavis Huang
TechNet Community Support

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

Migration from 2003 - 2010, OAB errors on client, and OAB virtual directory does not contain any files.

Migration from 2003 - 2010, OAB errors on client, and OAB virtual directory does not contain any files.

Hi,
Please re-create the Outlook profile to have a try. If the issue persists, we can do the further checks in Exchange server.
Please make sure you have changed the OAB generation server to Exchange 2010 and enable Web distribution on the Exchange 2010 Client Access server:
Move-OfflineAddressBook "Default Offline Address List" -Server <MBX2010>
If all configurations are correct, please check whether there is any folder in the following path in Exchange sever 2010:
a. OAB generation in Mailbox:
\\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB
b. OAB distribution in Client Access:
\\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB
Thanks,
Winnie Liang
TechNet Community Support

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.

Exchange 2003/2010 Coexistance - User login Issue

Hello
We have deployed Exchange 2010 SP3 in coexistance with 2003 and created connectors.
2003/2010 both Users are not able to login on 2010 OWA and error showing that username/PW is wrong although they are working on OWA 2003 perfectly.
When i add the same user to the local admin group on the Ex2010 server, it works fine with email send/receive. i am confused please suggest what i am missing....Regards
Waseem

Hello
This is the error that occured during that time.
SACL Watcher servicelet encountered an error while monitoring SACL change.
Got error 1722 opening group policy on system SERVER.DOMAIN in domain MYDOMAIN.
Event ID 6003
Source : MSExchange SACL Watcher
i am not sure if its related to this problem.
Secondly i have also tested to run the "Microsoft Exchange Active Directory Topology Service" with a new user having all the rights of exchange & AD groups but its showing giving the error that it cant run the dependency
services. currently this service is running with the local account rights.
I just add the test users (moved from 2003 and new user created in 2010) to the local admin group and it works fine, please give any idea what may be the problem in rights or something else ??
Regards
Waseem

2003/2010 co-existence - is it safe to create recipient policies under 2010?

I'm pretty sure this won't affect anything, but just want to be 100% sure.
Exchange 2003/2010 are in co-existence happily working away
The existing Exchange 2003 recipient policies are a real mess
To save having to fix them all up, the plan is to just create new ones under Exchange 2010 and scope them to apply for users on 2010
When all users are moved to 2010, the old ones can be removed which saves having to upgrade them to all to 2010 format which is another bonus
Will creating new recipient policies under 2010 apply to recipients on 2003 or force the 2003 policies to run again somehow against existing users, or can recipient policues under 2010 be set to only apply to users in 2010 using a custom attribute for example
and when users are moved to 2010 with the custom attribute the policy can be enforced at that time? All the current polices are set to applied = false under 2003.

I have experience with messing up in this scenario :) in a 20,000 user environment.
E-Mail address policies are shared across the Exchange Organization so you will see ones created in 2010 in 2003, although you won't be able to edit those. Having the 2003 policies set to false means that they haven't been applied in some time and
its best not to touch during the migration. My first step here (after making a mistake) is to Disabled the Automatic Email Update for all mailboxes. I can look up how I did this on a mass scale a little later.
I then created the policies in 2010 to use a custom attribute, as you had suggested, and when mailboxes were migrated over, I made sure those accounts had the Attribute and then checked the box to auto apply the address policy.
Someone else may have a better answer for you, but this is how I saved my butt in a larger organization.
Jason Apt, Microsoft Certified Master | Exchange 2010
My Blog

Exchange 2003 - 2010 Local Mail box move Error

Hey everyone,
I have just finished a transition from Microsoft Exchange 2003 to 2010, and I am having problem with moving the Legacy mailboxes over.
I have managed to move all the mail boxes over bar 2, using the " New local move Request".
So the problem is just these 2 mail boxes with the same error as below.
Any Advice?
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:39
Sifiso Mguni
Failed
Error:
Service 'net.tcp://tvt-exchange.vtrust.local/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: MapiExceptionLogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=131]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x80040111
    Lid: 26937
    Lid: 21921   StoreEc: 0x80040111
    Lid: 31418   --- ROP Parse Done ---
    Lid: 22753
    Lid: 21817   ROP Failure: 0x80040111
    Lid: 26297
    Lid: 16585   StoreEc: 0x80040111
    Lid: 32441
    Lid: 1706    StoreEc: 0x80040111
    Lid: 24761
    Lid: 20665   StoreEc: 0x80040111
    Lid: 25785
    Lid: 29881   StoreEc: 0x80040111
Exception details: MapiExceptionLogonFailed (80040111): MapiExceptionLogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=131]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x80040111
    Lid: 26937
    Lid: 21921   StoreEc: 0x80040111
    Lid: 31418   --- ROP Parse Done ---
    Lid: 22753
    Lid: 21817   ROP Failure: 0x80040111
    Lid: 26297
    Lid: 16585   StoreEc: 0x80040111
    Lid: 32441
    Lid: 1706    StoreEc: 0x80040111
    Lid: 24761
    Lid: 20665   StoreEc: 0x80040111
    Lid: 25785
    Lid: 29881   StoreEc: 0x80040111
Exchange Management Shell command attempted:
'vtrust.local/Valley Trust Users/Users/Staff/Sifiso Mguni' | New-MoveRequest -TargetDatabase 'Mailbox Database 0271422377'
Elapsed Time: 00:00:39

HI. I had the same problem while trying to migrate a user from Exchange 2003 to 2010. And the same error as you have appeared. I tried to skip more e-mails in case some fails but couldn't get successful.
Check if the user have accessed the mail at all on Exchange 2003 because if the user didn't accessed it it may contain many mails and when we try to migrate the mailbox, the mailbox size on Exchange 2003 may be grater than on the 2010.
On my case after many reading we just see that the user didn't access the mail at all on our Exchange 2003. (Let me know if you need to know how you can check if the user accessed the mail or not or you can just google it). So what we have done is we just
reset the user password on Active Directory. Because as you can see the error is related with Logon Failure.
This solved the issue for me. Can you check this way
Thanks

Exchange 2003 - 2010. Moving public folders one at a time

Hi all,
I'm in the process of decomisioning our old Exchange 2003 server (long overdue after what has been a relativly smooth and trouble free transition to 2010). As the first step in the decomisioning process, I'm looking to move the public folders from the 2003
box to the 2010 box. From my understanding there are a couple of ways to achieve this (please correct me if I'm wrong). The first is to add the Exchange 2010 server as a new replication partner, allow for replication of the PFs to occur, and then remove the
2003 partner from the replication partnership. The other option is to use MoveAllReplicas.ps1.
I opted for the first option, but the problem I have is that the initial replication process started to generate a very large number of transaction logs on the Exchange 2010 server, to the point I was slightly conccerned I was going to run out of space on
the volume (our server is backed up nightly at which point the transaction logs are normally flushed).Whilst I know I could potentially increase the size of the volume or turn on cicular logging for the duration of the migration (neither of which is appealing
as it will involve down time), I was wondering if there was a way to move a smaller set of Public folders one at a time with a powershell command, or is it an all or nothing operation? My other option may be to replicate a small subset of folders everyday,
but that just a little painful as there are a large number of child folders with in the structure. Any other suggestions welcome!
Many thanks,
Rob

Hi,
If your Public Folder Database is large, you can use tool like Exfolders or ESM to add replica folder by folder.
A related article for your reference.
http://careexchange.in/moving-public-folders-from-exchange-2003-to-exchange-2010/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or
suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
And it is recommended to replicate public folders off business hours.
Best regards,
Belinda Ma
TechNet Community Support

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."

Exchange 2007 to Exchange 2010 Transition

I am in the process of transitioning a client from Exchange 2007 to 2010(clients are XP/Win 7 with Outlook 2007/Outlook 2010). I know if have to extend the schema for Exchange 2010 and there will be co-existence throughout the process. At this point, Outlook
profile on users are point to either IP or netbios name of the server and their credentials. When I move their mailbox(in Exchange 2010 migration wizard), do I have to go to each Outlook and repoint their profile to the new netbios name of the Exchange 2010?

Outlook 2007 and newer will use a combination of AutoDiscover and redirection to update the client profile from the existing settings to the new server supporting their mailbox. Just make sure you have DNS resolution for autodiscover and the new
server names.
Gary A. Cooper | Senior Systems Architect | MCA:Exchange 2003/2007/2010 | MCM:Exchange 2003/2007/2010 | Horizons Consulting, Inc. If you have found my answer helpful, please vote as such.

Exchange Server 2003/2010 Coexistence Mail-flow Issues

I've installed Exchange 2010 in a 2003 coexistence scenario.
2010 was deployed with CAS,HUB, and Mailbox roles.
The installation went through smoothly, and the default RGC was created.
On the 2010 Server, when I create a new users with mailbox, that user is no able to send or receive mail from anywhere.
2010 user to 2010 user does not work
2003 user to 2010 user does not work
Mail delivery between 2003 users works fine.
The RGC message queue in ESM 2003 shows that the messages are queued and keep retrying.
I have deleted the RGC twice and created new ones, I have un-installed the HUB and CAS roles and re-installed them, and I have also re-run setup /preparead and setup /preparelegacyexchangepermissions
I'm not able to make any sense of the message tracking on the 2010 side. It just shows a bunch of entries:
EventID: NOTIFYMAPI
Source: STOREDRIV
When I use the best practices analyzer to test mailflow to a 2010 user from the outside, the test comes back with a pass even though the message itself isn't delivered to the specified mailbox.
There is no smart host defined on the default SMTP virtual server on 2003.
There is no SMTP Send Connector for External or Internal mail configured on 2003 besides the 2010 RGC
Any ideas?
Here is the mail flow analyzer result:
Testing inbound SMTP mail flow for domain '[email protected]'.
     Inbound SMTP mail flow was verified successfully.
     Additional Details
Elapsed Time: 3437 ms.
     Test Steps
     Attempting to retrieve DNS MX records for domain 'test.com'.
     One or more MX records were successfully retrieved from DNS.
     Additional Details
MX Records Host mail.test.com, Preference 0
, Host test.com, Preference 10
Elapsed Time: 110 ms.
     Testing Mail Exchanger mail.test.com.
     This Mail Exchanger was tested successfully.
     Additional Details
     Test Steps
     Attempting to resolve the host name mail.test.com in DNS.
     The host name resolved successfully.
     Additional Details
     Testing TCP port 25 on host mail.test.com to ensure it's listening and open.
     The port was opened successfully.
     Additional Details
Banner received: 220 EX2K3w2K3.test.net Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Wed, 5 Feb 2014 14:40:44 -0500
Elapsed Time: 368 ms.
     Analyzing SMTP Capabilities for server mail.test.com:25
     SMTP Capabilities were analyzed successfuly.
     Additional Details
     Attempting to send a test email message to [email protected] using MX mail.test.com.
     The test email message was delivered successfully.
     Additional Details
Elapsed Time: 621 ms.
     Testing the MX mail.test.com for open relay by trying to relay to user [email protected].
     The Open Relay test passed. This MX isn't an open relay.
     Additional Details
     Testing Mail Exchanger test.com.
     This Mail Exchanger was tested successfully.
     Additional Details
     Test Steps
     Attempting to resolve the host name test.com in DNS.
     The host name resolved successfully.
     Additional Details
     Testing TCP port 25 on host test.com to ensure it's listening and open.
     The port was opened successfully.
     Additional Details
     Analyzing SMTP Capabilities for server test.com:25
     SMTP Capabilities were analyzed successfuly.
     Additional Details
     Attempting to send a test email message to [email protected] using MX test.com.
     The test email message was delivered successfully.
     Additional Details
     Testing the MX test.com for open relay by trying to relay to user [email protected].
     The Open Relay test passed. This MX isn't an open relay.
     Additional Details

No duplicate security groups. I did notice Exchange 2010 is not in the Exchange Domain Servers group, but 2k3 is. Not sure if that matters.
In the Application event log I'm seeing this error a lot.
Log Name: Application
Source: MSExchangeMailSubmission
Date: 05/02/2014 3:02:31 PM
Event ID: 1009
Task Category: MSExchangeMailSubmission
Level: Error
Keywords: Classic
User: N/A
Computer: ex2010w2k8.test.net
Description:
The Microsoft Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeMailSubmission" />
<EventID Qualifiers="49156">1009</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-02-05T20:02:31.000000000Z" />
<EventRecordID>6530</EventRecordID>
<Channel>Application</Channel>
<Computer>ex2010w2k8.test.net</Computer>
<Security />
</System>
<EventData>
<Data>HubTransport</Data>
</EventData>
</Event>
As long as you cannot send email between ex2010 users this has nothing to do with connectors/smtp config..
I had the same issue one year ago and solved adding both sevrers to old/new exchange sevrers security groups.
Looks like for some missing security entry (not sure why) mailbox is unable to conact HUB  (MSExchangeMailSubmission) I expect you seing items stuck in draft for owa (outbok for outlook)
I saw in some blogs similar cases solved by setting static DNS servers for HUB severs config.
Yes that is similar to what I'm experiencing.
When using the Outlook client with a 2010 mailbox the mail leaves the outbox fine. When using OWA new messages just get saved as drafts when I try to send them.
I will try your suggestions. I see two groups. Exchange Domain Servers, and Exchange Enterprise Servers of which Exchange Domain Servers is a member.

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

Smartview Excel 2003 / 2010

Hi,
we have some users who have both excel 2003 and excel 2010 installed on the same p.c. with Smartview.
Initial install of Smartview works okay, but subsequently I find that Smartview add-in becomes disabled.
Re-enabling fixes the problem for 2010, but not for 2003 - and even full re-install thereafter does not fix it for me.
Anyone encounted this / have a fix?
thanks for any pointers,
Robert.

Hi Jasmine,
I don't think your fix applies to my version of excel.
i.e. On Excel *2003*
I can go to Tools\Add-Ins
Under there I see => Oracle Hyperion Smartview for Office, Fusion Edition
I can un-tick this option, but there is no 'remove' beyond that.
If I do so I can then browse, but excel expects either .xla or .xll at this point.
Correct me if I am misunderstanding!
regards and thank you,
Robert.

EXCH 2003 2010 Transition, /PrepareLegacyExchangePermissions failure.

Similar Messages

Maybe you are looking for