DSA_LIST = { | | | site: | gc: | nc: | pnc: | mnc: | fsmo_ : } Examples: "*" = All DSAs in the enterprise/forest/configuration ...

DSA_LIST = {  | * | * | site:              | gc: | nc: | pnc: | mnc: | fsmo_: }       Examples:     "*" = All DSAs in the enterprise/forest/configuration set.     "part_server_name*" = would pick "part_server_name_dc_01" and "part_server_name_dc_02"                 but not server "part_server_diff_name".     "site:east_site1" = All DSAs in site "east_site1".     "gc:" = All GCs in the enterprise.     "nc:DC=fabrikam,..." = All DSAs hosting DC=fabrikam,...     "pnc:DC=fabrikam,..." = All DSAs hosting a partial copy of DC=fabrikam,...     "mnc:DC=fabrikam,..." = All DSAs hosting a master copy of DC=fabrikam,...     "fsmo_pdc:DC=my-corp-dom,DC=com" - repadmin runs against the PDC in the NC "DC=my-corp-dom,DC=com"     "fsmo_istg:east_site1" would pick the ISTG for the east_site1 site.  Additional option for DSA_LIST:  /homeserver:[dns name]     The initial DS server that facilitates DSA_LIST expansion is called the homeserver.     If the DSA_LIST argument is a resolvable server name (such as a DNS or WINS     name) this will be used as the homeserver.  If a non-resolvable parameter is used      for the DSA_LIST, repadmin will use the locator to find a server to be used as the      homeserver.  If the locator does not find a server, repadmin will try the local box (port 389).  The      /homeserver:[dns name] option is available to explicitly control home server selection.      This is especially useful when there are more than one forest or configuration set possible.  For      example, the DSA_LIST command "fsmo_istg:site1" would target the locally joined      domain's directory, so to target an AD/LDS instance, /homeserver:adldsinstance:50000      could be used to resolve the fsmo_istg to site1 defined in the ADAM configuration set on      adldsinstance:50000 instead of the fsmo_istg to site1 defined in the locally joined     domain. FSMO_TYPE = dnm | schema | pdc | rid | im | istg     NOTE: different types of FSMOs require different base DNs/RDNs.     "fsmo_dnm:" - is an enterprise wide FSMO, and doesn't take any DN.     "fsmo_schema:" - is an enterprise wide FSMO, and doesn't take any DN.     "fsmo_pdc:" - is a domain specific FSMO, and takes the DN of the domain the user wants.     "fsmo_rid:" - is a domain specific FSMO, and takes the DN of the domain the user wants.     "fsmo_im:" - is a partition/NC specific FSMO, and takes the DN of the NC the user wants.     "fsmo_istg:" - is a site specific quasi-FSMO, and takes the RDN of the site. DSA_NAME = { . |  |  |  |  }     . = Tells repadmin to try to pick one for you.     adlds_dns:ldap_port = specifies a specific AD LDS instance.     server_dns = specifies a specific server by DNS.     dsa_guid = specifies a specific server by its DSA GUID.     server_obj_rdn$service_short_name = specifies a specific AD LDS instance by its full server object rdn.     server_obj_rdn = specifies a server by its server object rdn (usually the same as its NetBios name)         The "$service_short_name" is not necessarily needed, but the DSA will only find a server, if         the portion of the server_obj_rdn specified in unambiguous.     dsa_dn = specifies a server by the DN of its DSA object. OBJ_LIST = { ncobj: | dsaobj: }     "ncobj:" = means use the DN of NC Head specified in NC_NAME.     "dsaobj:" = means use the DN of the DSA we're connected to. NC_NAME = { config: | schema: | domain: }     "config:" = Configuration Directory Partition.     "schema:" = Schema Directory Partition.     "domain:" = Domain Directory Partition for the Domain of the DC repadmin is running against. OBJ_LIST OPTIONS = { /onelevel | /subtree} /filter:     With these options, the showattr and viewlist commands can be used to cover a list of objects,     instead of just a single object. NOTES:  o The * in wildcards are evaluated by LDAP.  o Some options are not valid in AD LDS such as "gc:", "fsmo_pdc:", "fsmo_rid", "domain:", etc