Hi people!!

We have two Exchange environments in different forest. We want to do a crossforest migration from Exchange Server 2007 to Exchange Server 2013 (Exchange Resource Forest with Linked Mailboxes). These are the configurations:

Domain: SourceDomain.local

ActiveDirectory: 2012 R2 Domain Controllers. Domain functional level 2008

Exchange: Exchange Server 2007 Service Pack 3 RU15

• 2 Mailboxes Servers à Cluster Continuous Replication
• 2 ClientAccess & HubTransport Servers with NLB by Microsoft
• 2 Edge Servers

Domain: TargetDomain.local

ActiveDirectory: 2012 R2 Domain Controllers. Domain functional level 2012 R2

Exchange: Exchange Server 2013 Cumulative Update 7 (CU7) (Exchange Resource Forest)

• 2 Mailboxes Servers à 1 DAG
• 2 ClientAccess Servers
• 2 Edge Servers

Both Exchange works fine. Exchange Server 2007 (SourceDomain.local) is currently in production and Exchange Server 2013 in Resource Forest (TargetDomain.local) is for migrating mailboxes in Linked Mailbox from Exchange 2007. We´ve configured a Linked Mailbox and it works.

We´ve configured a trust between the forests:

• Conditional Forwarders in both domains
• Forest trust, One-way outgoing, Forest-wide authentication: TargetDomain.local, Domains trusted by this domain (outgoing trusts)à SourceDomain.local – Forest- Transitive SourceDomain.local, Domains that trust this domain (incoming trusts) à TargetDomain.local – Forest – Transitive

We´ve configured following prerequisites for migrating:

• Accepted Domains à Both Exchanges have an accepted domain:Company.com as Internal Relay Domain
• Send Connectors à Both Exchange have a send connector (CrossForest) with Address Space:*.company.com and Smart Hosts
• Test Mailflow. (Currently, MXs for company.com are in Exchange 2007)
  • Mail from external source to mailbox in Exchange 2007 à OK
  • Mail from external source to mailbox in Exchange 2013 à OK
  • Mail from external source to Linked Mailbox in Exchange 2013 an account in DomainSourceDomain.localà OK
  • Internal Mail from Exchange 2007 to Exchange 2013 à OK
  • Internal Mail from Exchange 2013 to Exchange 2007 à OK
• MRSPROXY. We´ve activated MRSProxy in both Client Access Servers in Exchange 2013

For Migrating Mailboxes, from Client Access Server in Exchange 2013 in PowerShell, We’ve done these steps:

• Preparation Mailboxes. Previously We´ve stored credentials with Get-Credential. $SourceCredentials à SourceDomain.local and &TargetCredentialsà TargetDomain.local We´ve run this command: Prepare-MoveRequest.ps1 –identity “Testuser”–RemoteForestDomainController DC1.SourceDomain.local –RemoteForestCredential $SourceCredentials –LocalForestDomainController DC1.TargetDomain.local –LocalForestCredential $TargetCredentials –LinkedMailUser –TargetMailUserOU “OU=Mailboxes,DC=TargetDomain,DC=local” –Verbose It finished fine and 1 mailbox ready to move. We´ve checked It´s created a Disable User in TargetDomain.Local.
• New-MoveRequest. Previously We´ve stored credentials with Get-Credential. $SourceCredentials à SourceDomain.local We´ve run this command: New-MoveRequest –identity “Testuser” –RemoteLegacy –TargetDatabase “DB1” –RemoteGlobalCatalog “DC1.SourceDomain.local” –RemoteCredential $SourceCredentials –TargetDeliveryDomain “company.com” It finished with this error: MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)

Diagnostic context:

    ......

    Lid: 62184

    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a

    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 4480

    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-06-16T07:25:29.0510000Z

    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18

    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722

    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 323

    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0

    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0

    Lid: 62184

    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a

    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 4480

    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-06-16T07:25:29.0510000Z

    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18

    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1237

    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 313

    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0

    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0

    Lid: 62184

    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a

    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 4480

    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-06-16T07:25:29.0510000Z

    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18

    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060

    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 311

    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0

    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3

    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 135

    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0

    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0x2A84C00A00000000

    Lid: 62184

    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a

    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 4480

    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-06-16T07:25:29.0510000Z

    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18

    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060

    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 318

    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0

    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0

    Lid: 45169   StoreEc: 0x977

    Lid: 50544   ClientVersion: 15.0.1044.25

    Lid: 52080   StoreEc: 0x977

    Lid: 51152

    Lid: 52465   StoreEc: 0x977

    Lid: 60065

    Lid: 33777   StoreEc: 0x977

    Lid: 59805

    Lid: 52487   StoreEc: 0x977

    Lid: 19778

    Lid: 27970   StoreEc: 0x977

    Lid: 17730

    Lid: 25922   StoreEc: 0x977

    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException

    + FullyQualifiedErrorId : [Server=MAIL01,RequestId=48ad3e2e-deb3-492d-bfff-1425c231ae6f,TimeStamp=16/06/2015 7

   :25:29] [FailureCategory=Cmdlet-RemoteTransientException] D68807DB,Microsoft.Exchange.Management.RecipientTasks.Ne

  wMoveRequest

    + PSComputerName        : CAS01.TargetDomain.local  

After this error, We´ve done following changes and tests:

• To check network permission between both Exchanges and Active Directory. Currently we have any/any permissions.
• To resolve NETBIOS name and FQDN names beween both Exchange. In TargetDomain.local We added in host file NETBIOS name and FQDN name of all Exchange Servers 2007. In SourceDomain.local we can do ping to NETBIOS and FQDN without to edit host file.
• Import Root CA Between both Exchange Organizations. In each Exchange server in SourceDomain.local import Root CA we use in Exchange 2013 and in each Exchange server in TargetDomain.local import Root CA we use in Exchange 2007. After this, We´ve checked to access OWA without warning certificate (Internal Access OWA).
• Restart all Exchange Servers 2013.

After these steps we carry on with the same error:

MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)

I´ve tried as well to do the movement of Mailbox from EAC in Exchange Server 2013. After insert Source Credentials, we have this warning:

Hi,

I use Exchange 2013 Server SP1 on Windows 2012.

From yesterday my user don't have new emails in they OWA or Outlook 2013 App...

Seems no errors sended to mail sender... so what I can check first ?

Thanks

I have these logs :

I have gone ahead and created a RetentionPolicy to remove items older than 60 days from the DeleteItems folder. I have assigned the new Policy to a few users that were migrated from Exchange 2007 to Exchange 2013. When I use the get-mailbox command, I can see the new policy applied. However.... when I perform a get-RetentionPolicyTag -Mailbox "MovedMailbox" nothing returns. What am I missing here?

How can I confirm this policy is applying?

Thanks

Recently upgraded to CU3.  I'm not sure if my EAC problems are due to that or something else.  I could have swore this worked before, but I am not 100% positive.

If I go to "Recipients > Mailboxes > Properties on a mailbox > Mailbox Delegation" it says "Please wait...".  It stays like that for about 15-20 seconds, then finally comes back with:  "error.  Your request couldn't be completed.  Please try again in a few minutes".  I hit OK and the boxes for Send As, Send on Behalf, and Full Access are all empty.

I can view permissions on that same mailbox with PowerShell.

Also, if I do the same process for a Distribution Group, then that works okay in EAC!

I am trying to move my Discovery Search Mailbox from the original database built with Exchange. It is not in a DAG. The database I am trying to move to is in a DAG. I am getting the below error, any ideas?

FailureCode                            : -2146233088
FailureType                            : MailboxDataReplicationFailedPermanentException
FailureSide                            :
Message                                : Error: Mailbox changes failed to replicate. Database
                                         a6e59ff8-f93e-4ba9-ba41-c33a45400705 doesn't satisfy the constraint
                                         SecondDatacenter because the commit time 6/22/2015 3:32:09 PM isn't
                                         guaranteed by replication time 12/31/9999 11:59:59 PM.
FailureTimestamp                       : 6/22/2015 10:42:12 AM
IsValid                                : True
ValidationMessage                      :
RequestGuid                            : 81c11a5c-fdaa-410c-95e2-1c1b47860303

Hi,

We have recently upgraded from Exchange 2010 to Exchange 2013. Since the migration we have had issues with our archiving system.  Bascially the archiving system creates .eml files types

When Outlook is running in non-cached exchange mode any attachments within these .eml files are missing when the eml file is opened. If you change Outlook to run on cached mode the attachments show up fine.

It's almost identical to the following issue;

http: // social.technet.microsoft.com/Forums/office/en-US/b9a390a9-e014-4098-ad6e-dd377a53422a/office-2010-exchange-2010-attachments-in-emlemails-are-invisible?forum=outlook

Except for the Exchange version this is exactly what is happening to us. Is anyone aware of whether the same issue fixed in Rollup update 5 for Exch 2010 SP1 is present in Exchange 2013?

Ivanildo Teixeira Galvão

How can I set a default retention policy to all new accounts created so they adopt the policy by default.

I have tried running...

Set-RetentionPolicy -Identity "Company Wide Retention Policy" -IsDefault $true

A parameter cannot be found that matches parameter name 'IsDefault'.
    + CategoryInfo          : InvalidArgument: (:) [Set-RetentionPolicy], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Set-RetentionPolicy
    + PSComputerName        : ex13mb01.mydomain.local

Clean load of 2012 R2, Prepped schema and AD.

Exchange setup fails with the below:

Error:
The following error was generated when "$error.Clear();
          if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
          {
          if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
          {
          $sysMbx = $null;
          $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
          $dispName = "Microsoft Exchange";
          Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
          $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
          if ($mbxs.Length -eq 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
          $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
          if ($dbs.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
          $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
          if ($arbUsers.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
          $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
          }
          }
          }
          else
          {
          if ($mbxs[0].DisplayName -ne $dispName )
          {
          Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
          Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
          }
          $sysMbx = $mbxs[0];
          }

          # Set the Organization Capabilities needed for this mailbox
          if ($sysMbx -ne $null)
          {
          # We need 1 GB for uploading large OAB files to the organization mailbox
          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
          set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
          }
          else
          {
          Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
          }
          }
          else
          {
          Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
          }
          }
        " was run: "Database is mandatory on UserMailbox.".

Error:
The following error was generated when "$error.Clear();
          if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
          {
          if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
          {
          $sysMbx = $null;
          $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
          $dispName = "Microsoft Exchange";
          Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
          $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
          if ($mbxs.Length -eq 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
          $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
          if ($dbs.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
          $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
          if ($arbUsers.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
          $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
          }
          }
          }
          else
          {
          if ($mbxs[0].DisplayName -ne $dispName )
          {
          Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
          Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
          }
          $sysMbx = $mbxs[0];
          }

          # Set the Organization Capabilities needed for this mailbox
          if ($sysMbx -ne $null)
          {
          # We need 1 GB for uploading large OAB files to the organization mailbox
          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
          set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
          }
          else
          {
          Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
          }
          }
          else
          {
          Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
          }
          }
        " was run: "Database is mandatory on UserMailbox.".

Hi All

I am in a position of doing cross forest migration. Source Exchange is 2007 and target 2013.In the source mail box has got recipient limit set(ex 50). currently we are in a co-existence scenario. when a migrate user send a mail to many distribution list the user receives too many recipients error. which is generating by the remote exchange server(source). Is there away to overcome the issue without increasing the recipient limit on the source enabled user?

Sanka Perera

We have an equipment resource calendar that we use to keep track of usage.  It has delegates that accept the meeting request. The problem is the users would like to allow meeting requests that occur in the past because sometimes they don't put things in in advance, but they want to document the use.  Every time a meeting request is sent with the date in the past:

Your meeting request was declined.
The invitation was declined because it occurred in the past.
________________________________
Sent by Microsoft Exchange Server 2013

Here is the configuration as it stands now:

RunspaceId                          : cd6e516b-a2c2-4933-8c4d-286f23fef449
AutomateProcessing                  : AutoAccept
AllowConflicts                      : True
BookingWindowInDays                 : 365
MaximumDurationInMinutes            : 0
AllowRecurringMeetings              : True
EnforceSchedulingHorizon            : True
ScheduleOnlyDuringWorkHours         : False
ConflictPercentageAllowed           : 0
MaximumConflictInstances            : 0
ForwardRequestsToDelegates          : True
DeleteAttachments                   : True
DeleteComments                      : True
RemovePrivateProperty               : True
DeleteSubject                       : False
AddOrganizerToSubject               : False
DeleteNonCalendarItems              : True
TentativePendingApproval            : True
EnableResponseDetails               : True
OrganizerInfo                       : True
ResourceDelegates                   : {xxxxx/Users/Field Operations/xxxxxxx, xxxxx/
                                      Users/Headquarters/xxxxxxxx, xxxxx/Users/Headquarters/xxxxxx}
RequestOutOfPolicy                  : {}
AllRequestOutOfPolicy               : False
BookInPolicy                        : {}
AllBookInPolicy                     : False
RequestInPolicy                     : {}
AllRequestInPolicy                  : True
AddAdditionalResponse               : False
AdditionalResponse                  :
RemoveOldMeetingMessages            : True
AddNewRequestsTentatively           : True
ProcessExternalMeetingMessages      : False
RemoveForwardedMeetingNotifications : False
MailboxOwnerId                      : xxxxx/Exchange/Resources/NameOfResourceList
Identity                            : xxxxx/Exchange/Resources/NameOfResourceList
IsValid                             : True
ObjectState                         : Changed

Sally

I read about this problem a lot, but did not find any correct answer. I hope somebody can help.

Exchange 2013 CU7 (migrated from Exchange 2007, but for now only the Exchange 2013 is available)

1. When I try to download OAB from Outlook 2007 or 2013, I get 0x80190194 error, but not for all computers and not for all users. One of our domain admin can download the OAB, but I can not (i have the same privilegies). Some of our users can download OAB, some other users who has the same rights, can not. We tried all the users on many machines and who could download it, can download from anywhere.

2. I try to open from O2007 or O2013 address book\All Rooms I get alert message because of "bookmark is not valid".

3. If I try to update All Rooms from ECP or run in EMS the  Get-GlobalAddressList | Update-GlobalAddressList command I get this:

Active Directory operation failed on dc1.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
+ CategoryInfo          : NotSpecified: (:) [Update-GlobalAddressList], ADOperationException
+ FullyQualifiedErrorId : [Server=EXCHANGE,RequestId=5bdfd63a-b117-4ac9-b969-3be642fe5be9,TimeStamp=2015.06.18. 10:58:02] [FailureCategory=Cmdlet-ADOperationException] 76923803,Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateGlobalAddressList
+ PSComputerName        : exchange.domain.local

I think these correlate with a main issue, but i don't know where and how can I manage it. Can anybody help me?

Hi,

I'm trying to get my head around something I am sure is very basic indeed. All the guidance recommends keeping things simple and trying to minimise URLs and so on , but i can't square how it works in my head. Single AD domain with "acme-corp.com" for example.

Lets say I have two separate datacenters one in northamerica and one in emea. I want my 2000 users in NA to use a DAG in north america and my 1000 users in emea to use a DAG in emea DC. Unless of course there is an outage in which case I want the dag's to failover. lets say each DC has 2 CAS/MBX servers installed to keep it small.

So starting  is the "autodiscover.acme-corp.com" record. My understanding is that for each server, I can create a DNS record for autodiscover for each host (and set the URL's correctly) so that clients will pick one of these and connect to the particular server (create a certificate for it and so on).  If an EMEA client picks a north american server from DNS this will proxy the request to an EMEA mailbox server. When the docs say proxy does it mean that the traffic will constantly flow from outlook > NA server > EMEA server, or it is just the initial connection and once that is made traffic goes from outlook to the EMEA server directly? A brief connection to NA is probably ok, but not all traffic!

I've read about the autodiscover site affinity setting but I'm not sure that works with Exchange 2013 and I'm not really sure if that is what i want, as ideally i will just use a single URL/hostname for autodiscover over all the servers as this keeps things a lot simpler.

Does that make any sense?

Cheers

Dave

David Hood www.consilium-uk.com

two user migrated to 2013 from 2007 are unable to create appointment/mtgs on mailbox/calendar that is still on the 2007.

They have added the Room calendar to outlook and are able to see it, but when they try to add an appointment, the option of adding/editing an appointment is grayed out.  an appointment that has already been created, a message comes back saying they don’t have permissions.

using web mail, they get " YOU DONT HAVE PERMISSION TO CREATE AN ENTRY IN THIS FOLDER."

they have author rights to the calendar.

I did removed them and re-added them to the permission list, but it still does not work. I also deleted / added the
calendar from their Outlook.

Dear Sir, 

    A user received a return message from Outlook 2010:

==================

From: Boss1@domain1.net
Sent: Tuesday, June 23, 2015 11:02 AM
To: joe@domain1.net
Subject: RE: Service work re-arrangement

This message contains content that is prohibited by organization policy. The message will not be downloaded.

Original Message ID:  3EA487EC-E34B-4CA4-53A0-43635F8A3530

Action:Quarantine

Status:::::action exception handling:: 

==================

       Do it has any method to trace what kind of organization policy blocked this message?  Is it possible to trace in Exchange server with message ID?

Regards,

Joe Tam