4.4.1 Replica DC Sends Out CMD_NEED_JOIN to PDC

COMM_BOP (4 bytes):

 00 00 00 00

COMM_COMMAND (4 bytes):

  
 21 01 00 00

COMMAND: CMD_NEED_JOIN

COMM_TO (118 bytes):

  
 10 00 00 00 1a b2 f4 54 fd 03 74 43 8e 3b 28 75 e7 40
 d9 58 5e 00 00 00 73 00 68 00 69 00 63 00 6f 00 2d 00
 74 00 65 00 6d 00 70 00 2d 00 31 00 2e 00 73 00 68 00
 69 00 63 00 6f 00 2d 00 6f 00 66 00 66 00 69 00 63 00
 65 00 2e 00 6e 00 74 00 74 00 65 00 73 00 74 00 2e 00
 6d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00
 2e 00 63 00 6f 00 6d 00 00 0

GUID: 54f4b21a-03fd-4374-8e3b2875e740d958

Name: shico-temp-1.shico-office.nttest.microsoft.com

Notes:

54f4b21a-03fd-4374-8e3b2875e740d958 is objectGuid of the following object:

CN=SHICO-TEMP-1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=shico-office,DC=nttest,DC=microsoft,DC=com

shico-temp-1.shico-office.nttest.microsoft.com is the DNS host name of the primary domain controller (PDC).

COMM_FROM (50 bytes):

  
 10 00 00 00 e6 87 d1 e5 aa 12 df 48 ab c1 d7 94 0a e0
 80 4c 1a 00 00 00 53 00 48 00 49 00 43 00 4f 00 2d 00
 54 00 45 00 4d 00 50 00 2d 00 32 00 00 0

GUID: e5d187e6-12aa-48df-abc1d7940ae0804c

Name: SHICO-TEMP-2

Notes:

  • e5d187e6-12aa-48df-abc1d7940ae0804c is the objectGuid of the following object:

  • CN=SHICO-TEMP-2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=shico-office,DC=nttest,DC=microsoft,DC=com

shico-temp-2 is the host name of the replica DC.

COMM_REPLICA (96 bytes):

  
 10 00 00 00 1a b2 f4 54 fd 03 74 43 8e 3b 28 75 e7 40
 d9 58 48 00 00 00 44 00 4f 00 4d 00 41 00 49 00 4e 00
 20 00 53 00 59 00 53 00 54 00 45 00 4d 00 20 00 56 00
 4f 00 4c 00 55 00 4d 00 45 00 20 00 28 00 53 00 59 00
 53 00 56 00 4f 00 4c 00 20 00 53 00 48 00 41 00 52 00
 45 00 29 00 00 0

GUID: 54f4b21a-03fd-4374-8e3b2875e740d958

Name: DOMAIN SYSTEM VOLUME (SYSVOL SHARE)

Notes:

  • 54f4b21a-03fd-4374-8e3b2875e740d958 is objectGuid of the following object:

    CN=SHICO-TEMP-1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=shico-office,DC=nttest,DC=microsoft,DC=com

  • DOMAIN SYSTEM VOLUME (SYSVOL SHARE) is the name of the following object:

    CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=shico-office,DC=nttest,DC=microsoft,DC=com

COMM_CXTION (118 bytes):

  
 10 00 00 00 5f 34 89 2d ac b2 89 4e 8b dd 0e fa 16 6b
 92 e6 5e 00 00 00 73 00 68 00 69 00 63 00 6f 00 2d 00
 74 00 65 00 6d 00 70 00 2d 00 31 00 2e 00 73 00 68 00
 69 00 63 00 6f 00 2d 00 6f 00 66 00 66 00 69 00 63 00
 65 00 2e 00 6e 00 74 00 74 00 65 00 73 00 74 00 2e 00
 6d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00
 2e 00 63 00 6f 00 6d 00 00 00

GUID: 2d89345f-b2ac-4e89-8bdd0efa166b92e6

Name: shico-temp-1.shico-office.nttest.microsoft.com

Notes: In this case:

  • 2d89345f-b2ac-4e89-8bdd0efa166b92e6 is the connection GUID of the SYSVOL volatile connection. During DCPromo, the replica DC dynamically creates a random GUID to be used as the volatile connection GUID, and then passes this connection GUID to PDC via the CxtionGuid parameter in FrsRpcStartPromotionParent.

  • shico-temp-1.shico-office.nttest.microsoft.com is the DNS host name of the PDC.

  • A volatile connection is used to seed SYSVOLs after dcpromo. If there is inactivity on an outbound volatile connection for more than 30 minutes, this connection is unjoined. An unjoin on an outbound volatile connection triggers a delete on that connection. This is to prevent the case where staging files are kept forever on the parent for a volatile connection.

COMM_JOIN_GUID (20 bytes):

  
 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00

GUID: 00000000-0000-0000-0000000000000000

Note Since the join has not been started, the connection session GUID is set to all zeros.

COMM_LAST_JOIN_TIME (8 bytes):

  
 01 00 00 00 00 00 00 00

COMM_EOP (4 bytes):

 ff ff ff ff