You are on page 1of 33

The Expert's Guide for

Exchange 2003
Preparing for, Moving to, and Supporting
Exchange Server 2003

by Steve Bryant



Chapter 3 Consolidating Your Exchange Services . . . . . . . . . . . . . . . . . . . 34
Server Ownership Costs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Exchange Server Proliferation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Consolidating Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Exchange 2003 and AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Front-End Exchange Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Front-End Servers and Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Balancing Front-End and Back-End Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Consolidating Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Storage Space and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuration and Memeory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Mailbox Consolidation Concerns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Creating Server Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Spreading the Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Deploying High- or Continuous-Availability Servers . . . . . . . . . . . . . . . . . . . . . . 50
Consolidating Mailbox Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Move Mailbox Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Consolidating Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Consolidating Your Exchange Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Consolidating Exchange 2003 and Exchange 2000 Organizations . . . . . . . . . . . . . . . . 52
Tools for Merging Exchange Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Using the Exchange Migration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Copying Public Folder Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Copying the Organizational Forms Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Copying Contacts from One Organization to Another . . . . . . . . . . . . . . . . . . . . . 54
Collecting Group Distribution Memebership . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Completing the Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
More Consolidation Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Next: Installing Exchange 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64


Chapter 3:

Consolidating Your Exchange Services
At the heart of most successful and cost-effective Microsoft Exchange 2003 and Exchange 2000
deployments lies consolidation. Fewer Exchange servers translates to fewer server licenses,
smaller data centers, easier administration, and a reduced cost of doing business. These benefits of
consolidation are often the desired end results that prompt – and justify budgets for – upgrading and
consolidating Exchange deployments. Estimating the savings that your consolidation efforts can realize
will require some intelligent speculation because you’ll derive your overall savings from multiple
In fact, Microsoft recently performed a consolidation that illustrates the potential for administrative
savings. With Exchange Server 2003, Microsoft reduced its 113 mailbox servers in 75 geographical
locations worldwide to 38 mailbox servers in 7 locations worldwide.

Server Ownership Costs
IDC estimated that 62 percent of 2002 server costs came from the additional staffing required to
support the servers. Another 23.1 percent of the costs came from downtime, with the balance
assigned to training, software, and hardware. IDC broke down its 2002 numbers for the annual cost
of Windows server ownership (per server) into the following server categories:
• File server $19,809
• Networking server $2,357
• Print server $17,369
• Security server $14,099
• Web server $6,461

Although reports about messaging costs offer various figures, I like to use an annual cost of $10,000
per server for most calculations. Whether your specific numbers are higher or lower, you can see
how quickly server-consolidation savings can add up. So the questions you’re probably asking right
now are “How did we get here?” and “Where did all these servers come from?”
In 2003, the Gartner Group noted that independent business units within companies – rather than
the company’s IT department – initiate more than 60 percent of all IT projects. The high proportion
of business units initiating deployments is especially true for Exchange because remote offices and
departments often decide they need more horsepower or an additional server – or worse still (in
terms of additional ports) their own SMTP domain or Microsoft Outlook Web Access (OWA) server.

Exchange Server Proliferation
Although you can certainly blame departmental projects for proliferation, Exchange 5.5 Server’s
limited scalability has also been a key factor. Most of Exchange 5.5’s scalability limits involved the

Brought to you by Quest Software and Windows & .NET Magazine eBooks

the security implications involved should make protocols an early priority.5 server. apparently the culprit had “tailgated” an employee into the building through a side door. I’ll then cover server consolidation. although Microsoft Outlook 98 offered a stable offline mode that permitted remote access to the Exchange server. As you know. the security team insisted that everyone come in and out the main doors so that security personnel needed to watch just one entrance for unauthorized access. Most remote offices wanted the same performance they enjoyed with local Microsoft Mail (MS Mail) and cc:Mail post offices. the less secure your network will be. Because business units drive many IT projects. His company was burglarized one afternoon.5 servers to “spread the load” – both to accommodate users and protocols and to maintain acceptable performance.1 shows a three-site design with multiple protocols in use. Moreover.5 servers too large because a 500GB database would take more than 15 hours to back up or restore). Chapter 3 Consolidating Your Exchange Services 35 limits of the Extensible Storage Engine (ESE) engine. you no longer need all those connections. you can place a couple of inbound servers for the mail protocols centrally to provide a redundant inbound path for email and OWA. I want to emphasize here some key points about the vulnerabilities that multiple protocols can create. and. a single database failure or corruption could mean certain death to the Exchange administrator who had decided to put all users on the same box (I won’t even mention how the OWA client performed). you probably can control how many and which protocols (and therefore ports) your company uses. I work all over the world and I get to hear many instructive stories. the more inbound ports you have open on your network. Fortunately. Instead. finally. site consolidation. Consolidating Protocols Although administrators often consider protocol consolidation only after they’ve deployed or upgraded Exchange. In short. Figure 3. One of my client companies has roughly 50 business units and as many Internet connections. Chances are you need to reduce the number of “entrances” to your network. you understand the risks and administrative nightmares. Thereafter. I’ll divide the subject of consolidation into distinct categories and begin with the lowest common denominator: protocols. Exchange organization consolidation. And. you now have more options. it wasn’t robust. many remote offices installed a small Exchange 5. For this discussion.) However. Although I’ll discuss security in more depth in Chapter 7. (I won’t discuss the potential problems that come with 50 Internet connections and possibly 50 firewalls. One customer described a security incident that put the virtues of consolidation in sharp perspective. Administrators didn’t want to scale Exchange 5. As an Exchange consultant. many companies needed additional Exchange 5. Also. companies often have multiple Internet connections. To achieve that performance. although you might not be able to control the number of firewalls on your network (whose protection can be somewhat offset by the monitoring and management challenges that different access rules create).NET Magazine eBooks . Brought to you by Quest Software and Windows & .

2. In Figure 3. 3. 4. A new virus or network attack could bring down all three sites because they’re all exposed to the Internet. Virus and antispam updates might not be in sync. From an SMTP perspective.1. a server or network failure stops inbound mail for that entire SMTP domain. a Demilitarized Zone or DMZ) and consolidate the Internet email services to better secure and stabilize the environment. so different locations might have different protection levels.e.1 Site design with multiple protocols SUv.. you can see that many inbound ports must be enabled to support each business unit. A better design would establish a clear boundary between the Internet and the email servers ( IMAP HTTPS Internet Other Sites SMTP POP Other Sites You can see several points of vulnerability in this design: 1. Three firewalls and their access rules are much more difficult to manage and monitor than one or two.36 The Expert’s Guide for Exchange 2003 Figure 3.NET Magazine eBooks . Brought to you by Quest Software and Windows & .

I want to point out that Exchange 2003 is smarter than I once thought. AD keeps mailbox information under several Exchange attributes in the Class object USER for each person who has a mailbox. And therein lay the magic. Brought to you by Quest Software and Windows & . But if you look at the Exchange objects in the Microsoft Management Console (MMC) Users and Computers snap-in. This notification lets each mailbox server (within the routing group) report the folder hierarchy as well. Exchange Edge Services.2 shows. Figure 3. You can configure Microsoft IIS to provide a boundary or configure Linux with Sendmail to accomplish the same purpose.NET Magazine eBooks .2 Exchange System Objects and Exchange Mailbox Store Each Exchange server in the routing group is notified of a hierarchy change. In your Exchange organization. you see that the public folder proxies (in the default top-level hierarchy) are also added to AD. Because its folders and mailboxes are published to Active Directory (AD). which will eventually play this role for SMTP and provide additional features as well. as Figure 3. Microsoft has recently announced a new product. The current Microsoft solution is to place Microsoft ISA Servers or Exchange 2003 front-end servers at the boundary. you have mailboxes on servers. Exchange 2003 knows to look in AD for Exchange resources. Other products and more sophisticated solutions also exist. and information about the folder structure is replicated. Chapter 3 Consolidating Your Exchange Services 37 You can establish a protective boundary for your organization in various ways. Exchange 2003 and AD Before I discuss front-end server deployment.

4 Exchange 2003 redirected request Mailboxes work similarly. the server to which I’m connected will perform a quick directory lookup and send me to the server that contains the data. All Exchange 2003 and Exchange 2000 servers can automatically redirect the OWA client. The Exchange 2003 server then redirects my request to the appropriate server that stores the data. When ServerA realizes it doesn’t have the folder I’m requesting. to the appropriate mailbox or public folder server. Exchange 2003 has redirected the request to the server that holds a replica of the OWATEST folder.38 The Expert’s Guide for Exchange 2003 Although the public folder exists on only one server in the routing group. Again. it performs a directory lookup to find the server that holds the data. By default. you could even consider DNS round-robin or some other way to provide DNS lookup for the server. as Figure 3.NET Magazine eBooks . Brought to you by Quest Software and Windows & . n Note The preceding paragraphs describe default behavior for Exchange 2003 and Exchange 2000. Figure 3. Exchange 2003 and IIS servers make a quick check to see which server holds the data. It doesn’t matter how you create the folder.4 shows. none of which depends upon Front-End Services or any special functionality. I’m attempting to connect to a public folder that exists only on Server2. An interesting aspect of this functionality is that you can have a single internal namespace for email and route users to their mail server automatically. this approach is default behavior for Exchange 2003 and Exchange 2000. In an environment with fast links. Figure 3. other Exchange 2003 servers can automatically redirect to the appropriate server. As Figure 3. If I use OWA to access a public folder that exists on a different server. an internal DNS alias of MAIL can route to a single Exchange 2003 server – and that server will automatically redirect the user to his or her appropriate mail server.3 shows. In other words.3 Using OWA to find a public folder In this case. and then redirects the client.

you can choose to turn it into a front-end server. An Exchange 2003 server is either a front-end server or a “regular” server – usually referred to as a back-end server when a front-end server is present. After you’ve installed your second Exchange 2003 server in the organization.NET Magazine eBooks . In this case. Making an Exchange 2003 server a front-end server is one of the easiest things you’ll ever do. No additional settings are involved for a front-end server.5 shows. Click OK and reboot the server to complete the transition. Chapter 3 Consolidating Your Exchange Services 39 Front-End Exchange Servers Now let’s talk about front-end servers. I right-clicked Server1 and selected This is a front-end server. as Figure 3. Figure 3.5 Converting an Exchange server to a front-end server Brought to you by Quest Software and Windows & . Open the MMC Exchange System Manager snap-in and expand the Servers node under your Exchange organization’s name. Right-click the server you want to convert to a front-end server and select This is a front-end server.

this time. but now it also handles authentication and all communications with the back-end server. Fortunately. as the dialog box in Figure 3. I enter the same information as before. However. I’m “proxied” to the appropriate mailbox or public folder server. So what have I done? By designating a server as a front-end server. The front-end server performs the same lookups as before.6 shows. I’m prompted for a password.7 shows.7 Front-end server password prompt Brought to you by Quest Software and Windows & .6 Using the front-end server In a front-end server test. Figure 3. it’s easy to change the server role back.NET Magazine eBooks . Figure 3. the front-end server doesn’t redirect me to the appropriate back-end server. I’ve instructed that server to no longer refer me to a server that holds requested information. as Figure 3. First. Let me demonstrate. Instead.40 The Expert’s Guide for Exchange 2003 n Note Making a server a front-end server prohibits that server’s access to the local stores for mailbox or public folder information. I try to open the OWA session from the front-end server.

NET Magazine eBooks . Next. So if you have an in-house application and don’t want to prompt the user for authentication.8 OWA session appearing to come from the front-end server Brought to you by Quest Software and Windows & . don’t use front-end servers. Notice in Figure 3.8 that the Address bar shows an Exchange directory on Server1. Chapter 3 Consolidating Your Exchange Services 41 n Note Front-end servers understand only basic authentication and always prompt for a password – even if you already have a token in memory. the front-end server acts like the back-end server it found. instead of redirecting me to the appropriate Exchange Server. Figure 3.

and the client then performs a GET request for an OWA session.9 shows by accessing http://server1/exchange from Internet Explorer (IE).com. Server1 – although the mailbox is actually on another Exchange 2003 server. Figure 3. In a typical situation. After the front-end server finds the GC server. the server that actually holds the data instructs the referring server to redirect the client. the client’s mailbox was on ServerA.42 The Expert’s Guide for Exchange 2003 As you see in the Address bar. To illustrate. I’ve included a packet trace I performed in the lab while a client requested an OWA session from the front-end server. The response arrives. Exchange servers search AD to find Exchange objects. However. the client performs a DNS lookup for Server1. it queries the AD to determine the mailbox server for the request.) The front-end server uses DNS to find the Global Catalog (GC) server.NET Magazine eBooks . the OWA session appears to come from the front-end server. Brought to you by Quest Software and Windows & . I started the process that Figure 3. front-end servers are directed to respond as if they held the data.bryant. First.9 OWA session request packet trace In this case. As I mentioned before. (Remember that Server1 is the front-end server.

WebDAV. and IMAP sessions are directed to the front-end server(s). then proxied to the appro- priate back-end or mailbox server located within the corporate network. The mailbox back-end server responds with information for the client. POP. A front-end server is designed to reroute Internet protocols to the appropriate back-end servers. When used in conjunction with XMLHTTP. Figure 3. Because WebDAV is based on HTTP. as Figure 3. OWA for Exchange 2003 is a prime example of this combination. HTTP. the front-end server begins to echo the client requests verbatim to the back-end server. Chapter 3 Consolidating Your Exchange Services 43 After the front-end server finds the appropriate back-end server. WebDAV can also define the XML post data structure. it’s an excellent way to code through firewalls. is a protocol standard for performing basic file system operations across the Web.10 Front-end and back-end servers responding to a client request n Note Another key component that lies at the heart of Exchange 2003 is Web-based Distributed Authoring and Versioning (WebDAV). a series of extensions of HTTP.NET Magazine eBooks .10 shows. (SMTP is handled a little Brought to you by Quest Software and Windows & .

front-end servers let you consolidate your inbound Internet protocols and help simplify and secure your Internet Other Sites SMTP POP IMAP HTTPS Front End Servers Exchange Exchange Other Sites Main Site A front-end server doesn’t “care” where a request originates.NET Magazine eBooks .44 The Expert’s Guide for Exchange 2003 differently in that the messages are spooled locally on the front-end server. you can leverage these central servers on behalf of other corporate-wide features such as Outlook Mobile Access and even remote procedure call (RPC) over HTTP. SportsCar. as Figure 3. In SUV. By reducing the number of inbound ports. Essentially.11 Front-end server protection layer Internet Exchange Trucks. then routed internally.) This layer of protection helps isolate the production mail servers and their data from the Internet. you make your environment more secure and easier to manage.11 shows. Figure 3. The front-end server will look in AD to find the source you’re requesting and proxy the request to that server on your behalf. Its sole task is to proxy the requests. Brought to you by Quest Software and Windows & . the front-end server has no inherent load-balancing characteristics nor can it provide your mail if your mail server is unavailable.

The peak on the right was generated when the client entered http://server1/exchange and accessed data on Server2 through the front-end server. As you can see. Chapter 3 Consolidating Your Exchange Services 45 Front-End Servers and Performance Interestingly. it lessens the load somewhat. the bottleneck continues to be the back-end servers. SSL doubles or more than doubles the processor use on the server and the amount of data sent over the wire. routing clients through a front-end server doesn’t dramatically reduce the load on the back-end servers. In most cases. front-end servers offer little performance gain apart from offloading Secure Sockets Layer (SSL) from the back-end servers. front-end servers support only basic authentication.12 Back-end server performance with and without front-end servers The peak on the left in Figure 3. SSL adds overhead to transactions. Figure 3. the load on the back-end server is slightly lower when access occurs through the front-end server. As you saw in the protocol traces. The front-end server acts as an IIS server and provides the controls you specify to the HTTP client. what exactly does a front-end server offload from back-end servers? • Authentication – As I mentioned previously. So.NET Magazine eBooks . You can see the degree to which the back-end server’s load is lightened in the performance comparison snapshot that Figure 3. the front-end server will handle SSL. Although a front-end server doesn’t hugely lighten the load on back-end servers. j Tip The overall recommendation to provide a good balance is one front-end server to four back-end servers. an AD domain controller (DC). • Controls – Your custom applications will use a set of tools or controls for the client. Brought to you by Quest Software and Windows & . and a GC for your domain.12 shows. If you use SSL. so offloading this overhead is helpful. the front-end server must be able to find your internal DNS Server. In most cases. The front-end server uses these tools to locate and communicate with the back-end servers. Balancing Front-End and Back-End Servers Based on this data.12 was generated when a client entered http://server2/exchange directly to access mail.

storage space and recovery determine the number of servers you need. add back-end servers as you typically would to overcome capacity issues on the mail servers. On quite modest equipment with dual processors. If your current backup and restore procedures can handle 50GB per hour and you have a maximum downtime window of 8 hours. Add front-end servers to provide redundancy to the browser clients and to add a single namespace. • Microsoft and security professionals highly recommend (many consider it a requirement) that you require HTTP Secure (HTTPS) for POP. IMAP. With Windows NLB. and HTTP traffic to protect not only the data. Storage Space and Recovery More than anything else. Brought to you by Quest Software and Windows & . and the answer depends on your service level agreements (SLAs) and uptime requirements explicitly defined or implied.46 The Expert’s Guide for Exchange 2003 As a general rule. If you’ve installed Microsoft SharePoint Portal Server or another program that might have disabled Kerberos support. each Exchange server should hold no more than 400GB of data. including access to the internal DNS and GC servers and the ability to communicate directly with the Exchange back-end servers. as well. HP and Dell both have some excellent hardware guides for Exchange that can help you identify the type of hardware you need for specific server types and numbers of Outlook users. I/O is much more important to Exchange. • Front-end servers do nothing with Messaging API (MAPI). messaging volume and message sizes for a given period of time into the future. Kerberos secures the channel between the front-end and back-end servers. so users will always be prompted for a password. • By which shows you how to correct the situation: http://www. but most importantly the logon credentials. you can successfully simulate thousands of users with ease.asp • You can implement Windows Network Load Balancing (NLB also formerly known as WLBS) to help balance the load on front-end servers. Your Outlook clients gain nothing from the introduction of a front-end server • Front-end servers require quite a bit of network access. Outlook clients (including Outlook Express and OWA) don’t create heavy CPU use on increase the allowed downtime in your SLA. or allocate a new server. Be careful that you consider both current capacity and capacity trends so that your environment can handle anticipated growth rates in messaging quantity. LoadSim is an excellent tool you can download to stress-test your servers with Outlook traffic. If you plan to increase quota limits in the near future make sure you take that into consideration.5) can handle thousands of users. you can put a collection of front-end servers into place to centralize all the inbound Internet protocols for a division or entire company. I’ll cover such security topics in more detail in later chapters. You’ll see rather quickly that a single Exchange server (even Exchange 5. you can reduce mailbox sizes.NET Magazine eBooks . you should look at the following Web page. Keep in mind the following six points about Exchange 2003 front-end servers: • Front-end servers use basic authentication. so that will likely be your primary concern. When the server load gets beyond that point. Consolidating Servers How many mailboxes can you put on a single Exchange 2003 server? That question is at the heart of any Exchange project.

Mailbox Consolidation Concerns The next question you need to answer is whether you want to run all of the mailboxes from one server (or a few servers). Chapter 3 Consolidating Your Exchange Services 47 Configuration and Memory For configuration and memory.NET Magazine eBooks . Exchange database reads are random. should be run on a separate server because you’ll need to install a Notes client and will probably need to reboot the server more often than an ordinary mailbox server. First. if you have 500 to 1000 users). Brought to you by Quest Software and Windows & . consider a mirrored array for each set of storage group transaction logs and a striped array for the databases in one storage group. because the spindles in the arrays can spin only so fast and the drive heads can occupy only one position at a time. j Tip You’ll find two exceptions to the preceding rule of thumb for Exchange Server service ratios: OWA servers that support SSL and Exchange application servers that regularly initiate complicated events might need more processing power. a heavily accessed database will contend with transaction log writes. At the same time. Second. you might not want to. If your database is on the same drive (which is a very bad practice and not recommended). To begin with. because transaction logs are deleted every night. The following factors affect this decision: • Foreign mail connectors – The Lotus Notes Connector. you face two concerns. you might even want to consider placing each database on a dedicated array. Although you probably could reduce your entire Exchange organization to a few servers.g. Memory and processor specifications are easy to define and plan for. you need to specify enough disk space to handle the data you plan to store or spool. avoid placing different types of programs and their data on the same set of disk-drive spindles as Exchange components. If you expect heavy or frequent database access (e. Different applications place different requirements on the drives and thus contend for them. for example. The result could be a slower operating environment. Moreover. the database transaction logs (not to be confused with the message tracking logs) are being written sequentially. which creates potential delays for all the programs that share the drive. with Outlook users experiencing pauses while Outlook opens folders or individual items. By caching as much data and as many processes as possible. you’ll probably experience a very fragmented Exchange Store. Given the way the overall process works. so a RAID array constantly moves the drive heads to seemingly random spots on the platters to find data. if your consolidation plan shows that you need to run multiple databases and storage groups on your server. Depending on the size of your Exchange databases and expected activity.. Exchange Server will use as much memory as you install. Exchange Server can reliably service thousands of simultaneous users on a server with as few as two Pentium II (or better) processors. drive fragmentation occurs. consider locating your Exchange databases and their transaction logs on completely different (and dedicated) arrays.

Although such a configuration lets you use cheaper servers because capacity is kept low. Should a server fail because of hardware or software issues. Clustering Clustering is often initially considered the “silver-bullet” for protection and redundancy in a design that has fewer servers. So how can you create redundancy in an Exchange network and still keep it as consolidated and cost-effective as possible? Let’s consider three widely used options: spreading the load.NET Magazine eBooks . Each server runs a local set of drives for the OS and uses the external device for the database stores and transaction logs.13 shows. Spreading the Load By placing your connector servers on dedicated equipment and placing the mailbox databases on separate Exchange 2003 servers. licensing and administration costs often make this configuration less desirable. clustering. Creating Server Redundancy Although this chapter is about consolidation. and deploying high-availability servers. as Figure 3. Later in this book. Brought to you by Quest Software and Windows & . we'll describe the savings gained by using Outlook 2003 in cached mode with Exchange 2003 mailbox servers. the need for redundancy sometimes outweighs the need for consolidation.48 The Expert’s Guide for Exchange 2003 • Remote offices – Companies with slow WAN links to remote offices will probably require an additional server – at least for the larger remote locations. While this will certainly affect the decision to place servers in smaller locations. Microsoft Clustering Services requires that similar machines share a common data storage device. the services on that machine alone would be affected. such as a Storage Area Network (SAN) or external drive array. the larger remote locations will likely still need a local server to expedite the delivery of local messages with large attachments and to help reduce the impact to the WAN link for large populations of mailbox users. • “Putting-all-your-eggs-in-one-basket” concerns – IT Managers (and administrators) are sometimes skeptical about placing all resources on one or just a few servers. you can mitigate some of the risk associated with server failure or database corruption.

The switchover from one node to another could take several minutes depending on the size and fragmentation of the Exchange databases. Exchange 2003 also offers you the ability to mix the configurations: Options such as active/active/active/passive are available.13 Microsoft Clustering Services configuration Active Node A Active Node B Active Node C Passive Node D C:\ C:\ C:\ C:\ G:\ H:\ I:\ J:\ K:\ L:\ DB1 LOGS1 DB2 LOGS2 DB3 LOGS3 Shared storage clusters rely on shared drives to store the Exchange log files and the databases. which might eventually support clusters as well. antispam software. In March 2004. Chapter 3 Consolidating Your Exchange Services 49 Figure 3.NET Magazine eBooks . Some Exchange features (e. Exchange 2003 has added support for up to 8-node active/passive clusters if you use Windows Server 2003 (Windows 2003) Enterprise Edition or Win- dows 2003 Datacenter Edition. Furthermore. Microsoft announced support for the iSCSI interface. because a clustered server runs its own OS and applications. it’s subject to separate licensing. You must license both Windows 2003 Advanced Server and Exchange 2003 Enterprise. Many External SCSI and Fibre Channel arrays support this configuration. you must purchase antivirus soft- ware. In addition. If one server should fail. In an active/passive configuration (in which only one server at a time is live). An active/active configuration (in which both servers are typically live and sharing the load) has a practical limit of roughly 3000 active MAPI sessions. and agents for each node. Brought to you by Quest Software and Windows & . Clustering for Exchange lets you load databases from one node onto another node in case of failure. the other server can load the databases and continue to service clients as the failed server.g. management tools.. as do many SANs. the foreign-mail connectors) and many third-party Exchange add-ons are not cluster-aware or only active/ passive aware. the number of concurrent sessions has no practical limit. In fact.

Because of its “roll-back” support. Digital Equipment (DEC) and the inheritors of that fault-tolerance knowledge. These platforms use redundant I/O modules. processor and memory modules. while the users (and you) are asleep. You can expect performance of roughly 1GB per hour. you’ll be able to reduce your server count with Exchange 2003. you can now let the tool run on a schedule or let a script initiate it. Consolidating Mailbox Servers Regardless of the approach you take to fault tolerance. as well as IBM. and other redundant hardware within the same system. The same level of protection is now available on the Windows platform. so don’t be disappointed if you see only a single migration thread when you move small batches of mailboxes. then Compaq and now Hewlett Packard (HP). In addition to its performance improvements. Any errors that occur during the migration would result in problematic mailboxes not being moved or moved with any corrupted items skipped. You can easily estimate the necessary space by looking at the Mailbox resources of the source mailboxes before the move. Failed components are taken offline. you’ll notice that the migration tool offers support for error logging and automatically leaves the old mailbox intact should corruption or other errors occur during the migration. I was surprised how well it worked. For years. so you can move multiple mailboxes at the same time. Moving mailboxes results in items being copied.NET Magazine eBooks . The tool generates a report at the end of the migration to detail which mailboxes it moved and to identify any errors it encountered. so be prepared for the data stores to grow larger than the size of the Exchange database .50 The Expert’s Guide for Exchange 2003 Deploying High. You can schedule the move to occur at night. The number of threads is based on the number of mailboxes you move. When you move mailboxes. Initial screens give you the option of instructing the tool to skip corrupted items and continue or skip the mailbox in which corrupted items occur entirely. Hitachi. and other non-Intel-based server equipment. You may want to explore fault-tolerant options in your research. Exchange management tools have let you move mailboxes from server to server. you can now script moving mailboxes. For example.edb file. have been building fault-tolerant solutions for more than a decade. Many companies still run critical business applications on dedicated IBM. when I first encountered a Stratus FT Server in 2001. Let’s say that you decide to balance the load on two servers manually. Moreover. their processes are re-routed before anyone is aware of a problem. depending on what your underlying infrastructure will support. Brought to you by Quest Software and Windows & . You’ll also find the consolidation process has improved. but Exchange 2003 offers some advanced features that make the job faster and more reliable.or Continuous-Availability Servers The concept of fault-tolerant servers isn’t new. which makes the company’s high-availability servers well worth a look. but you don’t want to move mailboxes to accomplish that purpose during the day. Exchange System Manager (ESM) lets you export the Mailbox resources page so you can bring the numbers into Microsoft Excel and calculate totals. NEC has purchased and improved upon the Stratus technology. keep the following factors in mind: • You’ll lose the single instance store. Move Mailbox Tool The new Move Mailbox tool is multi-threaded.

users need only launch Outlook to find the new server. Consolidating Sites Most remote Exchange servers exist to meet performance requirements.EDB) of the Exchange database prior to being moved. Outlook 2003 and Exchange 2003 now offer better options for slow networks. or third-party tools. rules probably won’t function. you can take either of the following approaches to collapsing your remote sites. the Exchange Migration Wizard.) • The Move Mailbox tool works for certain moves only. • Outlook clients will automatically correct the Outlook profile upon launch. Outlook clients and even OWA clients haven’t been terribly efficient on the wire. If you're moving from one admin group to another and the source server is Exchange 5. Chapter 3 Consolidating Your Exchange Services 51 • You can move mailboxes while users are logged on.EDB files will be much larger on the target server than they were on the source server. but the bottom line is that you can retire many of those remote servers. I’ll discuss client-server performance numbers in detail in Chapter 6. All other mailbox settings are retained. In addition. and your resulting . To move from server to server in the same Admin Group. If you need to move the mailbox across admin groups and the source server is Exchange 2000 or Exchange 2003.NET Magazine eBooks . The migration tool then collects the deltas before it deletes the mailbox on the source. Although you can move email messages while users are connected to Outlook. You can • collapse remote sites before you deploy Exchange 2003. Some lab testing I did in 1999 showed that just launching Outlook 97 created more than 100KB of network traffic. Brought to you by Quest Software and Windows & . The first pass copies email items from the source server and begins populating the target server. This scenario closely resembles the organizational move described in the following text because you’ll have to “brute force” copy the mailboxes over with ExMerge. As mailboxes are moved from Exchange 2000 or Exchange 2003.STM file) will be promoted to the rich text store (. you need only to use the ESM console to make the moves. you’ll lose distribution list membership along with delegate information. and Microsoft has made dramatic improvements in compression. caching directory lookups.5. Because the mailboxes you move will basically be new mailboxes. (Note that this is dependent on the original mailbox server remaining online until Outlook has connected once. If you deploy Exchange 2003. they’ll have to re-launch Outlook to get their email messages. The mobile users will be affected the most as the OST files will need to be rebuilt and the offline address books will need to be downloaded new. and Outlook client performance. Outlook clients will automatically be redirected to the correct server. and you’ll need to create a new Outlook profile for the client machine and configure it to point to the new server. any content in the streaming store (. After mailboxes are moved. The numbers associated with Outlook 2003 – when used in conjunction with Exchange 2003 – are substantially better due to compression and the new cached mode. This means that native storage is “lost” as part of the move mailbox process. The Move Mailbox tool is pretty clever in that it runs two passes. they put a lot of information on the network. then the organization must be set to Native mode. SP1 and use the Outlook profile modification tool to change the Outlook profile to the new server. you'll need to use the ESM from Exchange Server 2003. • Streaming content will be promoted to the Rich Text Store as part of the migration. In other words.

you don’t have to worry about a “point of no return” in the process of moving hundreds of users at once. such as those that involve Exchange 2003 or Exchange 2000 (or a mix of the two).) As you consolidate fairly current Exchange organizations. because you now must deal with AD and the security accounts. You’ll find the tool on the Exchange 2000 Service Pack 2 (SP2) CD-ROM. You’ll probably need several nights of moving mailboxes to get remote users onto the central server. Contacts. as well as email and public folders.823143&product=exch2003 for detailed information about the necessary configuration settings. Drafts. ExMerge is an efficient. or Blackberry service. public folders. The rest of this chapter describes a process for consolidating Exchange 2003 and Exchange 2000 organizations. Tasks. Before you can use ExMerge on Exchange 2003 and Exchange 2000 systems. you need to understand the nature. In fact.5 environment. and every folder created in the mailbox – from the source mailbox to the target server.aspx?scid=kb. no single wizard helps you perform all the necessary changes and additions. but I recommend that you get the most current version directly from Microsoft’s Exchange site. As you collapse your remote sites. This would not result in a “double” See http://support. (In an Exchange 5. unfortunately. the migration will be more like the mailbox moves I’ve already discussed except for the latency associated with the slow link.NET Magazine eBooks . For most remote locations. you would use ExMerge to connect to the source server. Consolidating Your Exchange Organization Merging Exchange organizations has. however. For example. Distribution Brought to you by Quest Software and Windows & . and risks of the task you’re tackling as you collapse one Exchange organization into another. Calendar. distribution groups. You’ll be copying multi-threaded migration tool that can access mailboxes on a source server and import the data into personal folder store (PST) files and ultimately onto a target Exchange server. select the mailboxes you want to copy. voicemail connector. become more complex since Exchange 2000. You need to get to know ExMerge because you’ll use it more and more with Exchange Server. ExMerge can then migrate items – Mail folders. you would need to replace a fax gateway. In this scenario. you could conduct the migration overnight by preloading the redundant gateways. You’ll need to rebuild any connector information on the central server. Because you can roll back if necessary. it’s the tool you’ll use to extract a single mailbox or item from an Exchange database restore. you can use Microsoft’s InterOrg synchronization tool from the Microsoft BackOffice Resource Kit. Second Edition. scope. Personally. so you must use several or look for third-party tools that offer an all-in-one solution.52 The Expert’s Guide for Exchange 2003 • collapse remote sites after you deploy Exchange 2003. • you could also decide to collapse the sites as you move. The process lets you keep your old and new systems running until the final merging. I have found it best to break these steps up into separate small projects in order to ensure focus on the moves.en-us. and contacts before moving the mailboxes. Public Folders. you’ll need to create an account that has permissions to the mailboxes you intend to populate. Sent Items. Consolidating Exchange 2003 and Exchange 2000 Organizations First. and select the target server.

the SMTP address will be used to address the message. and they let you perform the migration with few manual steps. You’ll need to change Outlook profiles manually or through a script to direct the users to the new server. put together a workstation (or two) with the following configuration: Windows 2000 or Windows NT. The Exchange Migration Wizard will bring these over. Using the Exchange Migration Wizard If you plan to merge Exchange organizations without third-party tools. One strength of the Exchange Migration Wizard is its ability to match up the accounts before committing to migrating any email messages.500 and. If you have few mailboxes to move and have already created the accounts. all offline users will need to create a new offline folder store (OST) file and download a new copy of the Offline Address Book(s).NET Magazine eBooks . For example. you’ll probably need to delete the nickname files that the Outlook client keeps. you can migrate Exchange 2003 and Exchange 2000 mailboxes to Exchange 2003 servers in different organizations.. including most of the old attributes. you need to capture the current public folders. such as the SMTP addresses. the wizard doesn’t address everything. The wizard also creates any necessary AD accounts in the target directory.g. the migration is worth the risk because a single organization is much more flexible and offers better collaborative functions than two organizations.400 or X. I run the Exchange Migration Wizard and copy the mailboxes. To get the mail moved over. When a person replies to a message. because the wizard is single-threaded. in some cases. However. they’ll move one at a time until the migration is complete. Copying Public Folder Data The next step – copying public folder data – involves a combination of several tools as well as a few custom applications. the following text provides a step-by-step walk-through with Microsoft tools and some light scripting. One of the final screens in the wizard lets you view the account matches and change the mapping if necessary. the old X. You can migrate accounts and change Outlook profiles with ease. Tools for Merging Exchange Organizations The easiest way to merge two Exchange organizations is to purchase migration tools from such vendors as Quest Software (including migration solutions from recent acquisitions of Aelita Software and Discus Data Solutions) or NetIQ. follow the wizard’s screens and move the mail. 100). For most companies I work with. Mailbox rules probably won’t function correctly. Outlook 97 or Brought to you by Quest Software and Windows & . Also. The capable tools these companies offer are all-in-one. For those who lack the budget for a third-party tool. as will third-party tools. you’ll probably use the Microsoft Exchange Migration Wizard. these third-party tools let you handily undo tasks. and Contacts from one Exchange organization into the other. Moreover. Chapter 3 Consolidating Your Exchange Services 53 Lists. For example. To do so. and they offer detailed reports about the migration. no matter how many mailboxes you migrate (e. Finally. replies to existing messages might fail if you don’t exercise great caution during the migration. Administrators who are considering purchasing a third-party tool will also benefit from a better understanding of the tasks involved. Delegate information won’t carry over smoothly – if at all. First. It is very important that the old mail proxy addresses for the users are migrated from the old organization to the new organization. Several functions won’t work correctly after the merge. With this most recent version of one of my favorite tools.

You’ll use this information later to restore the permission settings.OU=USERS. Upload the PSTs into the target public folder system. network access to your public folder server. Depending on the size of your public store. install on the workstations the PFAdmin tool from the \exreskit\tools\pftools\pfadmin directory on the Microsoft Exchange 2000 Resource Kit CD-ROM or download it from the Exchange 2003 site at Microsoft.chm file located in the Help folder on the CD-ROM for detailed instructions about the PFAdmin tool.targetaddress" The result of this command will be a file named collect.DC=oldcompany. close any open PST files and close Outlook. manipulate the file. then select the Forms tab. With one of the Outlook sessions.mailnickname. After the upload is complete. Select Manage to open the Forms Manager screen.chm Help file.objectclass. and then import the ACLs into the new structure. you can export the ACLs into a text file.54 The Expert’s Guide for Exchange 2003 later. In large migrations. After the copying process is complete. make sure you have permissions to the new organizational forms library and upload the forms you copied to the PST as before. After you run the Listacl command to generate the list.txt that contains the field specified in the command: dn: CN=Jason Sherry. If you follow the instructions in the exchtool. Use an Outlook client and your administrator account to systematically copy each of the folders in the public folder tree to a local PST file. Copying the Organizational Forms Library Now.DC=com changetype: add displayName: Jason Sherry mailNickname: JSherry objectClass: top Brought to you by Quest Software and Windows & . I recommend that you keep the PST file size less than 1 GB for stability and performance reasons. and access to the public stores on the source and target servers. use the PFAdmin information to reset the folder permissions on the newly created folders. select Properties. back up the organizational forms library – if such a library exists – on the server. Select all the forms on the left and click Copy in the center of the window to copy the forms to the PST. you can begin copying the public folder data.txt -r "(&(objectClass=contact)(mailnickname=*))" -l "display- name. Refer to the exchtool. In a nutshell. If you have permissions to the organizational forms libraries. Copying Contacts from One Organization to Another To collect the distribution group membership on the source domain. Finally. we can use the LDIF export function to collect the SMTP address and names from the source AD.proxyaddresses. Launch the following command from a batch file: ldifde -m -f collect. I’ve used as many as 20 computers to capture the public folder store among several PST files. Right-click the folder. In addition. you might need to use Outlook sessions on several machines to copy the data in a timely fashion. you need to create a text file that lists the ACLs on each folder.NET Magazine eBooks . create a new folder in the PST named Backup Forms. you should be able to select it from the left pane and view the available forms.

First.txt file and start again or remove all the entries and re-run the import phase.p=First Organizati. huh? Be sure to watch the status of the import because LDIF does not work well with duplicates. and then make the change to the export command.DC=newcompany. or if the import fails on an entry. To collect this information. if you need more fields than I have provided in this After your change is You'll need to change this file so that all references to the old forest are replaced with references to the new forest. At that point. Chapter 3 Consolidating Your Exchange Services 55 objectClass: person objectClass: organizationalPerson objectClass: contact proxyAddresses: SMTP:jsherry@hotmail. If the contact already exists.mailnickname.targetaddress" You can then modify the resulting file to import the information into the new AD structure. there should be only one change per entry: dn: CN=Jason Sherry.NET Magazine eBooks . Also. and members from all mail-enabled groups in the source AD. use the LDIF export function to collect the SMTP address.a= . Collecting Group Distribution Membership To collect the distribution group membership on the source domain.o=Exchange.a= . targetAddress: SMTP:jsherry@hotmail. you'll need to change all references to the old AD information: Brought to you by Quest Software and Windows & .OU=USERS.s=Jason Sherry.DC=com changetype: add displayName: Jason Sherry mailNickname: JSherry objectClass: top objectClass: person objectClass: organizationalPerson objectClass: contact proxyAddresses: SMTP:jsherry@hotmail. Actually.member. group name.p=First proxyAddresses: X400:c=us. you can either delete the successful entries from the collect.txt Pretty easy.proxyaddresses.s=Jason Sherry.o=Exchange. execute the following command to import these contacts into the new AD: ldifde -i -f collect.txt -r "(&(objectClass=group)(mailnickname=*))" -l "displayname.objectclass. use ADSI Edit to see the name of the field you wish to add. launch the following command from a batch file: ldifde -m -f collect. the whole import proxyAddresses: X400:c=us. targetAddress: SMTP:jsherry@hotmail. proxyAddresses: smtp:Sales@oldcompany.DC=newcompany.DC=oldcompany.DC=com After: dn: CN=Sales.OU=USERS.DC=com changetype: modify add: member member: CN=Phil George.DC=com changetype: modify add: member member: CN=Phil George. After: dn: CN=Sales proxyAddresses: X400:c=us.DC=com changetype: add displayName: Sales mailNickname: All-Sales objectClass: top objectClass: group proxyAddresses: X500:/o=First Organization/ou=First Administrative Group/cn=Recipients/cn=All- Sales proxyAddresses: SMTP:All-Sales@oldcompany.s=All-Sales.a= proxyAddresses: X400:c=us.NET Magazine eBooks .OU=USERS.DC=oldcompany. Later.OU=USERS.a= .DC=oldcompany.DC=com Brought to you by Quest Software and Windows & . The same changes will be needed in those entries as well: Before: dn: CN=Sales.56 The Expert’s Guide for Exchange 2003 Before: dn: CN=Sales Team.OU=USERS.OU=USERS.p=First proxyAddresses: smtp:Sales@oldcompany.p=First Organizati. the import file will contain the actual member list that is added after the initial list is imported.o=Exchange.DC=newcompany.DC=com changetype: add displayName: Sales mailNickname: All-Sales objectClass: top objectClass: group proxyAddresses: X500:/o=First Organization/ou=First Administrative Group/cn=Recipients/cn=All- Sales proxyAddresses: SMTP:All-Sales@oldcompany.

In many cases. Windows 2000. but not client-based rules). including Folder Agents. If not. other key aspects of the project are user acceptance and the overall smoothness of the transition from the users’ perspective. It is also important to understand that my references here are with all the users in the default USERS OU for both the source and target AD structures. and OST. and Rules (you can copy server-based Inbox Rules by using ExMerge 2000 to move the mailboxes. For example. This recreation process could mean some pain for Notebook users who need to resynchronize over a slow link. When you plan your consolidation. and Windows Server 2003 machines – and it will work for any version of Outlook. you'll need to make sure the import text file has the correct target OU listed for each account or contact. You'll need to change the NEWSERVER name to match the name of your target server and replace newserver. The collect scripts will find the entries no matter the OU. You can create the new profiles with an assortment of tools (e. The migration will affect Notebook users the most because they’ll need to recreate all previous OST and Outlook profile settings. Delegate Rights and Settings (both client and host). And you can find third-party tools to help you create profiles programmatically.5 environment). if you take this route. Chapter 3 Consolidating Your Exchange Services 57 A good search and replace should knock all these out in one step. However. the fun has just begun. However. you’ll experience problems later on because reminders will often break and links to the contacts folder as an address book often do not work properly. but the target scripts will work much better if you can place all the entries in a single OU. Brought to you by Quest Software and Windows & .14) you need to create if you wish to programmatically create new ones for the clients. Here is the . Completing the Consolidation At this point. such as PST file use. You should create a new Outlook profile for every user you move. You might be tempted to reuse the old Outlook profiles and just change the server name. You should probably leave the old ones intact to manually copy any settings the profiles might contain. However. the server parts of consolidation are the easiest because you can plan for most contingencies and work on the weekends or late at night.g. it might seem as if the most difficult parts of a large project are behind you. Folder with the DNS name of your server.REG file (Figure 3. keep the impact on users in mind. Bite the bullet and create new Windows XP. You can also script the creation of an Outlook profile by adding just a few registry keys to the client’s machine. This registry file will work on Windows NT. you’ll lose several functions.. when you move Exchange mailboxes from one organization to another (or site to site in an Exchange 5. the Office Profile Wizard).NET Magazine eBooks . "00036619"=hex:\ 00.00.00.a2.00.6c.00 "00036606"=hex: "01023d0c"=hex:7e.\\ 9c.00.41.b4.00.46.\ 00.6f. "00036605"=hex:03.\ 00 "001f3d13" "01023d0c"=hex:d8.00.95.f1. "001f3001" [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\13dbb0c8aa05101a9bb000aa002fc45a] "00036661"=hex:00.00 "00033009"=hex:00.00.00.b7.\ Brought to you by Quest Software and Windows & .9d.00.00.\ 44.36.7d.64.12.5a.b9.00.e1.9c.00.7d. "01023d01"=hex:a1.00.2e.\ 00.30.\ 04.fe.6f.00.2f.37.9f.fd. [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\1018e8b4de806342b370f3d513f342ec] "001f300a"=hex:63.54.a7.00.00.6b.aa.74.00.42.a8.\ 00.c0. File Windows Registry Editor Version "001f3d09" "001e6750"="NEWSERVER Profile" "001e6608"="NEWSERVER. "000b0412" "00036601"=hex: "00036604"=hex: Magazine eBooks .14 Example .00.00.6b. "00033e03"=hex:23.84.c3.74.00.7d. "01023d00" "01023d02"=hex:67.21.8a.bc. "001f3006" "01026601"=hex:40.31.d9.38.b9.00.31.6f.00.\ 00.00.\ 00.2b.\ 00.6e. "110265e0"=hex:0f.00.58 The Expert’s Guide for Exchange 2003 Figure "000b0413"" "001f662a"=hex:6e.\ [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files] "DefaultProfile"="NEWSERVER Profile" [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile] [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\0a0d020000000000c000000000000046] "000b0340"=hex:00.37.00.\\ "00036600"\ 61.00.b9.39.a7.2b.\ 73.2f.\ c8.\\ 43.6e.\\\ 33.00.\\ 34.41.41.c8.\ 15.00.2b.\\\ Chapter 3 Consolidating Your Exchange Services 59\ 1a.\ e1.\\ 41.43.46.\\\ 37.41.00.\ 2f.\ 00.30.a7.\ 30.c8.\ Brought to you by Quest Software and Windows & .01.00.\\\\\\ 46.\\\ 00.41.0f.\ 69.b4.\\ 00.00.4c.6f.00 "101f65e4"=hex:0f. "100365e3"=hex:\ 00.a7.6c.3d.44.\ 31.00.00.b4.64.53.dc.\ "100365e2"=hex:\\\\ 30.b4.\\ 42.\ Magazine eBooks .\\ 00.69.c0.\\ "100365e1"=hex:\\\\\ dc.31.1a.00.b4.\ 2f.\

31.00.69.b9.b4.\ 42.82.b4.8c.\ 00 "001f3d13"=hex:7b.2f.\ "00033e03"\ 00.1a.74.3d.\ 00.\\ 34.3d.00.b4.00.42.45.c8. "110265e6"=hex:0f.b4.\ e0.\ 64.b9.\\\ 40.46.\ 35.00 "010265ec"=hex: "000b65ea"=hex:01.\ 10.2f.32.2f.\ 00.41.41.\ 30.3d.\ 69.\\\\ 33.42.b9.2f.00.00.b4.\ 00.31.1a.\ 41.\\ 1a.b9.\ 36.00.a7.\ 00.00.dc.37.\\ c8.e1.2b.43.41.37.b4.\ 2f.34.30.NET Magazine eBooks .b9.\ 4c.\ "100365e5"=hex:\ The Expert’s Guide for Exchange 2003 00.00.dc. [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\522121b7579cad4f815965481963977e] "001f300a"=hex:45.40.d0.82.00.c0.\ 2f.31.b9.dc.00 "00033009"=hex:06.2f.39.00.00.b9.\ 00.b9. Brought to you by Quest Software and Windows & .\\\\\ 00.30.2d.\ e1.31.c0.\\ "000365eb"=hex:\ 43.\\ dc.2b.\ 00.\\\ "01023d0c"=hex:d8.00.6f. "001f3d09"=hex:4d.00.68 "001f3d09"=hex:4d.\ [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\7e9c76239d8799459feef1a71dfd133c] "001f3d0a"=hex:\ "0003660a"=hex:0a.31.00.44.a1.53.00 "00036609"=hex:\ 00 "001f3d13"=hex:7b.73.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\5254129a867d1e49bf8937208f135a06] "00033e03"=hex: "00033009"=hex:\\\ "001f3006"=hex:4d.\ 00.00.17 "001f3001"=hex: "001f300a"=hex: "00036609"=hex: "001f3001"=hex: "01023d0c"=hex:d8. [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\5acf76a3665511cea39a00aa004acafa] [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\67d962f70362044d93d9f4aa3ab5c3e3] "001f3001"=hex:4d.\ 00 "001f300a"=hex:\ "001f3d09"=hex:4d.74.6f. "001f3d13"=hex:7b.\ Brought to you by Quest Software and Windows & .\ "01023414"=hex:\ 00 "001f3006"=hex:4d.31.31.4c. "01023414"=hex: "001f3006"=hex:4d.\ "00033e03" "01023d0c"=hex:d8.\ 00 "001f3d13"=hex:7b.\ 00.NET Magazine eBooks .00.25.6e.00.6f.\\\ 45.00.00.\ 00.00.00.aa.a2.\ "0003660a"=hex:01.f0. Chapter 3 Consolidating Your Exchange Services 61 "00036609"=hex:0c.20.\ "0003660a"=hex: "00033009"=hex:

e3.00.89 [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\9207f3e0a3b11019908b08002b2a56c2] "01023d01" [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\8503020000000000c000000000000046] "0102300b"=hex:b1.20.NET Magazine eBooks "NextAccountID"=dword:00000003 [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\9375CFF0413111d3B88A00104B2A6676\00000001] "clsid"="{ED475414-B0D6-11D2-8C3B-00104B2A6676}" "Mini UID"=dword:56742a89 "Service Name" "LastChangeVer"=hex:08.6f.6e.00.73.00.\ "{ED475419-B0D6-11D2-8C3B-00104B2A6676}"=hex: "Account Name"=hex:4d.\ Brought to you by Quest Software and Windows & .\ 00.00.48.\ 97.80.f1. "101e3d0f" [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\9375CFF0413111d3B88A00104B2A6676\00000002] "clsid"="{ED475414-B0D6-11D2-8C3B-00104B2A6676}" "Mini UID"=dword:2460e6dd "Service Name"=hex:4d.60.7d.6f.00.63.3c.00.f1. "001f3001"=hex:4f.74.3a.00.b3.\ 42.62 The Expert’s Guide for Exchange 2003 "01023d00"=hex:52.87.8f.42.62.00.f0.66.72.31.\ "Service UID"=hex:d8.6c.20.dc.63.6e.64.00.6f.\ 64.4f. "01023d0e"=hex:7e.8a.df.f3.\ "01023d08"=hex:dc.a8.97.21.f3. "00033009"=hex: "001f3d0b" [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\9375CFF0413111d3B88A00104B2A6676] "{ED475418-B0D6-11D2-8C3B-00104B2A6676}"=hex: "01023d01"=hex:10.00.4d.00.a1.00.\ 00.3c "MAPI Provider"=dword:00000002 "Account Name" "001f3d09" "MAPI Provider"=dword:00000005 "Identity Eid"=hex: "XP Provider UID"=hex:67.00.79.a2.72.6c.6f.43.6f.6e. "Service UID"\\\ 9c.00.42.4d.00.\ "01023d02"=hex: [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\a10cb5608742104c853574c1b6642917] "001f3001"=hex:4d.0b.00.76.45.b4.73.00 "{ED475420-B0D6-11D2-8C3B-00104B2A6676}"=hex:02.00.41.fe.f1.75.69.9f. "001f3006"=hex:4d.54.00.b3.6f.60 "01023d08"=hex:dc.65.00.f1.00.2d.63.32.7d. "001f3d09"=hex:4d.68 "001f3d09"=hex:4d.e7. "101e3d0f"=hex: [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\d89ff04133504346a808966b8aa26668] "001f3001"=hex:4d.4c.00.9a.6c.73.6b.f8.00.32.\ 00.c3.00.00 "01023d01" "00033e03"=hex:\ 9c.00.2d.00.6f.\\\\\ 00 "001f3d13"=hex:7b.\ "001f3d0b"=hex:45.7d.\ 00 "001f3d13"=hex:7b.68 "001f3d09"=hex:4d.00.\\ "01023d0d"=hex:13.8f.\ 2e.00.39.17 "01023d00"=hex: "01023d0c"=hex:d8. [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\dc30434b7a0ef849aa75c37a99b3e7cd] "001f3001"=hex:4d.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\dca740c8c042101ab4b908002b2fe182] [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Pro- files\NEWSERVER Profile\f10b187cfe97204387dc7d32bab3d160] Brought to you by Quest Software and Windows & .fe. "001f3006"=hex:4d.00.00.41.\ Chapter 3 Consolidating Your Exchange Services 63 "001f300a"=hex: "00033009"=hex: "00033009"=hex:00.00 "001f300a"=hex:45.NET Magazine eBooks .4b.76.6f.3a.d9.\\ 00.6f.\\\ "001f3d13"=hex:7b.\ "01023d02"=hex: "00033e03"=hex: "001f3d0a"=hex:\ 6c.00.6f.\\ 63.39.31.\ 00.2e.36.0b.00.00 "00033009"=hex:00.00.00 "01023d0c"=hex:d8.6f.0c.

\ 00. you should be able to move the computer and user accounts in an hour. not the old ones.53.20. tools that you can download from the Microsoft Exchange Server site.00.00.54.\ 00 "001f3d13"=hex:7b. Those who move to Exchange 2003 from Exchange 5. Next: Installing Exchange 2003 The next chapter will discuss installing Exchange Server 2003. You’ll need to plan for DNS and SMTP changes before you migrate mailboxes.2d.20.73.66.\ 73. Your users need to know that they must log on to the new domain (they might require no more than some basic instructions).g.6f.31.. or third-party tools available from vendors. and how to use the Exchange Server deployment wizards to prepare the systems for you.20.00.8a. "001f3006"=hex:4d.6f.00. In addition. Larger deployments will obviously take much more planning and many helping hands. voicemail connector.\ you can use tools available on the server CD-ROMs. including preparing the server and migrating to Exchange 2003.00 "00036609"=hex:00.6e.70.64 The Expert’s Guide for Exchange 2003 "001f3001"=hex:4d. followed by about 8 hours to move the machines from the old domain into the new domain. Consolidation is one of the key aspects of efficient Exchange deployments. "00033009"=hex: how to create connection agreements manually.39.5 server can’t be upgraded to Exchange Server 2003?). a reorganization such as this Exchange consolidation usually includes migrating an SMTP domain.00.73. you’ll need to replace a fax gateway. or Blackberry service. "00033e03"=hex:24.2d.67. Having said that. I’ll also cover in detail the requirements of the Active Directory Connector (ADC). To assist with more complicated consolidation efforts.00 "001f300a"=hex: More Consolidation Details Also.34.00.7d.31. Later (but as soon as possible).32.00.5 will need extensive information (e. In a smaller deployment (e.66.35. Brought to you by Quest Software and Windows & . "01023d0c"=hex:d8.\ 45.43.00.a8.00. 150 users).08. you can provide a clean break by removing the trusts and unplugging the old domain and old Exchange server from the network.00. As with site consolidations. Magazine eBooks .\ you’ll need to rebuild any connector information in the source organization.68 "001f3d09"=hex:4d. Did you know that an Exchange\\ 00.00. remember that the new AD account is associated with the new mailboxes.00. remember that Exchange site and organizational consolidation projects will affect end users and their current configurations and data. For example. I prefer to copy the computer accounts and do the domain-migration work over a weekend and use Systems Management Server (SMS) or Office Wizards during the week to automate the necessary changes to the Outlook profiles..72.