Hi,

I am working on our Exchange 2010-2013 migration and have come upon an issue after migrating test mailboxes. After migrating a mailbox to the 2013 database I am able to open it in OWA but when I try to open it via Outlook I get the error message "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)". I also get the same message when I create a new mailbox in the 2013 database and try to open it.

I have deleted and recreated the profile on the client. When I create the profile and let autodiscovery configure the information I get a message that the Ex2013 server is not available and the window comes up allowing me to enter the server and mailbox name. If I enter the Ex2013 server name I get the same error whether I enter the hostname of the server or the full DNS name. When I enter the Ex2010 server name it accepts it and converts it to the DNS name of the Ex2013 server but Outlook will still not open.

Both servers are single servers hosting all the roles. The Ex2010 server is using an internal certificate using the internal DNS. When I originally set up the Ex2013 server I did the same thing but have since purchased a SAN certificate based on our public DNS and installed that. The 2 names on the certificate are webmail.(xxxx).com and autodiscover.(xxxx).com. I was getting certificate errors on machines and now I have the SAN certificate that seems to have solved that problem.

I have a feeling I might have 2 problems, 1 with the autodiscover settings and another with the mailbox looking at the 2010 CAS rather than 2013. After doing some research I'm still a little lost in how I move forward on this one. Any help would be appreciated.

Peter Haase

We are currently running Exchange 2013 CU6.  We have multiple application servers relaying bulk mail thru our 4 EX servers. 

We would like to bring up a dedicated exchange server to handle the delivery of smtp application relay mail only.  What would be the steps involved?   

Hi,

We have 1 cas server and 2 mbx servers in a DAG outlook anywhere for internal works flawlessly. We do not use autodiscover externally yet so we set them up manually.

When i use test exchange connectivity and i use the CAS server as servername to connect it gives me the error message:

    

Attempting to ping RPC proxy mail.domain.com. 
  RPC Proxy can't be pinged. 

 Additional Details 

A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
Headers received:
request-id: a932b166-cb19-4feb-b751-f98c4c549279
X-CasErrorCode: MailboxGuidWithDomainNotFound
Persistent-Auth: true
X-FEServer: EXCH-CAS
Content-Length: 0
Cache-Control: private
Date: Fri, 27 Dec 2013 00:29:32 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET

However only when i specifically use the MBX server which holds the active copy of the mailboxdatabase it connects properly without errors. But the casserver should use active manager to see which server holds the active mailboxdatabase automatically doesn't it? I have recently updated to CU3 I have no errors in the eventlogs of both the casserver and the mailbox servers. It doesn't matter which kind of authentication i set in Outlook Anywhere also it doesn't matter wether or not i set the EXCH and EXPR settings of set-outlookprovider. I have tried reinstalling the RPC over http feature and tried resetting virtual directories of the casserver already.

Will this be fixed when i start using autodiscover?

I went to install the CU5 update today and it fails on the step Mailbox role: transport service.

Error:
The following error was generated when "$error.Clear();
          $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
          foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\MFP". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Error:
The following error was generated when "$error.Clear();
          $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
          foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Client Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

When I try to re-run the setup, it fails at the same spot. I can't use the ECP nor the Shell to remove the Receive Connector (it is just a receive connector for the MFP).

Is there any way to remove this receive connector with Powershell not working?

(It looks like this is the problem: http://exchangemaster.wordpress.com/2014/01/24/incorrectly-adding-new-receive-connector-breaks-exchange-2013-transport/ but since I can't get a shell to run in this failed upgrade state I can't take the recommended fix nor just remove the connector.)

Hi,

This is my Folder to Mailbox file, migrating public folders from 2010 to 2013:

"FolderPath","TargetMailbox""\","Hierarchy-PF""\IPM_SUBTREE\Office1","Office1-PF""\IPM_SUBTREE\Office2","Office2-PF""\IPM_SUBTREE\Office3","Office3-PF""\IPM_SUBTREE\Office4","Office4-PF"

All these PF mailboxes live in a dedicated database. But only the mailbox DB containing Hierarchy-PF is growing and my initial migration (New-PublicFolderMigrationRequest / Step 5 in the technet article) is over 50% percent complete. This mailbox is going to be over 300GB big and I gather the limit is 100GB, I'm sure that can be exceeded without problems, but I had several different reasons splitting the mailboxes and data the way I wanted above. 

Questions:

1. How do I achieve the end result I want? Do I need to add a \ to the end of the office1-5 ipm_subtree perhaps?

2. Is there any problem with me stopping the existing migration, deleting that request/mailbox/DB and starting over?

Thanks.

Good afternoon

I currently operate a two node DAG in our primary site supporting one mailbox database. I plan to introduce a third DAG node in our datacenter which is in a different Active Directory site. Both current DAG members replicate over a dedicated replication network to keep the traffic separate from the MAPI traffic. The third DAG member will also have a dedicated replication network adapter (of course, on a different subnet). Ideally I would like to seed the database at a time of my choosing, rather than at the moment I add the mailbox database copy (I know how to achieve this), but I would like to specify which network the data replicates over.

According to the following (see below link) under the 'Seeding and Networks' section as my two DAG members will be on different subnets in different sites Exchange will make the decision to use the MAPI network adapters of the target and source server.

'If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.'

http://technet.microsoft.com/en-us/library/dd335158%28v=exchg.150%29.aspx

Am I able to force Exchange to use the replication network adapters of both source and target server when I initiate the seeding process? I have a 200+ GB mailbox database that will need to replicate over a 100Mbps internet connection to our secondary site and I would like to keep that traffic to the replication network I have configured.

Any insight would be helpful.

I have a Barracuda filter receiving all inbound internet mail which delivers to the edge server (both in DMZ).  I have one 2010 edge server and one 2010 ht,cas,mailbox server.   I have added a 2013 server and started working on configuring virtual directories.  This is a far as I have gotten. Goal is once new box is working to move all mailboxes to 2013 server and remove 2010 mail box server and keep Barracuda and 2010 edge server to pass mail to the 2013 box.

My issue is the edge server is already passing inbound internet mail to the new 2013 server.  I see the mail being accepted by the Barracuda and message tracking on the edge shows it as delivered to the new 2013 server, but mailbox users never receive.

Is my solution to simply create a new send connector from the 2013 server to the 2010 box or could this be something else?

And why is it delivering to a server with now mailboxes on it yet?

Thank you for any help

dean

I have successfully performed a staged migration for a few users. However, they have each been plagued with different issues along the way. Currently, I am attempting to complete the migration of two users to Exchange 365 and have gotten to the last step, which is executing the PowerShell script Exchange2007MBtoMEU.ps1. This script fails at the first step, which is Disable-Mailbox. The error message I receive is:<o:p></o:p>

Disabling Mailbox<o:p></o:p>

A positional parameter cannot be found that accepts argument '-DomainController'.<o:p></o:p>

+ CategoryInfo : InvalidArgument: (:) [Disable-Mailbox], ParameterBindingException<o:p></o:p>

+ FullyQualifiedErrorId : PositionalParameterNotFound,Disable-Mailbox<o:p></o:p>

I have added the -DomainController parameter in just about every conceivable fashion, but have gotten this message every time. In turn, this causes the remainder of the script to fail.<o:p></o:p>

I really need to get this migration completed, as having an on-premise server and Exchange 365 is proving to be difficult.<o:p></o:p>

Thanks so much,<o:p></o:p>

Randy<o:p></o:p>

Hi All,
I am currently in the process of migrating exchange 2007 to 2013. Everything has gone ok so far, but I am stuck on issues with coexistence.
A very brief rundown of my setup:
Single domain, single exchange 2007 server running all roles.
TMG Firewall
Single exchange 2013 server
Situation:
Exchange 2013 is mail.domain.com
Exchange 2007 is now legacy.domain.com
All relevant names exist in the UCC SSL certificate
OWA:
User with mailbox on exchange 2013 goes to mail.domain.com which is pointed to TMG. Logs in fine and opens the users mailbox on 2013.
User with mailbox on exchange 2007 goes to mail.domain.com, logs into TMG, immediately get “webpage cannot be displayed” Under more information is say )HTTP 500 internal server error)
User with mailbox on exchange 2007 goes to legacy.domain.com, logs into tmg and is correctly redirected to the exchange 2007 mailbox.

Active Sync:
User with mailbox on exchange 2013 works fine pointing to mail.domain.com
User with mailbox on exchange 2007 no longer works after changed 2007 to the legacy namespace.
In exchange 2007 I have left the external url blank for ActiveSync.

Outlook anywhere:
Users with mailbox on 2013 work fine, 2007 don’t.

Internal outlook clients:
Both with mailboxes on either server work fine.
Any help would be much appreciated.
Thanks in advance.

We are providing Exchange 2010 today - in the past it was migrated from Exchange 2003. Now I am prepearing migration to Exchange 2013 - migration proces stopped with error message there is still Exchange 2003 server in configuration. I checked it through Exchange management console and there are realy 2 servers in server summary screen. I did not find legacy Exchange2003 anywhere else in configuration. So I search through internet and found some artical with manual removing old records through ADSIedit tool.
A removed the record from
Configuration\CN=Microsoft Exchange\CN=<Exchange Domain>\CN=Administratice Groups\CN=First Administratice Group\CN=Servers

there was one record with Exchange 2003 specification - so this has been deleted - but in the Exchange console I can still see the legacy Exchange2003 in the Server Summary.

Can somebody point me, what else I should check?

Note: There is still one record in:
Configuration\CN=Microsoft Exchange\CN=<Exchange Domain>\CN=Administratice Groups\CN=First Administratice Group\CN=Routing Groups\CN=First Routing Group\CN=Connection

which it seems define some connection between non existing Exchange2003 and current Exchange2010.

Should I remove this too? Is it safe?

Thanks for any help

Pavel

Hi all,

I have an issue regarding mailbox moves from Exchange 2010 to Exchange 2013. I moved a mailbox and checked statistics on completion. I know that mailboxes can grow up to 30-40% on migration, but the statistics tell me much more.

There was TotalMailboxSize 923MB and BytesTransferred 2.53GB. I wonder, what's the cause. Mailbox database quota was default by 2.3 GB - so the user wasn't able to send mails anymore. What's the cause for such a size increasement?

Thanks.

Hey Team,

I am sure this is well documented and i for some reason cant seem to get good solid answer. But here is my questions. what are the correct URL settings for (OWA, ActiveSync, EWS) etc for Exchange 2013/2010 in a coexistence scenario?

1) All servers in the same ad site

2) mail. autodiscover, pointed to the 2013 server

3) 2013 server is internet connected.

Am i supposed to clear all the 2010 URLs?, Just the external ones? Use a separate namespace?

Thanks,

Robert

---

Robert

I have Exchange 2007 and 2013.  I want to migrate to 2013 but I'm having issues in the testing phase.  I have a test account that I moved the mailbox to the new server.  I have a test PC with a modified hosts file that points to the new Exch 2013 server IP address.

When I log in with this test user, Outlook appears to connect and download the mailbox.  However a Windows Security dialog box pops up saying Microsoft Outlook Connecting to test@domain.com and it has a username and password field.  No matter what is entered here, it is NOT accepted, nor if forcefully entering the wrong information is the account locked out.

I can click cancel here and it proceeds to update the inbox and then says All folders are up to date.  But at the bottom in Outlook 2013 it says Need password and Outlook's icon in the taskbar has a yellow triangle on it.  I can send myself a test email and I get it (I personally am on the 2007 server), but after it sends Outlook 2013 prompts again for the password, and since it does not accept anything, I have to click cancel.

I have done ALL the windows updates available on this test PC.  Exchange 2013 is on CU6 which is the latest at the time of this writing.

Another thing is in the Lync 2013 client it says "Exchange needs your credentials".  No matter what is entered here, it will not make this message go away unless you click the X on this warning bar.  Lync itself appears to work regardless.

Any ideas?

I just changed the ExternalClientAuthenticationMethod from Ntlm to Negotiage.  Now the Outlook prompt does accept the domain password, but I don't want anyone to have to enter any type of credentials just to get on.  Note, this test is on the same LAN as the servers, so I haven't even tackled an external test yet, though last time I tried it was the same results.

Hi,

I have a problem with Exchange 2013 SP1 with CU6.

All of OWA user cannot write in the body of email. They can write the Object and the recipient but they cannot select body and write the body message. We have try with multiple Web brother and desactivate all Add-on but the problem still there...

The only way that works is to respond to an email, and in that case, it's working, we can write normally in the body of email.

Have you an idea ?

Thanks in advance!

Sebastien

Hi Everyone-

I'm migrating my PF from 2007 to 2013 and ran into a weird issue.  I've gone through the steps outlined in this guide twice: http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

1st attempt: After running through all checks - the initial sync, waiting for 'AutoSuspended' failed because of too many bad items.  Read some more about the error and ended up deleting some old system public folders / public folders that it was had the error on (http://support.microsoft.com/kb/555978). I know without a doubt that the cleanup of a previous 2003-2007 migration was not completed.  I chalked it up to that.  I increased the baditemlimit to 20, and resumed the request.  Finally was able to reach autosuspend - locked down PF - and went in to finalize.  After finally restarting the legacy information store, was able to get it to attempt a final sync.  Attached below is the final error.

2nd attempt:  Wasn't sure if the PF's i deleted were sync'd and now causing issues on the 2013 system - went ahead and deleted PF mailbox on 2013, and Migration request.  Unlocked PF's on 2007 - everything came back fine.  Started over again, re-created PF mailbox and started new migration request.  Got to 'autosuspended' almost immediately.  Moved forward as normal, ultimately hitting the same error as attempt 1.

I've deleted all existence of the 'exchangeV1' entities out of the system PF.

Please advise

Thank you!

I've changed the names of my servers - Exchange 2007 = LEGACY2007.DOMAIN.NAME

  Exchange 2013 = NEW2013.DOMAIN.NAME

RunspaceId                       : f1b4ac3d-8a05-4abe-9bd3-87144947df9d
Name                             : PublicFolderMigration
Status                           : Failed
StatusDetail                     : FailedOther
SyncStage                        : IncrementalSync
Flags                            : IntraOrg, Pull, Suspend
RequestStyle                     : IntraOrg
Direction                        : Pull
Protect                          : False
Priority                         : Normal
Suspend                          : True
SourceVersion                    : Version 8.3 (Build 327.0)
SourceDatabase                   : LEGACY2007\Public Folders Storage Group\Public Folders
SourceServer                     : LEGACY2007.DOMAIN.NAME
BatchName                        : 
OutlookAnywhereHostName          : 
RemoteCredentialUsername         : 
AuthenticationMethod             : Basic
RemoteMailboxLegacyDN            : 
RemoteMailboxServerLegacyDN      : 
BadItemLimit                     : 5
BadItemsEncountered              : 303
LargeItemLimit                   : 0
LargeItemsEncountered            : 0
FolderToMailboxMap               : {\}
QueuedTimestamp                  : 10/22/2014 2:27:36 PM
StartTimestamp                   : 10/22/2014 2:27:43 PM
LastUpdateTimestamp              : 10/22/2014 2:35:18 PM
InitialSeedingCompletedTimestamp : 10/22/2014 2:27:46 PM
FinalSyncTimestamp               : 
CompletionTimestamp              : 
SuspendedTimestamp               : 
OverallDuration                  : 00:08:27
TotalFinalizationDuration        : 
TotalDataReplicationWaitDuration : 
TotalSuspendedDuration           : 00:04:09
TotalFailedDuration              : 00:00:46
TotalQueuedDuration              : 00:00:03
TotalInProgressDuration          : 00:00:22
TotalStalledDueToCIDuration      : 
TotalStalledDueToHADuration      : 
TotalStalledDueToReadThrottle    : 
TotalStalledDueToWriteThrottle   : 
TotalStalledDueToReadCpu         : 
TotalStalledDueToWriteCpu        : 
TotalStalledDueToReadUnknown     : 
TotalStalledDueToWriteUnknown    : 
TotalTransientFailureDuration    : 
TotalIdleDuration                : 00:00:01
MRSServerName                    : 
EstimatedTransferSize            : 0 B (0 bytes)
EstimatedTransferItemCount       : 0
BytesTransferred                 : 930.6 KB (952,985 bytes)
BytesTransferredPerMinute        : 
ItemsTransferred                 : 9
PercentComplete                  : 95
PositionInQueue                  : 
PreventCompletion                : False
FailureCode                      : -2146233088
FailureType                      : TooManyBadItemsPermanentException
FailureSide                      : 
Message                          : Error: This mailbox exceeded the maximum number of corrupted items that were 
                                   specified for this move request.
FailureTimestamp                 : 10/22/2014 2:35:17 PM
IsValid                          : True
ValidationMessage                : 
OrganizationId                   : 
RequestGuid                      : 5d826d67-05d5-49d4-9453-58bc40f69c5a
RequestQueue                     : DB01
ExchangeGuid                     : d08583f4-6475-45da-ac01-059dee1cd29e
Identity                         : 830182b4-863f-4214-b0e2-f11fbc7c1158\5d826d67-05d5-49d4-9453-58bc40f69c5a
DiagnosticInfo                   : 
Report                           : 10/22/2014 2:27:36 PM [NEW2013] 'DOMAIN.NAME/.Privileged Accounts/Server 
                                   Support/admin, asimpson' created request.
                                   10/22/2014 2:27:41 PM [NEW2013] The Microsoft Exchange Mailbox Replication 
                                   service 'NEW2013.DOMAIN.NAME' (15.0.913.7 caps:0FFF) is examining the request.
                                   10/22/2014 2:27:41 PM [NEW2013] Connected to target mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e', database 'DB01', Mailbox server 
                                   'NEW2013.DOMAIN.NAME' Version 15.0 (Build 913.0), proxy server 
                                   'NEW2013.DOMAIN.NAME' 15.0.913.7 caps:FFFFCB07FFFF.
                                   10/22/2014 2:27:41 PM [NEW2013] Connected to source mailbox '', database 
                                   'LEGACY2007\Public Folders Storage Group\Public Folders', Mailbox server 
                                   'LEGACY2007.DOMAIN.NAME' Version 8.3 (Build 327.0).
                                   10/22/2014 2:27:41 PM [NEW2013] Request processing started.
                                   10/22/2014 2:27:41 PM [NEW2013] Cleared sync state for request 
                                   00000000-0000-0000-0000-000000000000 due to 'CleanupOrphanedMailbox'.
                                   10/22/2014 2:27:43 PM [NEW2013] Stage: CreatingFolderHierarchy. Percent 
                                   complete: 10.
                                   10/22/2014 2:27:43 PM [NEW2013] Initializing folder hierarchy from mailbox 
                                   '': 38 folders total.
                                   10/22/2014 2:27:43 PM [NEW2013] Folder creation progress: 0 folders created 
                                   in mailbox 'd08583f4-6475-45da-ac01-059dee1cd29e'.
                                   10/22/2014 2:27:44 PM [NEW2013] Folder hierarchy initialized for mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e': 6 folders created.
                                   10/22/2014 2:27:44 PM [NEW2013] Stage: CreatingInitialSyncCheckpoint. Percent 
                                   complete: 15.
                                   10/22/2014 2:27:44 PM [NEW2013] Initial sync checkpoint progress: 0/38 
                                   folders processed. Currently processing mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e'.
                                   10/22/2014 2:27:44 PM [NEW2013] Initial sync checkpoint completed: 6 folders 
                                   processed.
                                   10/22/2014 2:27:44 PM [NEW2013] Stage: LoadingMessages. Percent complete: 20.
                                   10/22/2014 2:27:44 PM [NEW2013] Messages have been enumerated successfully. 9 
                                   items loaded. Total size: 818.8 KB (838,451 bytes).
                                   10/22/2014 2:27:44 PM [NEW2013] Stage: CopyingMessages. Percent complete: 25.
                                   10/22/2014 2:27:44 PM [NEW2013] Copy progress: 0/9 messages, 0 B (0 
                                   bytes)/818.8 KB (838,451 bytes), 5/38 folders completed.
                                   10/22/2014 2:27:45 PM [NEW2013] Copying messages is complete. Copying rules 
                                   and security descriptors.
                                   10/22/2014 2:27:46 PM [NEW2013] A corrupted item was encountered: Folder ACL 
                                   "schema-root"
                                   10/22/2014 2:27:46 PM [NEW2013] A corrupted item was encountered: Folder ACL 
                                   "microsoft"
                                   10/22/2014 2:27:46 PM [NEW2013] A corrupted item was encountered: Folder ACL 
                                   "Default"
                                   10/22/2014 2:27:46 PM [NEW2013] Initial seeding completed, 9 items copied, 
                                   total size 818.8 KB (838,451 bytes).
                                   10/22/2014 2:27:46 PM [NEW2013] Stage: IncrementalSync. Percent complete: 95.
                                   10/22/2014 2:27:46 PM [NEW2013] Folder hierarchy changes reported in source 
                                   '': 0 changed folders, 0 deleted folders.
                                   10/22/2014 2:27:47 PM [NEW2013] Incremental Sync 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e' completed: 0 hierarchy updates, 0 content 
                                   changes.
                                   10/22/2014 2:27:47 PM [NEW2013] Stage: IncrementalSync. Percent complete: 95.
                                   10/22/2014 2:27:47 PM [NEW2013] Automatically suspending job.
                                   10/22/2014 2:31:32 PM [NEW2013] 'DOMAIN.NAME/.Privileged Accounts/Server 
                                   Support/admin, asimpson' modified request.
                                   10/22/2014 2:31:55 PM [NEW2013] 'DOMAIN.NAME/.Privileged Accounts/Server 
                                   Support/admin, asimpson' resumed request.
                                   10/22/2014 2:31:56 PM [NEW2013] Job resumed with status 'InProgress'.
                                   10/22/2014 2:31:56 PM [NEW2013] Relinquishing job.
                                   10/22/2014 2:35:03 PM [NEW2013] The Microsoft Exchange Mailbox Replication 
                                   service 'NEW2013.DOMAIN.NAME' (15.0.913.7 caps:0FFF) is examining the request.
                                   10/22/2014 2:35:03 PM [NEW2013] Connected to target mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e', database 'DB01', Mailbox server 
                                   'NEW2013.DOMAIN.NAME' Version 15.0 (Build 913.0), proxy server 
                                   'NEW2013.DOMAIN.NAME' 15.0.913.7 caps:FFFFCB07FFFF.
                                   10/22/2014 2:35:03 PM [NEW2013] Connected to source mailbox '', database 
                                   'LEGACY2007\Public Folders Storage Group\Public Folders', Mailbox server 
                                   'LEGACY2007.DOMAIN.NAME' Version 8.3 (Build 327.0).
                                   10/22/2014 2:35:03 PM [NEW2013] Request processing continued, stage 
                                   IncrementalSync.
                                   10/22/2014 2:35:03 PM [NEW2013] Folder hierarchy changes reported in source 
                                   '': 5 changed folders, 0 deleted folders.
                                   10/22/2014 2:35:03 PM [NEW2013] Content changes reported for mailbox '': 
                                   Batch 1, New 401, Changed 0, Deleted 0, Read 0, Unread 0, Total 401. 
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"abstract_d.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"account_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"adminfolderdescription_ex.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"alldayevent_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"appointment_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"approved_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Author_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"baseschema_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"bcc_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"bcc_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"bday_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"billinginformation_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"binding_frm.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"browser_frm.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"businesshomepage_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"busystatus_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Bytes_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"calendarfolder_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"calendarmessage_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"callbackphone_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Category_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cc_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cc_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Characters_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"childcount_d.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"childrensnames_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"closedexpectedcontentclasses_s.xml", 
                                   Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cmd_frm.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cn_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"codebase_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comclassid_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Comments_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comment_d.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comment_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"companies_ex.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Company_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comprogid_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"computernetworkname_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"conflict_excc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"contactfolder_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"contacturl_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"contact_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-base_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-class_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-description_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-disposition-type_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-disposition_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-id_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-language_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-location_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-media-type_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                     

Recently I built two Exchange 2013 servers, CAS & mailbox and added them to my existing 2010 organization.  Now, people who HAVE NOT been migrated to the 2013 mailbox server are not getting an updated OAB.  Those on 2013 are getting an updated OAB.

Besides the obvious answer to hasten the migration to 2013, why aren't the 2010 mailbox users not getting an updated OAB?

Thank you,

Chris

Team i am getting issue while running prepare Ad comannd during setup exchange server. Id which i am using have all relevant permiision schema admin,enterprise admin,domain admin.

Setup.exe /prepareschema /IAcceptExchangeserverlicenseterms

gives error:  [ERROR] An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. Seehttp://go.microsoft.com/fwlink/?LinkId=155569 for more information. ; Any hints how to solve this?

---

bostjanc

I installed on Exchange 2013 environment in coexistence with Exchange 2010.

I installed a wildcard certificate on the Exchange 2013 and added the services IIS and SMTP to this certificate.

I have an outlook fat client which is connected to one test already migrated mailbox.

This client continually popups a security alert if I want to proceed: exchangeserver2013.FQDN

How can I prevent this behaviour before migrating other users / mailboxes?

Team,

Please suggest me tools which will help me for complete automization tool of my exchange 2013 server.

Which provide me health status of exchange server, Provides me all critical warning events  alerts, Health of Database, Mailflow, Health for services.