Questions and Answers


Lesson 1 Review

Page 5-24

1.

You are the Exchange Server administrator for Litware, Inc. You have installed an Exchange Server 2003 server in the existing Exchange Server 5.5 organization, and you are trying to migrate the mailboxes over to the new server. You run the Migration Wizard on the Exchange Server 2003 server and select to migrate from Exchange Server 5.5, but you find that you are unable to do so. Why would this happen?

the migration wizard is able to move mailboxes only between servers in different organizations. it cannot be used to move mailboxes between servers within the same organization. to accomplish this, you would use the active directory users and computers console and select move mailbox from the exchange tasks menu of the user accounts with the mailboxes you want moved.

2.

You need to migrate a server from Exchange Server 5.5 to Exchange Server 2003, but you know that you cannot perform an in-place upgrade in this situation. Since Exchange Server 5.5 with SP4 is running on Windows 2000 Server with SP4, you decide to do an interim in-place upgrade from Exchange Server 5.5 to Exchange 2000 Server, and then you will upgrade Exchange 2000 Server directly to Exchange Server 2003. You install Exchange 2000 Server successfully and verify that users are able to log on and access mail, and then you immediately insert the Exchange Server 2003 installation CD and run Setup. However, Setup fails. What is the most likely cause?

upgrading from exchange 2000 server requires sp3. in this instance, you successfully upgraded exchange server 5.5, so there are no permissions problems, and the version of windows supports exchange server 2003. once you install the latest service pack for exchange 2000 server, you will be able to perform the in-place upgrade.

3.

You install a new Exchange Server 2003 server into your existing Exchange Server 5.5 organization. You successfully migrate all the mailboxes to the new server, and users are able to access their mail from the new server without any problems. One afternoon, you shut down the Exchange Server 5.5 server, planning to use the machine later for something else. The next day, you receive many complaints that e-mail is working within the company, but mail is not being sent to or received from the Internet. What is the problem?

in addition to moving mailboxes, you must also transfer any connectors that are in use. in this instance, the internet mail service is still on the exchange server 5.5 server. first, you need to start the server back up, and then you need to configure an smtp virtual server on the new exchange server 2003 server and schedule the time to switch the mx record in dns to the new server when the downtime will have the least impact.

Answers

1.

The Migration Wizard is able to move mailboxes only between servers in different organizations. It cannot be used to move mailboxes between servers within the same organization. To accomplish this, you would use the Active Directory Users And Computers console and select Move Mailbox from the Exchange Tasks menu of the user accounts with the mailboxes you want moved.

2.

Upgrading from Exchange 2000 Server requires SP3. In this instance, you successfully upgraded Exchange Server 5.5, so there are no permissions problems, and the version of Windows supports Exchange Server 2003. Once you install the latest service pack for Exchange 2000 Server, you will be able to perform the in-place upgrade.

3.

In addition to moving mailboxes, you must also transfer any connectors that are in use. In this instance, the Internet Mail Service is still on the Exchange Server 5.5 server. First, you need to start the server back up, and then you need to configure an SMTP virtual server on the new Exchange Server 2003 server and schedule the time to switch the MX record in DNS to the new server when the downtime will have the least impact.

Lesson 2 Review

Page 5-37

1.

You are trying to configure an X.400 connection between your Exchange Server 2003 organization and a remote X.400 messaging system running on a UNIX platform. After working with the administrator of the remote system to configure the connector, you test and find that your side of the connection receives messages fine, but on the remote end, the messages come out garbled. What do you need to do to fix the problem on your end?

by default, allow exchange contents is enabled, which sends messages in exchange's internal format. this works when the destination system is an exchange server system, but when it is a non-exchange server system, you have to clear the option in order for messages to be sent in the standard x.400 format.

2.

You have set up directory synchronization between your Exchange Server 2003 organization and the Lotus Notes organization of a company that has recently merged with your company. E-mail is working fine and you are able to verify synchronization between Active Directory and Notes, but Outlook users are complaining that when they view the schedules of Notes users, the information is generally out of date. What can you do to correct the problem?

the schedule tab of the calendar connector's properties must be configured to synchronize calendar data. the default setting is never, which does not synchronize calendar data, and depending on what schedule you create, your data may become out of date before it synchronizes again.

3.

You are the administrator of two Exchange Server 2003 routing groups that have been connected by a T-1 line. Lately, the circuit has been very inconsistent, sometimes very slow, and sometimes dropping connection altogether. Message traffic is suffering as a result. What can you do to improve the reliability of the message transfer over the unreliable connection?

when bandwidth is reliable, you typically use site connectors to connect exchange server 2003 routing groups. however, x.400 connectors can be used to connect exchange server routing groups, as well, and they are useful when bandwidth is unreliable. this is because the x.400 connector uses messaging-based data transfer rather than remote procedure call (rpc), which requires a reliable connection. by implementing an x.400 connector, you can improve message transfer reliability in this situation.

Answers

1.

By default, Allow Exchange Contents is enabled, which sends messages in Exchange's internal format. This works when the destination system is an Exchange Server system, but when it is a non-Exchange Server system, you have to clear the option in order for messages to be sent in the standard X.400 format.

2.

The Schedule tab of the Calendar Connector's properties must be configured to synchronize calendar data. The default setting is Never, which does not synchronize calendar data, and depending on what schedule you create, your data may become out of date before it synchronizes again.

3.

When bandwidth is reliable, you typically use Site Connectors to connect Exchange Server 2003 routing groups. However, X.400 connectors can be used to connect Exchange Server routing groups, as well, and they are useful when bandwidth is unreliable. This is because the X.400 connector uses messaging-based data transfer rather than remote procedure call (RPC), which requires a reliable connection. By implementing an X.400 connector, you can improve message transfer reliability in this situation.

Lesson 3 Review

Page 5-41

1.

Which of the following messaging systems is not supported by the Migration Wizard?

  1. Lotus cc:Mail

  2. SendMail

  3. Microsoft Mail

  4. Internet Mail

the correct answer is b.

2.

You are trying to migrate a Lotus Notes server in the domain adatum.com to an Exchange Server 2003 organization in the fabrikam.com domain. You are performing a test migration using the Migration Wizard, and the wizard asks you to specify the name of your Lotus Notes server. After you do, you receive an error that the server cannot be contacted. You verify that the Notes server is running, and users in the adatum.com domain are not complaining about being unable to access e-mail. How would you troubleshoot this problem?

one of the most common problems when migrating across domains is having dns set up incorrectly. you should first verify that you have connectivity and name resolution between the two domains by attempting to ping the notes server by dns name from the exchange server 2003 server. if you are able to resolve the dns problem, you should be able to connect to the notes server with the migration wizard.

3.

You are involved in a migration of mail systems between two companies. Litware, Inc., which runs Exchange Server 2003, has acquired Contoso, which runs Novell GroupWise on the NetWare operating system. What type of information will you be able to migrate to Exchange Server 2003, and how will user accounts be handled?

the migration wizard will be able to effectively migrate all user mailbox data, but it will not be able to migrate netware user accounts intact. the migration wizard will create new user accounts for the netware users in active directory and then associate the migrated mailboxes with the new user accounts.

Answers

1.

The correct answer is b.

2.

One of the most common problems when migrating across domains is having DNS set up incorrectly. You should first verify that you have connectivity and name resolution between the two domains by attempting to ping the Notes server by DNS name from the Exchange Server 2003 server. If you are able to resolve the DNS problem, you should be able to connect to the Notes server with the Migration Wizard.

3.

The Migration Wizard will be able to effectively migrate all user mailbox data, but it will not be able to migrate NetWare user accounts intact. The Migration Wizard will create new user accounts for the NetWare users in Active Directory and then associate the migrated mailboxes with the new user accounts.

Case Scenario Exercise: Requirement 1

Page 5-42

1.

Installing the Exchange Server 2003 version of the ADC requires a minimum of Windows 2000 Server SP3, but all servers except the new Server07 are running SP2. Before installing the ADC, should you update the service pack level to SP4 or simply upgrade to Windows Server 2003, since management wants to upgrade anyway? What influences your decision?

you will need to install sp3 or sp4 for windows 2000 server rather than upgrade to windows server 2003. only exchange server 2003 is supported on windows server 2003, so upgrading your windows 2000 server systems to windows server 2003 will cause your exchange server 5.5 organization to fail.

2.

Describe the process for upgrading Exchange Server 5.5 to Exchange Server 2003 at the corporate office.

first you need to connect the existing exchange server 5.5 organization to active directory and have a two-way recipient connection agreement configured. but before doing so, you need to install sp3 or sp4 for windows 2000 server on at least the server hosting the active directory connector service. once you have the two directories replicating, you can install exchange server 2003 onto server07 and have it join the existing exchange server 5.5 organization. after the exchange server 2003 server is installed and the site replication service is configured, you can begin moving mailboxes from the exchange server 5.5 server to the exchange server 2003 server by using the active directory users and computers console. you should schedule the mailbox moves because users will need to update their outlook profiles to point to the new server. after the mailboxes are moved, you would move any connectors from the exchange server 5.5 server, as well as any public folder stores and other resources being hosted on the exchange server 5.5 server. once all of the resources are reallocated to server07, shut down server05. then repeat the process to move resources from server06 to server07.

Answers

1.

You will need to install SP3 or SP4 for Windows 2000 Server rather than upgrade to Windows Server 2003. Only Exchange Server 2003 is supported on Windows Server 2003, so upgrading your Windows 2000 Server systems to Windows Server 2003 will cause your Exchange Server 5.5 organization to fail.

2.

First you need to connect the existing Exchange Server 5.5 organization to Active Directory and have a two-way Recipient Connection Agreement configured. But before doing so, you need to install SP3 or SP4 for Windows 2000 Server on at least the server hosting the Active Directory Connector Service. Once you have the two directories replicating, you can install Exchange Server 2003 onto Server07 and have it join the existing Exchange Server 5.5 organization. After the Exchange Server 2003 server is installed and the Site Replication Service is configured, you can begin moving mailboxes from the Exchange Server 5.5 server to the Exchange Server 2003 server by using the Active Directory Users And Computers console. You should schedule the mailbox moves because users will need to update their Outlook profiles to point to the new server. After the mailboxes are moved, you would move any connectors from the Exchange Server 5.5 server, as well as any public folder stores and other resources being hosted on the Exchange Server 5.5 server. Once all of the resources are reallocated to Server07, shut down Server05. Then repeat the process to move resources from Server06 to Server07.

Case Scenario Exercise: Requirement 2

Page 5-43

1.

What tool do you use to retain the SIDs while migrating Contoso's user accounts to Litware, Inc., and what do you need to do to migrate the existing user passwords?

the active directory migration tool is designed to migrate user account data while retaining sid history and acl settings. the migration wizard is not a full-featured account migration tool; it is unable to migrate existing account information. it can only create new accounts in the target domain or match mailboxes to existing accounts. in order to migrate passwords, you have to install the password migration dll file using pwdmig.exe from the windows server 2003 installation cd and then create a .pes file to be used during the password migration.

2.

After successfully migrating Contoso's existing user accounts to the litwareinc.com domain, what do you need to do prior to running Dcpromo, removing the contoso.com domain, and joining Contoso's servers to the litwareinc.com domain?

migrating the user accounts with the active directory migration tool does not migrate the exchange mailboxes. the mailboxes are still associated with contoso user accounts, so you need to run the migration wizard to migrate the mailboxes to the litware, inc. exchange server organization and have the mailboxes associated with the migrated user accounts in the litwareinc.com domain. after running the migration wizard, users will need to log on to the litwareinc.com domain with their user accounts and edit their mail profiles to point to the new mail server.

Answers

1.

The Active Directory Migration Tool is designed to migrate user account data while retaining SID history and ACL settings. The Migration Wizard is not a full-featured account migration tool; it is unable to migrate existing account information. It can only create new accounts in the target domain or match mailboxes to existing accounts. In order to migrate passwords, you have to install the password migration DLL file using Pwdmig.exe from the Windows Server 2003 installation CD and then create a .pes file to be used during the password migration.

2.

Migrating the user accounts with the Active Directory Migration Tool does not migrate the Exchange mailboxes. The mailboxes are still associated with Contoso user accounts, so you need to run the Migration Wizard to migrate the mailboxes to the Litware, Inc. Exchange Server organization and have the mailboxes associated with the migrated user accounts in the litwareinc.com domain. After running the Migration Wizard, users will need to log on to the litwareinc.com domain with their user accounts and edit their mail profiles to point to the new mail server.




MCSA/MCSE Self-Paced Training Kit (Exam 70-284(c) Implementing and Managing Microsoft Exchange Server 2003)
MCSA/MCSE Self-Paced Training Kit (Exam 70-284): Implementing and Managing MicrosoftВ® Exchange Server 2003 (Pro-Certification)
ISBN: 0735618992
EAN: 2147483647
Year: 2003
Pages: 221

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net