How to Seize FSMO roles on Windows 2003 Server Environment

To seize the FSMO roles by using Ntdsutil, follow the below steps:

1. On the domain controller, click StartRun and type Ntdsutil in the Open box, and then click OK.


2. Type roles, and then press ENTER.


Note: To see a list of available commands at any of the prompts in the Ntdsutil tool, type ? and then press


3. Type connections and then press ENTER.


4. Type connect to server <GDCPORTAL>, where <GDCPORTAL> is the name of the server you want to use, and then press ENTER.


5. At the server connections: prompt, type q, and then press ENTER again.


6. Type seize <role>, where <role> is the role you want to seize. For example, to seize the RID Master role, you would type seize rid master:

Options are:


7. You will receive a warning window asking if you want to perform the seize. Click on Yes

. clip_image013


Note: All five roles need to be in the forest. If the first domain controller is out of the forest then seize all roles. Determine which roles are to be on which remaining domain controllers so that all five roles are not on only one server.

· Repeat steps 6 and 7 until you've seized all the required FSMO roles.

· After you seize or transfer the roles, type q, and then press ENTER until you quit the Ntdsutil tool.

Note: Do not put the Infrastructure Master (IM) role on the same domain controller as the Global Catalog server. If the Infrastructure Master runs on a GC server it will stop updating object information because it does not contain any references to objects that it does not hold. This is because a GC server holds a partial replica of every object in the forest.

Difference between IPv4 and IPv6



Addresses are 32 bits (4 bytes) in length.

Addresses are 128 bits (16 bytes) in length

Address (A) resource records in DNS to map host names to IPv4 addresses.

Address (AAAA) resource records in DNS to map host names to IPv6 addresses.

Pointer (PTR) resource records in the IN-ADDR.ARPA DNS domain to map IPv4 addresses to host names.

Pointer (PTR) resource records in the IP6.ARPA DNS domain to map IPv6 addresses to host names.

IPSec is optional and should be supported externally

IPSec support is not optional

Header does not identify packet flow for QoS handling by routers

Header contains Flow Label field, which Identifies packet flow for QoS handling by router.

Both routers and the sending host fragment packets.

Routers do not support packet fragmentation. Sending host fragments packets

Header includes a checksum.

Header does not include a checksum.

Header includes options.

Optional data is supported as extension headers.

ARP uses broadcast ARP request to resolve IP to MAC/Hardware address.

Multicast Neighbor Solicitation messages resolve IP addresses to MAC addresses.

Internet Group Management Protocol (IGMP) manages membership in local subnet groups.

Multicast Listener Discovery (MLD) messages manage membership in local subnet groups.

Broadcast addresses are used to send traffic to all nodes on a subnet.

IPv6 uses a link-local scope all-nodes multicast address.

Configured either manually or through DHCP.

Does not require manual configuration or DHCP.

Must support a 576-byte packet size (possibly fragmented).

Must support a 1280-byte packet size (without fragmentation).

Useful Symantec links for troubleshoot client communication issue

Troubleshooting communication problems with Symantec Client Security 3.x or Symantec AntiVirus Corporate Edition 10.x

Symantec AntiVirus quick communications check