: A Different Mind-set"> But its not as simple as it sounds. Dealing with Active Directory and Exchange requires a different mind-set for administrators used to previous versions of Exchange, according to Al Belfield, senior network system consultant at International Network Services Inc., in Hartford, Conn. Belfield is managing an Exchange 5.5-to-Exchange 2000 migration for a large enterprise client. "In Exchange 2000, the Exchange server no longer holds its own directory," said Belfield. "The mailbox is just an attribute of the Active Directory account.""You have to replicate directory information from 5.5 to Active Directory and establish a transport mechanism to pass mail back and forth while youre doing it," Belfield said. "One of the big concerns is coexistence between the two systems as youre doing the migration. And you have to have enough time to move from the public folders in 5.5 to the new system." Neither Duchemin nor Belfield thinks customers should feel any imperative to migrate unless they are going to take advantage of specific features in Exchange 2000. "Im not sure ... that it is urgent to move from 5.5, as the movement from 2000 to Titanium, .Net, etc., could be not too easy," said Duchemin. "We could have the same issues [migrating from] 5.5 to 2000 in 2000 to Titanium. The migration from 5.5 to Titanium might not be any worse." Additional reporting by John S. McCright Related Stories:
Exchange Titanium Release to Focus on Mobile, Outlook
Exchange 2000 Gets DoS Patch
Exchange to Support CRM
Belfield said that moving accounts from multiple account domains in large organizations with multiple resource forests to Exchange 2000, which supports just a single account domain in Active Directory, has been particularly challenging. However, he said Microsofts Active Directory Connector has met most of his migration needs.