3.2.5.7 Deployed OS Unattend and Domain Join

  • Article

If LogLevel (section 3.2.1.1) allows logging, the client MUST log a WDS_LOG_TYPE_CLIENT_POST_ACTIONS_START status message.

The client MUST get domain join information from the server using WDS_OP_GET_DOMAIN_JOIN_INFORMATION (section 2.2.5).

If the FLAGS variable in the reply packet includes the WdsCliJoinDomain flag, and if WdsCliFlagsAccountExists is also specified, the client MUST follow the steps in section 3.1.5.5.1 ; otherwise the client MUST follow steps in section 3.1.5.5.2.

If the client fails to configure the deployed OS to join an Active Directory domain, and if allowed by LogLevel), the client MUST log a WDS_LOG_TYPE_CLIENT_DOMAINJOINERROR2 status message. If the attempt to log the status message fails, the client MUST log a WDS_LOG_TYPE_CLIENT_DOMAINJOINERROR status message.

The client MUST query the server for unattended instructions for the deployed OS. The WDS OS Deployment Protocol does not provide a mechanism for obtaining the unattended instructions for the deployed OS. A contract MUST exist between client and server on how this information is communicated.

If unattended instructions for the deployed OS exists, the client MUST query for unattend variables for unattended instructions for the deployed OS, using WDS_OP_GET_UNATTEND_VARIABLES (section 2.2.4), and MUST perform variable replacement for unattended instructions for the deployed OS. The client MUST also configure the deployed OS to use the unattended instructions.

If LogLevel allows logging, the client MUST log a WDS_LOG_TYPE_CLIENT_POST_ACTIONS_ENDstatus message.