In this article I will give you a Step by Step solution how to rename a Windows 2003 domain with Exchange 2003 installed. This article will not explain every step how to do a domain rename. This is documented in the “Step-by-Step Guide to Implementing Domain Rename“. You will find the link at the end of this article. The Windows Server 2003 Active Directory Domain Rename Tool provides a supported methodology to rename one or more domains in an Active Directory forest. The DNS name and the NetBIOS name of a domain can be changed using the domain rename procedure. Note that implementing domain rename is a complex undertaking that requires thorough planning and a good understanding of the domain rename procedure.
Deployment & Migration
In this article I will give you an overview about basic Public Folder Administration Tasks with Exchange 2003 and the use of tools like PFMIGRATE.
In this article I will give you a step by step solution to deploy the Site Consolidation Tools for Exchange 2003 in Mixed Mode. Have you ever tried to move a Mailbox between different administrative Groups in Exchange 2003 Mixed Mode? – It doesn’t work. What do you do when you are deploying an Upgrade from Exchange 5.5 to Exchange 2003? What do you do with the Outlook Profiles? How can you update these settings to reflect the new Server? The answer is easy. Install Exchange 2003 SP1 and the updated version of the Exchange 2003 Deployment Tools and life will go easier. You will see this later in this article.
The Inter-Organization Replication tool was initially released as part of Microsoft Exchange Server 5.5 SP3, with an Update for Microsoft Exchange Server 2003. This tool is used to replicate public folder content and free and busy information between different Exchange organizations. It allows the coordination of meetings, appointments and contacts. In this article I will give you a step by step solution to setup an InterOrg Replication between two different Exchange 2003 Organizations.
The Windows 2003 Forest is the logical boundary of Exchange 2003. Microsoft recommends deploying only one Active Directory Forest whenever possible. There are many reasons for single forest deployment beginning with the administrative overhead through the need to synchronize the Global Address Lists of Exchange 2003 between two forests to provide a central GAL. But what if you have more than one forest with Exchange 2003 (through a merger or acquisition)? In this article I will explain in high level steps how to synchronize the GALs (Global Access Lists) of two Exchange 2003 organizations with the help of IIFP. This article should give you an overview about this complex process.
Exchange 2003 uses the Windows Server 2003 PKI architecture to provide secure e-mail services for Exchange users. Exchange 2000 KMS is no longer supported. The Windows 2003 Enterprise CA provides central key archiving and recovery. This article explains in high level steps how to migrate an Exchange 2000 KMS database to a Windows Server 2003 CA.
We would like to welcome Microsoft MVP Henrik Walther to our team of authors as he presents his first article to MSExchange.org readers. As companies seems to start their Exchange 2003 deployments way faster, than was the case with Exchange 2000, I thought it was about time to provide you with information on how you handle an in-place upgrade from Exchange 2000 to 2003.
Many companies are still using Exchange Server 5.5 as their primary email and collaboration system. With the end of Microsoft’s support of this release within 2003 they have to decide to move to a new release of Exchange Server. Within this article you will get a detailed overview on how to migrate an Exchange 5.5 directory to a new Windows Server 2003 supported Exchange Server 2003 environment. Because an in place upgrade is not supported, it won’t be covered in this article.
Moving users from using an internal POP3/SMTP server can be a tricky and costly business, with many pitfalls. The Exchange IFS "M" Drive can be used to ease some of these migration scenarios.
Active Directory and Exchange allows you to provide service to more than company without the need to build a separate domain / forest for each hosted company. The following article describes a simple shared hosting scenario where multiple sister companies are shared using the same Active Directory domain and can interoperate with each other.