MCITP Microsoft Exchange Server 2007 Messaging Design and Deployment Study Guide phần 3 pdf

Designing and Planning Migration of Legacy Exchange Features 137 Migrating Public Folders Microsoft has de-emphasized public folders in Exchange Server 2007—for example, free/busy calendaring functionality is provided by the Availability service, and offline address books are now distributed using HTTP or HTTPS and BITS (Background Intelligent Transfer Service). Additionally, Microsoft is encouraging the use of SharePoint for collaboration, and is provid- ing guidance for migrating public folders to SharePoint. However, public folders are still fully supported, and system folders in particular are actually required in certain topologies. Fur- thermore, for many enterprises that have developed custom applications or forms using public folders, transitioning the data held in public folders to SharePoint is simply not feasible, so this data must be migrated to Exchange Server 2007. The result of the Set-WebServicesVirtualDirectory cmdlet can be verified using the Get- WebServicesVirtualDirectory cmdlet as follows: Get-WebServicesVirtualDirectory -Identity " CAS_server \EWS (Default Web Site)" The output of the cmdlet will be as shown in this image: Note that the Set-WebServicesVirtualDirectory cmdlet is also used to set the –InternalURL parameter for NLB clusters of CAS computers. For example, to set the Availability service to use an internal NLB cluster named nlb.wiley.com instead of cas1.wiley.com , you would run the following cmdlet: Set-WebServicesVirtualDirectory -Identity " CAS_server " -InternalUrl "Https:// nlb.wiley.com/EWS/Exchange.asmx" EXERCISE 4.1 (continued) 81461c04.fm Page 137 Thursday, December 13, 2007 9:07 AM 138 Chapter 4  Designing and Planning Coexistence and Migrations In the rest of this section, references to public folders also apply to system folders unless otherwise stated. The following are the public folder features that have been removed or de-emphasized. The strategy for dealing with these features is to retain a computer running Exchange 2000 or Exchange Server 2003 in the organization. This applies to the following public folder features:  Public folder graphical user interface (GUI) management  Non-MAPI top-level hierarchies in a public folder store  Public folder access using Network News Transfer Protocol (NNTP)  Public folder access using IMAP4  Public folder access via Outlook Web Access (OWA) In the RTM (Release to Manufacturing) version of Exchange Server 2007, public folders were configurable only through the Exchange Management Shell and were not accessible via OWA. However, in Exchange Server 2007 Service Pack 1, public-folder configuration was added to the Exchange Man- agement Console (EMC) GUI, as was public-folder access via OWA, as shown in Figures 4.3 and 4.4. FIGURE 4.3 Public-folder management through SP1 EMC 81461c04.fm Page 138 Thursday, December 13, 2007 9:07 AM Designing and Planning Migration of Legacy Exchange Features 139 FIGURE 4.4 Public folder access through SP1 OWA Public Folder Hierarchy The public folder hierarchy is contained in the public-folder database, and is replicated to all public-folder databases in the Exchange organization, regardless of whether that database contains replicas of public folders. This replication is independent of the public-folder content replication, and is message-based. The hierarchy contains information on the following:  Client public-folder permissions  A public folder’s description  Public folder priority settings  The public folder replication schedule  A public folder’s position within the public-folder hierarchy  The replica list for each public folder (which public folder databases host copies of the public folder) The hierarchy is referred to by clients accessing public folders, and provides the folder listing displayed within Outlook as well as referrals to the appropriate public-folder replica so that clients can access the data contained within the public folders. 81461c04.fm Page 139 Thursday, December 13, 2007 9:07 AM 140 Chapter 4  Designing and Planning Coexistence and Migrations Public Folder Content Public folder content is also contained within the public-folder database. Unlike with the public folder hierarchy, public folder data is replicated selectively to databases hosting replicas of the particular public folder, dictated by the replica lists configured by the administrator and stored in the public folder hierarchy. Like with the public folder hierarchy, public folder content repli- cation is message-based. For various reasons, you may elect to deploy dedicated public folder servers in your environment. A common error in planning and deploying multiple dedi- cated public folder servers for redundancy is to configure all the mailbox data- bases to use one of the dedicated servers as their client’s default public folders database. Unfortunately, the default public folder database is the location from which clients access the hierarchy, which provides them with information on public-folder replicas and which databases contain that content. This means that if the configured default public folder database is inaccessible, clients have no way to locate other public folder replicas. In this case, it is better to create public folder databases on each mailbox server to provide the hierarchy to the clients, and host all the public-folder data on the dedicated servers. This way, if one of the dedicated public-folder servers becomes unavailable, clients can be referred to other replicas. Creating a Public Folder Database When you install the first Exchange Server 2007 computer hosting the Mailbox server role into an existing Exchange Server 2003 environment, a public folder database is created on that computer by default, and as with Exchange Server 2003 there can be only one public folder database per Exchange Server 2007 computer. However, in an environment with a large number of public folders, you may want to deploy a dedicated Exchange Server 2007 public folder server. Exercise 4.2 outlines the steps to create a public folder database on an Exchange Server 2007 Mailbox server. Although it is technically possible to create a public-folder database in an existing storage group, Microsoft recommends in Exchange Server 2007 that you create a separate storage group for each database—whether they are mailbox or public folder databases. 81461c04.fm Page 140 Thursday, December 13, 2007 9:07 AM Designing and Planning Migration of Legacy Exchange Features 141 EXERCISE 4.2 Public Folder Database Creation To create a public-folder database, you first create a new storage group, and then you create the database itself. Let’s walk through the steps for each. Creating a New Storage Group There are six steps to create a new storage group. 1. Click Start  Programs  Microsoft Exchange Server 2007, and then select Exchange Management Console (EMC). 2. Under the Microsoft Exchange root object, expand the Server Configuration work center and then select the Mailbox node. 3. Within the Mailbox result pane, select the server on which you want to add a storage group. 4. In the right-hand Actions pane for that Mailbox server, click the New Storage Group link as seen here. 81461c04.fm Page 141 Thursday, December 13, 2007 9:07 AM 142 Chapter 4  Designing and Planning Coexistence and Migrations 5. In the New Storage Group wizard shown in the next image, provide a name for the storage group, specify the log files path and the system files path as necessary, and then select New. 6. Click Finish on the Completion screen of the New Storage Group wizard shown here to complete the wizard and create the storage group. EXERCISE 4.2 (continued) 81461c04.fm Page 142 Thursday, December 13, 2007 9:07 AM Designing and Planning Migration of Legacy Exchange Features 143 Creating the Database Now you are ready to create the database. Just follow these steps. 1. In the Exchange Management Console, highlight the storage group created previously and select New Public Folder Database from the Action pane as seen here. 2. In the New Public Folder Database wizard shown next, enter a name for the database and specify a database path to place the database on a separate disk from the storage group’s transaction logs. Click New to create and mount the database. EXERCISE 4.2 (continued) 81461c04.fm Page 143 Thursday, December 13, 2007 9:07 AM 144 Chapter 4  Designing and Planning Coexistence and Migrations Migrating Public Folder Content You can migrate public folders from Exchange Server 2003 to Exchange Server 2007 in several ways. All public folder migration methods accomplish the same basic sequence of events, however: 1. You create replicas of the source public folders on the target server (Exchange Server 2007). 2. The public folder hierarchy is then replicated by Exchange, reflecting the changes you have made in the replica lists for the public folders. 3. Based on the replica changes made by you, the public folder data is replicated from the source server (Exchange Server 2003) to the target server by Exchange. 4. The source server is then removed from the replica lists of the public folders, either manually by you or automatically through a script or Exchange utility. 5. The updated public folder hierarchy reflecting the removal of the source server from the replica lists is replicated by Exchange. 6. Exchange removes the public folder data from the source server. 3. Click Finish on the Completion screen to close the New Public Folder Database wizard. EXERCISE 4.2 (continued) 81461c04.fm Page 144 Thursday, December 13, 2007 9:07 AM Designing and Planning Migration of Legacy Exchange Features 145 Migrating Public Folders Using Exchange System Manager You can move public folders from Exchange Server 2003 to Exchange Server 2007 using the Exchange System Manager GUI. Exercise 4.3 walks you through the necessary steps to do so. Although using Exchange System Manager to migrate public folders is pos- sible, this method may not be very practical in an enterprise environment with a large number of public folders. You would probably employ scripts, the Exchange Server 2007 Exchange Management Shell, third-party tools, or some combination of those elements to achieve the economies of scale required in a large public-folder migration. Public Folder Replication When you are planning your public folder implementation, it is important to note that there are two types of replication involved (and in some cases, three). Here are the two most common:  The public folder hierarchy, which contains the replica lists and client permissions, among other data, and is replicated separately from the public folder data  The public folder data, which, as mentioned earlier, replicates separately from the hierarchy Neither of those replications are accomplished by Active Directory replication. Public-folder hierarchy and data replication are message-based and the data is not stored in Active Direc- tory. These system messages can be tracked using the same mechanisms as user messages; as a consequence, email connectivity, routing, and addressing play a large role in the suc- cessful replication of public folders. The third type of replication that is used is Active Directory replication, but only if mail-enabled public folders exist in the environment. These are represented in Active Directory, so they can be assigned addresses and be listed in the address books. This is the only time when Active Directory replication plays a direct role in public-folder replication. EXERCISE 4.3 Migrating Public Folders with Exchange System Manager In lieu of using the Exchange Server 2007 Exchange Management Shell (built on PowerShell) you can migrate public folders using the Exchange Server 2003 Exchange System Manager GUI. Let’s walk through the steps required to accomplish this. 1. On the Exchange Server 2003 computer or management station, click Start  All Pro- grams  Microsoft Exchange  System Manager. 81461c04.fm Page 145 Thursday, December 13, 2007 9:07 AM 146 Chapter 4  Designing and Planning Coexistence and Migrations 2. Within Exchange System Manager, expand Administrative Groups, expand the adminis- trative group containing the Exchange Server 2003 public folders, expand Folders, and expand Public Folders. 3. If you will be migrating system folders, right-click Public Folders and select View System Folders from the context menu, as shown here. 4. Under Public Folders, right-click the public folder to move to Exchange Server 2007 and select All Tasks  Manage Settings from the context menu as shown here. EXERCISE 4.3 (continued) 81461c04.fm Page 146 Thursday, December 13, 2007 9:07 AM [...]... 2000 Server and Exchange Server 20 03 mailboxes with the Exchange Server 2007 tools, but you can’t create mailboxes on Exchange 2000 Server or Exchange Server 20 03 with the Exchange Server 2007 tools To create Exchange 2000 Server or Exchange Server 20 03 mailboxes, you must use the ADUC Exchange snap-in Discontinued Features Table 4 .3 details the Exchange 2000 Server features that are not supported in Exchange. .. Transport server role 3 Mailbox server role The Client Access Server Role The Client Access server role should be implemented before all other server roles Exchange 2000 Server or Exchange Server 20 03 front-end servers can’t access Exchange Server 2007 mailboxes, but the Exchange Server 2007 Client Access server role can provide access to both Exchange Server 2007 and Exchange Server 20 03 mailboxes Users... on the same Exchange Server 2007 computer is possible However, in the case of OWA access to Exchange 2000 Server or Exchange Server 20 03 mailboxes, if the Client Access role is on a computer a lso holding Exchange Server 2007 mailboxes, then Exchange 2000 Server or Exchange Server 20 03 users will be redirected to the Exchange 2000 Server or Exchange Server 20 03 mailbox server and be prompted for logon... Exchange Server 2007 on the first computer 6 Deploy other Exchange Server 2007 server roles 7 Move mailboxes to Exchange Server 2007 8 Remove legacy Exchange computers Installing Windows Server 20 03 The computer that will be running Exchange Server 2007 requires 64-bit Windows Server 20 03 SP1 or higher The 32 -bit version is supported for evaluation and training purposes only Although Windows Server 20 03 R2... Users and Computers (ADUC) snap-in extension for Exchange, while Exchange Server 2007 mailboxes are managed with the Exchange Server 2007 Exchange Management Console (GUI) or Exchange Management Shell (command line) Exchange Server 2007 mailboxes must not be managed by using the Exchange Server 20 03 tools This is not blocked from happening, but Exchange Server 2007 mailboxes modified with the ADUC Exchange. .. disabled FIGURE 4.5 Exchange Server 20 03 offline address book To enable web-based distribution, the offline address book needs to be moved to an Exchange Server 2007 computer, as Exchange 2000 Server and Exchange Server 20 03 do not support this feature If you have users with Outlook 2007, then during the migration phase to Exchange Server 2007 from Exchange 2000 Server or Exchange Server 20 03, you will need... December 13, 2007 9:07 AM 150 Chapter 4 Designing and Planning Coexistence and Migrations EXERCISE 4.4 (continued) 3 To move a public folder called Ex2003TL and all of its subfolders within that hierarchy from Exchange Server 20 03 to Exchange Server 2007, run the following command: ReplaceReplicaOnPFRecursive.ps1 -TopPublicFolder "\Ex2003TL" -ServerToAdd Targetserver -ServerToRemove Sourceserver In... to Exchange Server 2007 is to implement it in the existing Exchange 2000 Server or Exchange Server 20 03 organization In an intra-organization migration, the sequence of events is as follows: 1 Install Windows Server 20 03 on the Exchange Server 2007 computer 2 Prepare Exchange 2000 Server or Exchange Server 20 03 permissions 3 Extend the Active Directory Schema 4 Prepare Active Directory 5 Install Exchange. .. group, and you can’t create additional routing groups to hold Exchange Server 2007 computers Exchange Server 2007 computers must reside in Exchange Routing Group (DWBGZMFD01QNBJR), and this routing group can’t be renamed Exchange Server 2007 and Administrative Groups Exchange 2000 Server and Exchange Server 20 03 used the concept of administrative groups to allow for delegation of subsets of the Exchange. .. that command, the following is true: Targetserver is the Exchange Server 2007 server folders are being moved to Sourceserver is the Exchange Server 20 03 server public folders are being removed from 4 To replicate all public folders from Server0 1 to Server0 2, run the following command: MoveAllReplicas.ps1 -Server Sourceserver -NewServer Targetserver In that command, the following is true: Sourceserver . "Ex2003TL" -ServerToAdd Targetserver -ServerToRemove Sourceserver In that command, the following is true: Targetserver is the Exchange Server 2007 server folders are being moved to. Sourceserver. first introduced in Exchange 2000 Server and carried over to Exchange Server 20 03 has been removed from Exchange Server 2007. This is because recipients in Exchange Server 2007 are fully provisioned. Sourceserver -NewServer Targetserver In that command, the following is true: Sourceserver is the source Exchange Server 20 03 computer. Targetserver is the target Exchange Server 2007 computer. TABLE