J
Jason Robarts [MSFT]
Many of the commands on the version of repadmin that ships with Windows
Server 2003 and Active Directory Application Mode support a richer way of
specifying items. It is much easier to specify things like the name of a
naming context or a list of DCs to use in a command. Repadmin /listhelp
provides information on how to use these features.
For example the new repadmin /replicate command supports the following
syntax:
Repadmin /showrepl [DC_LIST [Source DC object GUID]] [Naming Context]
[/verbose] [/nocache] [/repsto] [/conn] [/all] [/errorsonly] [/intersite]
Notice I can specify a DC_LIST. Repadmin /listhelp indicates the following
as possible options for a DC_LIST (See repadmin /listhelp for more details):
DC_LIST = { <DC_NAME> | * | <part_server_name>* | site:<SITE_NAME> | gc: |
fsmo_<FSMO_TYPE>:<FSMO_DN> }
I'm particularly interested in <part_server_name>*.
In my enterprise the bridgeheads for my Data-Center-Site are named BHDC1,
BHDC2, BHDC3. To show the replication status on each of these DCs
I can use the command:
Repadmin /showrepl BHDC*
Another example is the repadmin /kcc command. It supports the following
syntax:
Repadmin /kcc [DC_LIST] [/async]
In the above DC_LIST description there is a FSMO_TYPE option. We find the
following in the repadmin /listhelp:
FSMO_TYPE = dnm | schema | pdc | rid | im | istg
..
"fsmo_istg:" - is a site specific quasi-FSMO, and takes the RDN of the site.
So to run the KCC on the ISTG of my Data-Center-Site I can write:
Repadmin /kcc fsmo_istg
ata-Center-Site
These are but 2 examples of new support in repadmin to make it easier to
use.
Jason
Server 2003 and Active Directory Application Mode support a richer way of
specifying items. It is much easier to specify things like the name of a
naming context or a list of DCs to use in a command. Repadmin /listhelp
provides information on how to use these features.
For example the new repadmin /replicate command supports the following
syntax:
Repadmin /showrepl [DC_LIST [Source DC object GUID]] [Naming Context]
[/verbose] [/nocache] [/repsto] [/conn] [/all] [/errorsonly] [/intersite]
Notice I can specify a DC_LIST. Repadmin /listhelp indicates the following
as possible options for a DC_LIST (See repadmin /listhelp for more details):
DC_LIST = { <DC_NAME> | * | <part_server_name>* | site:<SITE_NAME> | gc: |
fsmo_<FSMO_TYPE>:<FSMO_DN> }
I'm particularly interested in <part_server_name>*.
In my enterprise the bridgeheads for my Data-Center-Site are named BHDC1,
BHDC2, BHDC3. To show the replication status on each of these DCs
I can use the command:
Repadmin /showrepl BHDC*
Another example is the repadmin /kcc command. It supports the following
syntax:
Repadmin /kcc [DC_LIST] [/async]
In the above DC_LIST description there is a FSMO_TYPE option. We find the
following in the repadmin /listhelp:
FSMO_TYPE = dnm | schema | pdc | rid | im | istg
..
"fsmo_istg:" - is a site specific quasi-FSMO, and takes the RDN of the site.
So to run the KCC on the ISTG of my Data-Center-Site I can write:
Repadmin /kcc fsmo_istg

These are but 2 examples of new support in repadmin to make it easier to
use.
Jason