REF: Exchange 2010– Convert Mailbox to Resource Mailbox (轉換信箱)

-

 

http://technet.microsoft.com/zh-tw/library/bb201749.aspx

主題說明如何使用 Exchange 管理命令介面將信箱轉換為不同類型的信箱。您可以轉換下列項目：

  • 使用者信箱至共用信箱
  • 使用者信箱至資源信箱
  • 共用信箱至使用者信箱
  • 共用信箱至資源信箱
  • 資源信箱至使用者信箱
  • 資源信箱至共用信箱

您無法使用此程序將使用者信箱轉換為連結的信箱，或將連結的信箱轉換為使用者信箱。如需如何轉換為連結之信箱的指示，請參閱如何將信箱轉換為連結的信箱。

適合轉換信箱的案例像是將資源信箱從 Exchange Server 2003 移至  Exchange Server 2010 時。在 Exchange 2003 中，您必須使用共用信箱來代表資源。當您將這些信箱移至 Exchange 2010 時，這些信箱會變成 Exchange 2010 共用信箱。您必須將它們從 Exchange 2010 共用信箱轉換為 Exc hange 2010 資源信箱，讓它們具有 Exchange 2010 資源信箱的所有內容。

Set-Mailbox ConfRoom1 -Type Room

您可以針對 Type 參數使用下列值：

  • Regular
  • Room
  • Equipment
  • Shared

1. Share mailbox on Exchange 2003 for meeting room resource

image

 

2. After move to Exchange 2010，share mailbox is a user mailbox.

image

3. New Exchange 2010 resource mailbox

image

 

4. Convert mailbox to resource mailbox

Set-Mailbox “Mailbox” –Type Room

image

5. Mailbox converted

image

6. After converted, account will be disabled.

image

Comments

Post a Comment

Popular posts from this blog

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Secti...
Read more

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c7992...
Read more

REF: Planning Exchange 2010 DAG - Part 1 - Network Requirements

-
Image
  Planning for High Availability and Site Resilience  - Network Requirements (a single MAPI network / one or more Replication networks ) In Exchange 2010, each DAG will have multiple networks: a single MAPI network , which is used by other Exchange 2010 servers to communicate with the Mailbox server in the DAG, and one or more Replication networks , which are used for log shipping and seeding within the DAG. It's important that the DAG networks are configured correctly. (two adapters/ MAPI network failover/ Replication network revert to MAPI Network/ ) Each member of the DAG must have at least two network adapters installed . This configuration provides you with one MAPI network and one Replication network, and the following recovery behaviors: In the event of a failure affecting the MAPI network, a server failover will occur (assuming there are healthy mailbox database copies that can be activated). In the event of a failure affectin...
Read more