transfer the GC

M

ming \(HK\)

Dear All,

This is my company scenario:

old server -------------------------> new server
(w2k + e2k) (migrate mailbox) (w2k + e2k)

I have already tranfer all the mailbox + 5 FSMO

Howver it always said something "no rpc server unavailable" , "No GC server
in domain"... I won't use the old server anymore. Any tricky way that can
transfer GC to new server successfully?

best Regards,

Ming
 
D

Deji Akomolafe

GCs are not "transfered", they are made or unmade. Go to your "Active
Directory Sites and Services". Open the Site where the new server is
located. Open "Servers". Open your server. You should see "NTDS Settings".
Right-click on that and click "Properties". You should now see an option to
make this server a "Global Catalog". Check that option. wait for a while,
then reboot the Server.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
 
M

ming \(HK\)

already done this step along with reboot but the problem still persisted.
Actully, do I need to demoted the old server?

Thx !!
 
G

Guest

A demotion followed by a new promotion of the OLD server
is a good idea, but make sure the connectivity is working
well.

Alseo check the new server is a GC server because if it's
not true you'll LOOSE ALL THE DOMAIN INFORMATION!!

Moreno
 
M

ming \(HK\)

thx for your information!!
So that mean I can't roll it back if the demotion is completed?


A demotion followed by a new promotion of the OLD server
is a good idea, but make sure the connectivity is working
well.

Alseo check the new server is a GC server because if it's
not true you'll LOOSE ALL THE DOMAIN INFORMATION!!

Moreno
 
M

Moreno

Ok Ming,

I'll explain in detail all the scenario.

In your LAN there are, now, TWO server, the OLD W2K + E2K
server and the NEW W2K + E2K server.
I suppose, when you started the migration to the NEW
server, that the NEW server was configured to be A DOMAIN
CONTROLLER for the DOMAIN; also, now I suppose that the
new server is a GLOBAL CATALOG server if you applied DEJI
suggest.

In this situation WE HAVE TWO DOMAIN CONTROLLERS and, at
least, one of this is a GLOBAL CATALOG SERVER but I
believe that now BOTH your server are GLOBAL CATALOG
SERVER (you can verify this by applying the DEJI suggest
to the OLD server).
At this point, the OLD W2K server (domain controller and
probably GLOBAL CATALOG server) can be DEMOTED to become a
normal server using DCPROMO.EXE.

This is possible BECAUSE in the LAN exists the OTHER
GLOBAL CATALOG server that stores ALL the ACTIVE DIRECTORY
database, so it will be possible, after the demotion of
the OLD server, to authenticate all the users and, in
general, to manage ALL the Active Directory schema.

If, for example, we suppose that the NEW W2K + E2K server
is NOT a GC server while the only GC server is the OLD
server, when you DEMOTE the OLD server to normal server
you will LOOSE the domain information because a normal
server stores only a PARTIAL REPLICA of the AD database
and NOT ALL the database.
In this case the NEW server will no longer be able to
refer to a GLOBAL CATALOG server and I think you will have
a lot of serious problems!!

For this reason, I also suggest you a SECOND possible
solution you can try:

1) take a PC and make a new FRESH installation of W2K
server;

2) when you finish the installation, PROMOTE this third
server to DOMAIN CONTROLLER for the existing domain;

3) transform this third machine to be a GC server by
checking the GC box as explained in the DEJI post;

4) wait for a complete replica of all the AD schema to the
new GC server;

Doing this operation I suppose ALL the DNS works
correctly; it is better for you to transfer ALL the DNS
service to the NEW W2K + E2K server.

At this point you will have at least TWO GC server in your
LAN (the NEW W2K + E2K server and the THIRD server) and
you can proceed to DEMOTE the OLD W2K + E2K server without
problems because you have not ONE but TWO GC server.

When you DEMOTE a domain controller to be a NORMAL SERVER
again, it is important that, at least, ONE global catalog
server exists in the LAN because when you DEMOTE the LAST
global catalog server, this operation REMOVE ALL THE
DOMAIN.

Hope this helps you.

Moreno.

========================================================
This posting is provided "AS IS" with no warranties, and
confers no rights.
Please do not send e-mail directly to this alias. This
alias is for
newsgroup purposes only.
========================================================
 
M

ming \(HK\)

Hi Moreno,

Thank you very much for your detail information!

Actually, I didn't demote the old server. Even I checked the box "GC" in new
Server, it still prompted the message " cannot find GC server..." then I
restore it by checked the box "GC" in the old server. Is it the replication
time not enough (around 10 mins)? How do I know that the new PC is acted as
a "GC" server?

Best Regards,

Ming

Ok Ming,

I'll explain in detail all the scenario.

In your LAN there are, now, TWO server, the OLD W2K + E2K
server and the NEW W2K + E2K server.
I suppose, when you started the migration to the NEW
server, that the NEW server was configured to be A DOMAIN
CONTROLLER for the DOMAIN; also, now I suppose that the
new server is a GLOBAL CATALOG server if you applied DEJI
suggest.

In this situation WE HAVE TWO DOMAIN CONTROLLERS and, at
least, one of this is a GLOBAL CATALOG SERVER but I
believe that now BOTH your server are GLOBAL CATALOG
SERVER (you can verify this by applying the DEJI suggest
to the OLD server).
At this point, the OLD W2K server (domain controller and
probably GLOBAL CATALOG server) can be DEMOTED to become a
normal server using DCPROMO.EXE.

This is possible BECAUSE in the LAN exists the OTHER
GLOBAL CATALOG server that stores ALL the ACTIVE DIRECTORY
database, so it will be possible, after the demotion of
the OLD server, to authenticate all the users and, in
general, to manage ALL the Active Directory schema.

If, for example, we suppose that the NEW W2K + E2K server
is NOT a GC server while the only GC server is the OLD
server, when you DEMOTE the OLD server to normal server
you will LOOSE the domain information because a normal
server stores only a PARTIAL REPLICA of the AD database
and NOT ALL the database.
In this case the NEW server will no longer be able to
refer to a GLOBAL CATALOG server and I think you will have
a lot of serious problems!!

For this reason, I also suggest you a SECOND possible
solution you can try:

1) take a PC and make a new FRESH installation of W2K
server;

2) when you finish the installation, PROMOTE this third
server to DOMAIN CONTROLLER for the existing domain;

3) transform this third machine to be a GC server by
checking the GC box as explained in the DEJI post;

4) wait for a complete replica of all the AD schema to the
new GC server;

Doing this operation I suppose ALL the DNS works
correctly; it is better for you to transfer ALL the DNS
service to the NEW W2K + E2K server.

At this point you will have at least TWO GC server in your
LAN (the NEW W2K + E2K server and the THIRD server) and
you can proceed to DEMOTE the OLD W2K + E2K server without
problems because you have not ONE but TWO GC server.

When you DEMOTE a domain controller to be a NORMAL SERVER
again, it is important that, at least, ONE global catalog
server exists in the LAN because when you DEMOTE the LAST
global catalog server, this operation REMOVE ALL THE
DOMAIN.

Hope this helps you.

Moreno.

========================================================
This posting is provided "AS IS" with no warranties, and
confers no rights.
Please do not send e-mail directly to this alias. This
alias is for
newsgroup purposes only.
========================================================
 
G

Guest

Tipically, the EVENT VIEWER tells you if the operation has
been completed successfully.
 
M

ming \(HK\)

Yes. I received this message. Then I can start demotion?

Tipically, the EVENT VIEWER tells you if the operation has
been completed successfully.
 
M

Moreno

Hi Ming,

I see your message only now......

....the MAD.EXE error seems to be an Exchange problem...

For this, please try to post in
microsoft.public.exchange2000.active.directory.integration

Sorry can't help you but I prefer to redirect you to an appropriate
newsgroup.

In general, GC problems can be resolved using the tools for the AD
management, but in your case Exchange Server makes lot of modifications in
your AD schema and I don't want to give you suggestions that can create
problems.

Sorry again!

Bye!

Moreno
 
M

ming \(HK\)

thx for your help!!

Moreno said:
Hi Ming,

I see your message only now......

...the MAD.EXE error seems to be an Exchange problem...

For this, please try to post in
microsoft.public.exchange2000.active.directory.integration

Sorry can't help you but I prefer to redirect you to an appropriate
newsgroup.

In general, GC problems can be resolved using the tools for the AD
management, but in your case Exchange Server makes lot of modifications in
your AD schema and I don't want to give you suggestions that can create
problems.

Sorry again!

Bye!

Moreno
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top