3.1.5.3 WDS_OP_GET_CLIENT_UNATTEND

This opcode is used to query for unattended instructions for the deployment agent.

The server MUST validate that all required variables are specified in the request packet.

The server MUST follow the following steps to determine if there are unattended instructions for the deployment agent:

The server MUST search for a matching computer object in the Active Directory domain as specified in section 3.1.1.2.

If a computer object is found and the DeploymentAgentUnattend attribute (section 3.1.1.2) specifies a relative path to a file for the deployment agent, the server MUST read the contents of the file and set the CLIENT_UNATTEND variable to the contents.

If a computer object is not found or the DeploymentAgentUnattend attribute does not specify a relative path to a file, then the server MUST check the deployment agent unattend store for unattended instructions for the architecture specified by the client using the ARCHITECTURE variable. If unattended instructions are found, the server MUST set the CLIENT_UNATTEND variable to it.

If the FIRMWARE variable is present, the server MAY use the value of the FIRMWARE variable to select more specific unattended instructions from the deployment agent's unattend store for the architecture and firmware types, by using both the ARCHITECTURE and FIRMWARE variables together.<40> In this case, the server MUST set the CLIENT_UNATTEND variable to these unattended instructions.

If unattended instructions are found, the FLAGS variable MUST be set to include the WdsCliClientUnattendPresent flag.

If the OSImageUnattendOverride (section 3.1.1.1) is set to TRUE, then the FLAGS variable MUST also include the WdsCliClientUnattendOverride flag.