Hybrid Exchange Troubleshooting – CÁC LỖI THƯỜNG GẶP HYBRID EXCHANGE

Bài viết này tôi xin tổng hợp lại 1 số thông tin lưu ý cũng như lỗi trong quá trình triển khai, chuyển đổi của mô hình Hybrid Exchange:

1. ERROR HYBRID CONFIGURATION WIZARD – HasMailboxManagerSettings

ERROR:

017.01.17 02:27:19.320 *ERROR* [Client=UX, Provider=OnPremises] System.Management.Automation.RemoteException: The recipient policy “Default Policy” with mailbox manager settings cannot be managed by the current version of Exchange Management Console. Please use a management console with the same version as the object.

SOLVED:

The Recipient Policy should be a legacy policy in Exchange 2003, which has the HasMailboxManagerSettings set as True. In this case, the policy cannot be upgraded.

You may check the setting by:

Get-EmailAddressPolicy “default policy” |fl *type*,*version*,*Manager*

To remove this setting, if you no longer have the Exchange 2003 Management Console anymore, we can remove it directly using ADSIEdit tool

  • Open adsiedit.msc.
  • In the Configuration container, navigate to CN=Recipient Policies,CN=<Exchange Org>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain>,DC=<com>
  • In the middle pane, view the properties of the Default Policy.
  • Remove the value(s) of the msExchMailboxManagerFolderSettings attibute so that it’s now <Not Set>
  • Edit the MsExchPolicyOptionList attribute and remove all the attributes that do not begin with 0xFC. The policy that begins with 0xFC is the email addressing policy.

After that, you can run the Get-EmailAddressPolicy again to ensure it is set as False. If so, please run the HCW again, you should not see this error again

2. 550 5.7.606 ACCESS DENIED, BANNED SENDING IP

ERROR:

testsync
Your message wasn’t delivered because the recipient’s e-mail provider rejected it.

The following organization rejected your message: HK2APC01FT021.mail.protection.outlook.com.

Diagnostic information for administrators:

Generating server: SERVERNAME-SRV.HO..VN

testsync@.com.vn
HK2APC01FT021.mail.protection.outlook.com #<HK2APC01FT021.mail.protection.outlook.com #5.7.606 smtp;550 5.7.606 Access denied, banned sending IP [x.x.x.x]. To request removal from this list please visit https://sender.office.com/ and follow the directions. For more information please go to http://go.microsoft.com/fwlink/?LinkID=526655 (AS16012609)> #SMTP#

SOLVED:

Cập nhật lại SPF Records cho Public CAS, Load Balancing CAS:

v=spf1 ip4:x.x.x.x ip4:210.245.1.66 ip4:x.x.x.x ip4:x.x.x.x ip4:x.x.x.x ip4:x.x.x.x –all

3. INCREASING THE NUMBER OF SILMULTANEOUS REMOTE / LOCAL MOVE REQUEST ON EXCHANGE 2010

1. Open the file C:\Program Files\Microsoft\Exchange Server\V14\Bin\MSExchangeMailboxReplication.exe.config;

2. Increase the blue values to a number of simultaneous active moves that you want.
<mrsconfiguration ></mrsconfiguration >MRSConfiguration
MaxRetries = “60”
RetryDelay = “00:00:30”
MaxMoveHistoryLength = “2”
MaxActiveMovesPerSourceMDB = “50”
MaxActiveMovesPerTargetMDB = “50”
MaxActiveMovesPerSourceServer = “50”
MaxActiveMovesPerTargetServer = “50”
MaxTotalMovesPerMRS = “100”
FullScanMoveJobsPollingPeriod = “00:10:00”
MinimumTimeBeforePickingJobsFromSameDatabase = “00:00:04”
ServerCountsNotOlderThan = “00:10:00”
MRSAbandonedMoveJobDetectionTime = “01:00:00”
BackoffIntervalForProxyConnectionLimitReached = “00:30:00”
DataGuaranteeCheckPeriod = “00:05:00”
EnableDataGuaranteeCheck = “true”
DisableMrsProxyCompression = “false”
DisableMrsProxyBuffering = “false”
MinBatchSize = “100”
MinBatchSizeKB = “256” ;

3. Save and close the file;

4. Restart the Microsoft Exchange Mailbox Replication service.

4. ENABLING SILENT OWA REDIRECTION TO ADFS OFFICE 365 HYBRID

Tham khảo: http://www.stevieg.org/2012/04/enabling-silent-owa-redirection-for-office-365-hybrid/

Set-OrganizationRelationship “On Premises to Exchange Online Organization Relationship” -TargetOwaURL:https://outlook.com/owa/federateddomain

 

1. You’ll find the casredirect.aspx file within the OWA directory, typically in the following path within the Exchange install directory:

2. C:\Program Files\Microsaoft\Exchange Server\V14\ClientAccess\owa\

3. Edit the casredirect.aspx file directly above the <!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.0 Transitional//EN”> tag and add the following lines:

<%

if (RedirectionUrl.Contains(“https://outlook.com/owa”)) {

Response.Redirect(“https://login.microsoftonline.com/?whr=.com.vn”);

Response.End();

}

%>

4. This should look like this in the actual file itself:

5. CONFIGURE AZURE AD CONNECT SCHEDULER

Gõ lần lượt các lệnh như sau để cấu hình lại scheduler Sync

1. Get-ADSyncScheduler

2. Set-ADSyncScheduler -SyncCycleEnabled $true

3. Set-ADSyncScheduler -CustomizedSyncCycleInterval 01:00:00

4. Start-ADSyncSyncCycle -PolicyType delta

6. THE MAILBOX WAS ALREADY MOVED BUT FAILED TO UPDATE THE JOB STATE DURING THE FINAL STAGES OF THE MOVE

Tham khảo link: https://deployhappiness.com/warning-the-mailbox-was-already-moved-but-failed-to-update-the-job-state-during-the-final-stages-of-the-move

Error Message: Warning: The mailbox was already moved but failed to update the job state during the final stages of the move.

It is possible that the source mailbox could still be alive since post move cleanup operations were deliberately not executed.

 

Symptoms:

Ø Migrated mailbox still appears in on premise exchange management console.

Ø User can’t receive external emails in OWA.

Ø User can’t receive internal emails in Microsoft Office Outlook.

Solution:

Ø Backup exchange attributes from on premise AD account.

Ø Disconnect the mailbox from on premise exchange environment

Ø Repopulate exchange attributes

Ø Set missing exchange attributes (most likely – only targetaddress attribute needs to be set. Compare to other successfully migrated users to double check).

Ø Wait for sync to Office 365 or force sync by running the following PowerShell line: Start-ADSyncSyncCycle -PolicyType Delta

Run Scripts:

Import-Module ActiveDirectory

$Username = “SadUsernameHere”

$O365DomainName = “@OFFICE365DOMAINNAME.COM”

$ADUser = Get-ADUser $Username -Properties *

$Backup = Get-ADUser $Username -Properties *

$TargetAddress = ‘SMTP:’ + $Username + $O365DomainName

$Proxyaddresses = $ADUser | select -ExpandProperty proxyaddresses

$mailNickname = $ADUser | select -ExpandProperty mailnickname

$mail = $ADUser | select -ExpandProperty mail

write-host $TargetAddress

write-host $Proxyaddresses

Write-Host $mailNickname

Write-Host $mail

pause

Disable-Mailbox -Identity $username

sleep -Seconds 5

Set-ADUser $Username -EmailAddress $mail -Replace @{mailNickname=”$mailNickname”;TargetAddress=”$TargetAddress”}

foreach ($Proxyaddress in $Proxyaddresses){

Write-Host $Proxyaddress

Set-ADUser $Username -Add @{Proxyaddresses=”$Proxyaddress”}

}

9. ERROR: MIGRATIONMRSPERMANENTEXCEPTION: ERROR: ENDPOINT

ERROR:

Data migrated: 1.615 GB ‎(1,734,361,022 bytes)‎

Migration rate: 0 B ‎(0 bytes)‎

Error: MigrationMRSPermanentException: Error: Endpoint ‎’09fcc9bd-893e-40de-aa2c-9aacb4ca86d2‎’ doesn‎’t exist. –> Cannot convert value “” to type “Microsoft.Exchange.Configuration.Tasks.OrganizationIdParameter”. Error: “Value cannot be null. Parameter name: objectId” –> Value cannot be null. Parameter name: objectId

SOLVED:

Restart MRS Service trên mailbox server của User

 

Ngoài ra còn một số lỗi trong quá trình Migration, đa phần là do Firewall + Bandwidth, sẽ có 1 bài viết khác cho việc Planning cho hệ thống Network khi sử dụng Office 365.

Cảm ơn các bạn đã ghé thăm Blog.

Comments

comments

Leave a Reply

Your email address will not be published. Required fields are marked *

× 9 = 81

LinkedIn Auto Publish Powered By : XYZScripts.com