Microsoft Press 70 284 training kit exchange server 2003 phần 5 docx

7-32 Chapter 7 Managing Recipient Objects and Address Lists 1. Select the Extract And Import (One-Step Procedure) option, and click Next to continue. 2. Next, you are prompted to select a Source Server, as shown in Figure 7-26. F07es26 Figure 7-26 Selecting the source server 3. You can control the behavior of the mailbox merge procedure by clicking Options after entering the source server name. You will be presented with multiple pages that allow you to configure different aspects of the merge. 4. The options you can configure are as follows: ❑ Data—The Data page allows you to control how much data you migrate. The default setting, User Messages And Folders, shown in Figure 7-27, migrates only user messages and folders. If you want to migrate additional items, such as the user’s dumpster items (items held by the Deleted Item Retention period) or folder permissions, you can select the appropriate options. Lesson 1 Configuring Recipient Objects 7-33 F07es27 Figure 7-27 The Data page ❑ Import Procedure—The Import Procedure page, shown in Figure 7-28, allows you to define how the data should be written to the destination mailbox store. You can copy the data to the target store (which could create duplicate items), merge the data, replace existing data, or archive the data (deletes it from the source store after copying). F07es28 Figure 7-28 The Import Procedure page 7-34 Chapter 7 Managing Recipient Objects and Address Lists ❑ Folders—The Folders page, shown in Figure 7-29, allows you to configure what folders are processed in the migration. By default, all folders in a mailbox are migrated, though you can choose to limit the migration to specific folders or to exclude certain folders. F07es29 Figure 7-29 The Folders page ❑ Dates—On the Dates page, shown in Figure 7-30, you can select messages between specific dates and times to be migrated. This is useful if you have users who have years worth of e-mail, tasks, and calendar items saved, and you wish to keep only items dating back to a certain date. The default is to migrate everything, regardless of date. F07es30 Figure 7-30 The Dates page Lesson 1 Configuring Recipient Objects 7-35 ❑ Message Details—The Message Details page, shown in Figure 7-31, allows you to extract items based on message subjects or attachment names. This is especially useful if you are working with a very large mailbox, and you want to extract only specific types of messages. F07es31 Figure 7-31 The Message Details page 5. After configuring your options, click OK, and then click Next to continue the wizard. This brings you to the Destination Server page, shown in Figure 7-32. F07es32 Figure 7-32 Selecting the destination server for the migrated mailboxes 7-36 Chapter 7 Managing Recipient Objects and Address Lists 6. Type the name of the destination server for the migration, and then click Next to continue the wizard. The Mailbox Selection page, shown in Figure 7-33, opens, and you can choose the mailboxes you want to migrate. Select the mailboxes you want to migrate, and then click Next. F07es33 Figure 7-33 Selecting the specific mailboxes to be migrated 7. Next, you are prompted to choose the default locale for the target mailboxes. If your destination is in the same country, such as the United States, then you probably have only a single locale in your Exchange organization. If you are mov- ing the mailboxes to a server in a different locale, select the one that is appropriate from the drop-down list, and then click Next. 8. Next, choose a folder on the Exchange server to store the temporary .pst files used during the migration process. When you select a folder, you will see the amount of disk space required and how much space the drive containing the selected folder contains, as shown in Figure 7-34. Lesson 1 Configuring Recipient Objects 7-37 F07es34 Figure 7-34 Selecting a folder to store the temporary .pst files used in the migration 9. Before the migration process begins, you will have the option to save the settings for use at a later date. This is useful if you want to run the migration later as part of a batch and not have to redefine all the settings. After you decide whether to save your settings, click Next to start the migration. A Process Status window will display, showing you vital statistics about the migration, including the elapsed time and how many successes and failures have occurred. When the operation completes, you can click Finish to exit. If there were any errors, an ExMerge.log file will be created in your \Exchsrvr\Bin folder. You can view it to see what went wrong in the process. Managing Mail-Enabled Groups As discussed earlier in this chapter, mail-enabled groups are typically Active Directory security and distribution groups that have been assigned an e-mail address, and when mail is sent to the group address, it is routed automatically to each member of the group. Mail-enabling an existing group is done through the Exchange Task Wizard by choosing the Create An E-Mail Address task from the list. Mail-enabling a new group as you create it adds one extra step, as Exchange extends the New Object creation wizard to prompt you with the option to create an e-mail address and assign the object to an administrative group. Before mail-enabling Active Directory groups, you should have a clear understanding of the effects of group scope on the Exchange Server messaging capability of these groups. There are three scopes for groups: domain local, global, and universal. ■ Domain local group Membership of this group is not published to the global catalog server. This means that Exchange Server users cannot view full 7-38 Chapter 7 Managing Recipient Objects and Address Lists membership of a mail-enabled domain local group when their user accounts are located in domains other than the domain in which the group exists. ■ Global group Membership of this group is not published to the global catalog server. This means that Exchange Server users cannot view full membership of a mail-enabled global group when their user accounts are located in domains other than the domain in which the group exists. ■ Universal group Membership of this group is published to all global catalog servers in a forest. This means that Exchange Server users in any domain can view full membership of mail-enabled universal groups. If you have multiple domains in your environment, it is recommended that you mail-enable only universal groups and not domain local or global groups. Expansion Servers An expansion server is a server that is used to resolve or expand the membership of a mail-enabled group whenever a message is sent to that group. Because of the limited scopes of a domain local group or a global group, Exchange users in one domain are not able to view the membership of groups defined in another domain. Exchange is unable to deliver messages sent by users in one domain to groups defined in another domain. To resolve group membership, you must use an expansion server when mail- enabling domain local groups or global groups in environments that have multiple domains. The expansion server that you choose must exist in the same domain as the mail-enabled group. Expansion servers are identified on a group-by-group basis by editing the properties of the group in the Active Directory Users And Computers con- sole and then clicking the Exchange Advanced tab. The default setting is to use any server in the organization, but you can click the drop-down list and choose a specific server. Query-Based Distribution Groups A query-based distribution group is a new type of distribution group introduced in Exchange Server 2003. A query-based distribution group provides essentially the same functionality as a standard distribution group; however, instead of specifying static user memberships, a query-based distribution group enables you to use a Lightweight Directory Access Protocol (LDAP) query to specify membership in the distribution group dynamically (for example, all employees in an accounting department or all employees in a particular office building). Therefore, adding a user account in the accounting department would result in their automatic membership in a query-based distribution list for the accounting department. The use of query-based distribution groups can considerably lower the administrative overhead in maintaining certain dis- tribution groups, especially those that have memberships that undergo frequent changes. Lesson 1 Configuring Recipient Objects 7-39 Query-based distribution groups are not without disadvantages though. They place more of a performance load on server resources. Every time an e-mail message is sent to a query-based distribution group, an LDAP query is executed against Active Directory to determine the membership of the query-based distribution group. In addi- tion, a query-based distribution group can only be created in an organization that is running Exchange Server 2003 or later and that has been switched to Native mode. To create a query-based distribution group, perform the following steps: 1. Start the Active Directory Users And Computers console, then right-click the Users container and select New, and then click Query-Based Distribution Group. 2. The New Object wizard starts, and the first page prompts you for the name of the group and an alias for it (by default the alias will be the same as the name). Complete the two fields, and then click Next to continue. 3. The next step is to build the LDAP query by filtering the types of addresses you want to include in the query. You can also specify what Active Directory container the query should begin at (all subcontainers will be included), shown in Figure 7-35. Select the address types, and then click Next to continue. F07es35 Figure 7-35 Selecting the address types that the LDAP query should filter for 4. The wizard will prompt you to confirm your selections and then will create the group when you click Finish. You can preview the results of the query-based distribution group by editing the properties of the group in Active Directory Users And Computers and going to the Preview tab. The preview will show you the contents of the group, as well as the syn- tax of the LDAP query that is being run. If the results are not what you intended, you 7-40 Chapter 7 Managing Recipient Objects and Address Lists can simply click the General tab and modify the query, then preview it again to see if the changes corrected the problem. Limiting Access to Mail-Enabled Groups In certain situations, you might want to limit access to your mail-enabled groups to only members of the group. For example, if you have a mail-enabled group that is intended for a particular purpose, such as receiving customer feedback from external customers, you might want to limit the amount of unwanted internal messages sent to this group. Similarly, you might want to prevent users from sending messages to a mail- enabled group if it contains sensitive information, as in the case of a mail-enabled group that is reserved for management. There are two ways to limit access to a mail-enabled group: hiding the mail-enabled group and restricting access to the mail-enabled group. ■ Hiding a mail-enabled group When you hide a mail-enabled group, it will not appear in Exchange address lists, so users will not be able to look up the mail- enabled group and send e-mail to it. However, users can still use the SMTP address of the mail-enabled group to send messages to it. To hide a mail-enabled group from Exchange address lists, edit its properties in the Active Directory Users And Computers console and click the Exchange Advanced tab. Select the option to Hide Group From Exchange Address Lists. This solution prevents users who legitimately need to use the mail-enabled group from being able to browse to it in Exchange address lists. ■ Restricting access to a mail-enabled group By configuring a mail-enabled group to specifically identify the users who can send messages to the group or who can receive messages sent to the group, you can effectively limit who uses the mail-enabled group to only those users that have been granted permission. This is a more effective solution than simply hiding a group because it allows the group to be displayed for the people who legitimately use it but prevents users who shouldn’t use the group from being able to send to it. Configuring message restrictions is done from the Exchange General page of the group’s properties. By default, everyone can send to the group, but you can also set it to allow only authenticated users or to allow only a specific list of users. Note Groups exist to provide a convenient way to send e-mail to a number of users simulta- neously, but they do not preclude users from simply selecting all of the individual members they wish to send to. Therefore, while restricting group access can limit the convenience fac- tor of sending e-mail, it cannot prevent a determined user from selecting every individual user in the GAL to get around the restriction. Lesson 1 Configuring Recipient Objects 7-41 Practice: Configuring Recipient Objects In this practice, you will create four mailbox-enabled users, two mail-enabled groups, configure properties for the objects, and move a mailbox from one server to another. Exercise 1: Create Recipient Objects 1. Using the Active Directory Users And Computers console, create mailbox-enabled accounts for the following users, placing them in the mailbox store on Server01: ❑ Chris Preston ❑ Kim Akers ❑ Alan Shen ❑ Willis Johnson 2. Create the following mail-enabled distribution groups in Active Directory Users And Computers, placing them in the mailbox store on Server02: ❑ Engineering ❑ Marketing 3. Add Chris Preston and Kim Akers to the Engineering group, and add Alan Shen and Willis Johnson to the Marketing group. 4. Open Outlook and send an e-mail to each user you created in order to initialize his or her mailbox. 5. Verify the presence of the mailboxes in Exchange System Manager by opening the Mailboxes folder in the mailbox store containing the mailboxes. Exercise 2: Delete and Reconnect a Mailbox 1. In the Active Directory Users And Computers console, right-click Chris Preston and select Exchange Tasks to start the Exchange Task Wizard. 2. From the list of tasks, choose Delete Mailbox and follow the wizard to delete Chris’s mailbox. 3. Open Exchange System Manager and navigate to the Mailboxes folder in the mail- box store that holds the mailboxes. 4. If Chris Preston’s mailbox does not have a red X on it, right-click the Mailboxes folder and select Run Cleanup Agent, and then refresh the view. 5. Right-click the mailbox for Chris Preston and choose Reconnect. Follow the prompts to reconnect the mailbox to Chris Preston’s user account. [...]... store service of Exchange Server 2003 manages all the storage groups on a server, which can contain public folder stores as well as mailbox stores Storage groups are one of the most significant advantages Exchange Server 2003, Enterprise Edition, has over Exchange Server 2003, Standard Edition Exchange Server 2003, Standard Edition, supports having only a single storage group per server, containing... created automatically in a domain when Exchange Server 2003 is installed, if there isn’t one already In domains where there are no Exchange Server 2003 servers but there are Exchange Server 5. 5 servers that are part of the organization, you must create a Recipient Update Service for that domain To do so, you must first run DomainPrep in the domain Then start Exchange System Manager, rightclick Recipient... planning a server configuration for optimal performance and reliability is crucial This includes not only planning for Exchange Server 2003 but also for the Windows operating system The following hard disk configuration is considered the best practice for a server running Exchange Server 2003 in the real world: ■ Mirrored system disk (RAID-1) Contains the operating system and Exchange Server 2003 binaries... for use by Exchange Server 2003 in case the hard disk runs out of space This allows the Exchange Server 2003 services to shut down normally rather than crashing when the disk becomes full ■ Res2.log The second reserved transaction log Each transaction log is 5 megabytes (MB) in size ■ Tmp.edb A temporary transaction log used by Exchange Server 2003 ■ E00tmp.log When the E00.log file reaches 5 MB in size,... schedule used by the Recipient Update Service to update address list changes in Active Directory ■ Exchange 4.0 and 5. 0 Compatibility Some features of Exchange Server 2003 address lists are compatible only with Exchange Server 5. 5 and later You can enable compatibility with earlier versions of Exchange Server by selecting this check box Offline address lists are flexible because they can be configured... Exchange server going down too often and wants to know what the problem is and how you can fix it Lesson 2 Configuring Information Stores 7 -57 Lesson Summary ■ Exchange Server 2003 uses a combination of database files and transaction logs to manage data Information is first written to a transaction log and later committed to the database ■ Transaction logs are always 5 MB in size Exchange Server 2003. .. the creation of new databases Exercise 1: Create a Storage Group 1 To start Exchange System Manager, from the Start menu, point to All Programs, then point to Microsoft Exchange, and then click Exchange System Manager 2 Navigate to the Exchange Server 2003 server that you will be adding the storage group to Right-click the server, point to New, and then click Storage Group 3 Type MIS for the name Leave... the mailbox store on the other server and it is not there either Why might this be happening? 7-44 Chapter 7 Managing Recipient Objects and Address Lists 2 You are an Exchange Server administrator responsible for 25 servers running Exchange Server 2003, Standard Edition, and approximately 10,000 mailboxes contained within a single administrative group Several of your servers are close to the 16 GB... on Server0 1, you decide to move some users to Server0 2 1 Open Exchange System Manager and navigate to the Mailboxes folder in the mailbox store on Server0 1 2 Select both Willis Johnson and Kim Akers, then right-click and choose Exchange Tasks 3 From the task list, choose Move Mailbox 4 Select Server0 2 from the drop-down list for the server, and note that the mailbox store changes to the store on Server0 2... this works, it does not allow for the optimal level of performance and reliability Exchange Server 2003 performs best when its transaction logs and database files are on separate physical disks (or disk arrays) With Exchange Server 5. 5 and earlier, there was a utility called Performance Optimizer that analyzed your server and made recommendations as to where to place the transaction logs and database . advantages Exchange Server 2003, Enterprise Edition, has over Exchange Server 2003, Standard Edition. Exchange Server 2003, Standard Edition, supports having only a single storage group per server, containing one. storage group, use Exchange System Manager. Each server running Exchange Server 2003 can host up to four storage groups. (However, remember that if you are using Exchange Server 2003 on a Cluster. each time the 5 MB size limit is reached. Exam Tip Transaction log files are always 5 MB in size. Exchange Server 2003 creates an empty 5 MB file and then fills it with data. When the 5 MB size