Requirements#
Used to specify prerequisites for a Playbook, requirements allow developers to ensure that the necessary conditions are met before their Playbook is run.
Requirements are specified in your playbook.conf
, as an array of requirements.
<Requirements>
<Requirement>Internet</Requirement>
<Requirement>NoPendingUpdates</Requirement>
<Requirement>DefenderToggled</Requirement>
<Requirement>NoAntivirus</Requirement>
</Requirements>
Requirement Values#
Requirement |
Description |
---|---|
|
Requires the user to have an active internet connection. |
|
Requires the user to not be connected to the internet. |
|
Requires the user to have an activated copy of Windows. |
|
Requires the Windows installation to be no more than 40 hours old. Note that this is easily bypassable in the UI. To specify an installation guide for the user, use the InstallGuide option. |
|
Requires the user to toggle the primary four Windows Security toggles. |
|
Requires the user to neutralize defender via the Prepare System step. |
|
Requires the user to disable the UCPD driver via the Prepare System step. |
|
Checks for Antivirus software registered in class |
|
Checks for any pending or downloading Windows updates, and prevents the user from moving forward until they have been installed. |
|
Requires the user to set their active user account password, and will subsequently convert any Microsoft accounts to local accounts. |
|
Requires the user to set the Administrator account password. |
|
Requires the userβs device to be plugged in, if it is a battery powered device. |