• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 239
  • Last Modified:

The relationship between Exchange 2003 and Windows 2003 Global Catalog

Hi;

I read many questions today regarding on how to deploy Exchange 2003 on a W2K DC environment, currently; we have 5
5 DCs listed as below.  Because I want to deploy Exchange 2003 in my company and it looks like that if I don't have at least one Windows 2003 DC with Global Catalog, I can't use RPC over HTTPS.

Here is my DC infrastructure with 2 sites

Site 1 - Head Office (mycompany.com)

DC1 - W2K server, GC
DC2 - W2K server, GC, FSMO role, IM, RID
DC3 - W2K server, GC
HUBDC - Win2003 server, GC

Site 2 - Remote Office (bo.mycompany.com)
REMOTEDC - Win2003 server, GC

I want to deploy a Exchange 2003 on my Site 1 - Head Office, the Exchange 2003 will be installed on a new Windows 2003 server.

Because I have a HUBDC - Win2003 server in my Head Office site already, do I match the requirement for RPC over HTTP?  This HUBDC is used to replicate the Active Directory between Head Office DCs and the Remote Office DC.

If I can deploy my Exchange 2003 with this HUBDC, how Exchange 2003 to use the GC on HUBDC?

By the way, when I go to "Active Directory Users and Computers" on DC1, I found a "X-on RED" on HUBDC computer icon.  What happen to it?
0
KANEWONG
Asked:
KANEWONG
  • 3
  • 2
1 Solution
 
december41991Commented:
Right click server properties in the ESM.Directory access TAB and you could manually choose the GC which it should be using.
0
 
SembeeCommented:
It would appear from that list you would match the requirements for RPC over HTTPS.
However I would be looking to move the FSMO roles currently held by the Windows 2000 domain controller to the Windows 2003 domain controller. Best practise is to have the highest version hold those roles.

You will not need to manually set the domain controller in ESM. When you configure the registry entries for RPC over HTTPS, simply point the domain controller part at the Windows 2003 GC.

Simon.
0
 
KANEWONGAuthor Commented:
Hi Sembee;

Do you have the link on how to configure the registry entries for RPC over HTTPS?  Because HUBDC is a replicator between the parent domain (mycompany.com) and a child domain (bo.mycompany.com), if there is any conflict?
0
Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

 
SembeeCommented:
The registry changes for RPC over HTTPS are all over the internet. It doesn't take long to find them. I even have them on my web site at http://www.amset.info/exchange/rpc-http.asp

The DNS role of the machine shouldn't matter. As long as it is a global catalog domain controller then it should be fine.

Simon.
0
 
KANEWONGAuthor Commented:
After review your link, these are what I need to update on registries for both of Exchange and GC domain controller.

ON DOMAIN CONTROLLER REGISTRY (GC DOMAIN CONTROLLER)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters

Create a new key of type REG_MULTI_SZ

Name: NSPI Interface protocol sequences
Value: ncacn_http:6004

ON EXCHANGE 2003

If NetBios Name of my GC DC is "HUBDC", can I combine dc:6001-6002 and dc.domain.local:6001-6002 to hubdc:6001-6002 only?

And if the host name of my Exchange 2003 is "mail3.mycompany.com" for external and internal, can I combine followings...

From
exchange-server:6001-6002;
exchange-server.domain.local:6001-6002;

To
mail3.mycompany.com:6001-6002;

From
exchange-server:6004;
exchange-server.domain.local:6004;

To
mail3.mycompany.com:6004;

From:
exchange-server:593;
exchange-server.domain.local:593;
mail.external.com:593;

To
mail3.mycompany.com:593;

Because they are referred to the same Exchange 2003 server.

From
dc:6001-6002;
dc.domain.local:6001-6002;

To
hubdc:6001-6002;

From
dc:6004;
dc.domain.local:6004;

To
hubdc:6004;

From
dc:593;
dc.domain.local:593;

To
hubdc:593;

Because they are referred to same GC/DC

Your example
exchange-server:100-5000;
exchange-server:6001-6002;
exchange-server.domain.local:6001-6002;
dc:6001-6002;
dc.domain.local:6001-6002;
exchange-server:6004;
exchange-server.domain.local:6004;
dc:6004;
dc.domain.local:6004;
mail.external.com:6001-6002;
mail.external.com:6004;
dc:593;
dc.domain.local:593;
exchange-server:593;
exchange-server.domain.local:593;
mail.external.com:593;

0
 
SembeeCommented:
You cannot combine the registry entries. I haven't repeated the naming conventions by error.
You have to use both the name the server is known as on the internet and what it is known as on the LAN. If this is different, then both names have to go in to the registry.
Similarly, you need to use the name and the FQDN for all server names, except for the name that is used externally.

Those settings are what I use week in, week out when I do an Exchange build. I have a 100% success rate on them. Simply do a find and replace as I outlined on my web site, then put all the entries on to a single line and copy them in to the relevant place in the registry.

Simon.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now