Johnny Yao WorkSpace

  http://technet.microsoft.com/zh-tw/magazine/ff626260.aspx Client Creation Q: Do you have any best practices to share for creating an Exchange 2010 CAS array in an Active Directory site? A: I’d advise you to create the CAS array before you make any Mailbox databases or move any mailboxes to an Exchange 2010 Mailbox server in a site. Exchange 2010 Mailbox databases have an attribute called RpcClientAccessServer. If there’s no CAS array in the Active Directory site when the database is created, this will be populated with the server FQDN of an Exchange 2010 CAS server in the Active Directory site. If you create the CAS array before any Mailbox databases, this attribute will instead be given the FQDN of the CAS array as shown in Figure 2. Figure 2 RpcClientAccessServer attribute on a Mailbox database. Why is this a good idea? The Outlook client (whether Outlook 2003, 2007 or 2010) won’t pick up the change automatically. If you use Outlook 2007 or 2010, you can have the

  http://technet.microsoft.com/zh-tw/magazine/ff626260.aspx Q: I’m planning to upgrade our environment from Microsoft Exchange 2007 to Exchange 2010. This im plementation has to be fully redundant on all levels.Because our organization has about 3,000 users, I plan to install Exchange on two machines initially. Each will have the Hub Transport (HT), Client Access Server (CAS) and Mailbox (MB) server roles. Both will also be members of a Database Availability Group (DAG), so the servers will replicate databases between themselves . From our experience with the current Exchange environment, I know that if the HT and MB roles are on the same machine, the Microsoft Exchange Mail Submission service always prefers the local HT server. It doesn’t use other HT servers in the Active Directory site in a round robin fashion, as do MB servers that don’t have the HT server role. If this is the same in Exchange 2010, we have an issue. Keeping the transport dumpster on a DAG member doesn’t m

    http://blogs.technet.com/b/ilvancri/archive/2010/06/15/don-t-forget-to-update-your-ldap-filters-to-opath-filters-when-transitioning-from-exchange-2003-to-exchange-2010.aspx   1. download PS1 from MSExchangeTeamBlog 2. Update methods # Examples on ways to use this script in Powershell... # To convert a manually entered filter and display the result: # # .\ConvertFrom-LdapFilter "(&(mailnickname=*))" # # To convert the LDAP filter on an existing address list and display the result: # # .\ConvertFrom-LdapFilter (Get-AddressList "My Address List").LdapRecipientFilter # To convert the LDAP filter on an existing address list and update the address list with the new filter: # # Set-AddressList "My Address List" -RecipientFilter ( .\ConvertFrom-LdapFilter (Get-AddressList "My Address List").LdapRecipientFilter ) # To convert all existing legacy address

  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   2. After move to Exchange 2010，share mailbox is a user mailbox. 3. New Exchange 2010 resource mailbox   4. Convert mailbox to resource mailbox Set-Mailbox “Mailbox” –Type Room 5. Mailbox converted 6. After converted, account will be disabled.

  1. Create Additional FSW C:\Users\exchadm>cluster res /priv 列出所有資源的私人內容: T  資源                 名稱                           值 -- -------------------- ------------------------------ ----------------------- BR Cluster Name         ResourceData                   01 00 00 00 ... (260 個位元組) DR Cluster Name         StatusNetBIOS                  0 (0x0) DR Cluster Name         StatusDNS                      0 (0x0) DR Cluster Name         StatusKerberos                 0 (0x0) SR Cluster Name         CreatingDC                     \\dc13.msft.corp.com FTR Cluster Name         LastDNSUpdateTime              2010/10/25 上午 08:14:32 SR Cluster Name         ObjectGUID                     b7728a34ccb9044180469c96d885acc4 S  Cluster Name         Name                           BQT-DAG1 S  Cluster Name         DnsName                        BQT-DAG1 D  Cluster Name         RemapPipeNames                 0 (0x0) D  Cluster N

  1. FSW has been changed to BQT-CAS01 and old share path has been removed.   2. But Cluster Res still show original FSW C:\Users\exchadm>cluster res /priv 列出所有資源的私人內容: T  資源                 名稱                           值 -- -------------------- ------------------------------ ----------------------- BR Cluster Name         ResourceData                   01 00 00 00 ... (260 個位元組) DR Cluster Name         StatusNetBIOS                  0 (0x0) DR Cluster Name         StatusDNS                      0 (0x0) DR Cluster Name         StatusKerberos                 0 (0x0) SR Cluster Name         CreatingDC                     \\dc13.msft.corp.com FTR Cluster Name         LastDNSUpdateTime              2010/10/25 上午 08:14:32 SR Cluster Name         ObjectGUID                     b7728a34ccb9044180469c96d885acc4 S  Cluster Name         Name                           BQT-DAG1 S  Cluster Name         DnsName