2011/01/14
Using the Exchange tools ISINTEG and ESEUTIL to Ensure the Health of your Information Store
Using the Exchange tools ISINTEG and ESEUTIL to Ensure the Health of your Information Store: "- 已使用 Google 工具列寄出"
2010/08/24
2010/07/24
2010/07/07
Getting to know the legacy Routing Group Connector in Exchange 2007
Getting to know the legacy Routing Group Connector in Exchange 2007:
"For those of you running bigger organizations, you may need to have multiple legacy RGCs. There are several things to consider before you do this, and as usual, the Exchange team blog tells you all you need to know. Before you go run off and read that link, though, here's a summary of the highlights:
Add the legacy bridgehead servers to the "ExchangeLegacyInterop" group so they have the proper permissions to authenticate to the Exchange 2007 HT servers
"For those of you running bigger organizations, you may need to have multiple legacy RGCs. There are several things to consider before you do this, and as usual, the Exchange team blog tells you all you need to know. Before you go run off and read that link, though, here's a summary of the highlights:
Add the legacy bridgehead servers to the "ExchangeLegacyInterop" group so they have the proper permissions to authenticate to the Exchange 2007 HT servers
2010/06/25
將預設電子郵件地址原則從 LDAP 篩選器升級為 OPATH 篩選器
Exchange 2010 中支援 LDAP 語法篩選，只有從 Exchange 2003 或更早版本遷移的物件上才會存在。有當您想要編輯來自 Exchange 2010 伺服器的篩選器時，才需要將這些 LDAP 篩選器升級為 OPATH 語法。例如，您的組織中若有 Exchange 2003 和 Exchange 2010 伺服器，便可以從 Exchange 2003 伺服器管理 LDAP 語法篩選器。您不能在 Exchange 2010 中管理或建立 LDAP 語法篩選器。
Set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients
Set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients
2010/06/01
2010/05/28
Error: ClassFactory cannot supply requested class, error code: -1056749262
http://www.itexperience.net/2008/06/14/error-classfactory-cannot-supply-requested-class-error-code-1056749262/
During a migration of Exchange 2000 or Exchange 2003 to Exchange 2007, the following error may occur:
During a migration of Exchange 2000 or Exchange 2003 to Exchange 2007, the following error may occur:
Error was found for Username(user mail address) because: Error occurred in the step: Opening source mailbox. Failed to open mailbox with error: ClassFactory cannot supply requested class, error code: -1056749262
In my case, this error occured because the user was disabled in Active Directory.
If you face this same error, try the following:
If you face this same error, try the following:
- Unhide the user in the Global Address Book (open the Properties of the User in Active Directory, go to the Exchange Advanced tab, and deselect the “Hide from Exchange Address Lists” checkbox)
- Enable the user, in case the user is Disabled. Also check whether the user is Locked out or not (open the Properties of the User in Active Directory and check the Account tab. Both the chekboxes should NOT be checked)
When one or both of the above were the case, wait for 10-30 minutes. Active Directory needs to replicate its changes. Then retry to move the mailbox to the other server.
If you still face the same error after 30 minutes, try to unmount en mount the Information Store. This should be your last chance for survival :)
2010/05/05
公用資料夾 衝突
如果您的組織把公用資料夾保存在一部以上的 Microsoft Exchange Server 上，並且在不同的電腦上對相同的項目作修改，而這些電腦又同步作業的話，您可能會看到衡突的訊息。
若要解決衝突，請開啟衝突的訊息。此訊息包含該項目所有衝突的版本。若要把所有資訊合併為一個項目，開啟在衝突訊息中的其中一個項目，然後 從其他項目複製任何您需要的資訊到此項目。然後按一下 [保存此項目]。其他衝突的項目則會被刪除。
若要將所有衝突項目個別儲存在公用資料夾中，按一下 [保存所有]。
若要解決衝突，請開啟衝突的訊息。此訊息包含該項目所有衝突的版本。若要把所有資訊合併為一個項目，開啟在衝突訊息中的其中一個項目，然後 從其他項目複製任何您需要的資訊到此項目。然後按一下 [保存此項目]。其他衝突的項目則會被刪除。
若要將所有衝突項目個別儲存在公用資料夾中，按一下 [保存所有]。
2010/05/03
troubleshoot public folder replicate is stop between ad site. - Windows Live
troubleshoot public folder replicate is stop between ad site. - Windows Live
公用資料夾的問題終於處理ok
原因是Public folder 的 proxyaddress衝突
利用adsiedit錯開即可。
公用資料夾的問題終於處理ok
原因是Public folder 的 proxyaddress衝突
利用adsiedit錯開即可。
2010/04/30
2010/04/29
exchange 2000 public folder 複寫 in sync and local Modified
In Sync indicates that there have been no changes to local public folder replicas
since changes were last sent.
Local Modified indicates that there have been changes made to local public folder replicas that have not yet been sent. So if you see the local modified for Exchange 2003 server there is no need to worry, if it is for 2000 it means that there are changes yet to be replicated.
As far as best way to know if replication completed, I rely on looking at the size and number of items in the local public folder store for each PF and compare both source and target store (This is not feasible in large environments and you might need to export the list and compare using excel).
thanks,
since changes were last sent.
Local Modified indicates that there have been changes made to local public folder replicas that have not yet been sent. So if you see the local modified for Exchange 2003 server there is no need to worry, if it is for 2000 it means that there are changes yet to be replicated.
As far as best way to know if replication completed, I rely on looking at the size and number of items in the local public folder store for each PF and compare both source and target store (This is not feasible in large environments and you might need to export the list and compare using excel).
thanks,
2010/04/27
Public Folder Replication Troubleshooting – Part 1: Troubleshooting the Replication of New Changes
http://msexchangeteam.com/archive/2006/01/17/417611.aspx
New-DatabaseAvailabilityGroup: Exchange 2010 Help
New-DatabaseAvailabilityGroup: Exchange 2010 Help
you must add the Exchange Trusted Subsystem universal security group to the local Administrators group on the witness server prior to creating the DAG
you must add the Exchange Trusted Subsystem universal security group to the local Administrators group on the witness server prior to creating the DAG
Moving public folder replicas from Exchange 2000 to Exchange 2007
http://msexchangeteam.com/archive/2007/10/30/447339.aspx
訂閱：
文章 (Atom)