This page is generated from the Chef Infra Client source code. To suggest a change, edit the windows_user_privilege.rb file and submit a pull request to the Chef Infra Client repository.
The windows_user_privilege resource allows to add and set principal (User/Group) to the specified privilege. Ref: https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/user-rights-assignment
New in Chef Infra Client 16.0.
The full syntax for all of the properties that are available to the windows_user_privilege resource is:
windows_user_privilege 'name' do
principal String # default value: 'name' unless specified
privilege Array, String
users Array, String
action Symbol # defaults to :add if not specified
endwhere:
windows_user_privilege is the resource.name is the name given to the resource block.action identifies which steps Chef Infra Client will take to bring the node into the desired state.principal, privilege, and users are the properties available to this resource.The windows_user_privilege resource has the following actions:
:add:clear:nothing:remove:setprivilege property for only the users listed in the users property.The windows_user_privilege resource has the following properties:
principal The resource block's name An optional property to add the user to the given privilege. Use only with add and remove action.
privilege REQUIRED One or more privileges to set for users.
users An optional property to set the privilege for given users. Use only with set action.
Chef resources include common properties, notifications, and resource guards.
The following properties are common to every resource:
compile_timeRuby Type: true, false | Default Value: false
Control the phase during which the resource is run on the node. Set to true to run while the resource collection is being built (the compile phase). Set to false to run while Chef Infra Client is configuring the node (the converge phase).
ignore_failureRuby Type: true, false, :quiet | Default Value: false
Continue running a recipe if a resource fails for any reason. :quiet will not display the full stack trace and the recipe will continue to run if a resource fails.
retriesRuby Type: Integer | Default Value: 0
The number of attempts to catch exceptions and retry the resource.
retry_delayRuby Type: Integer | Default Value: 2
The delay in seconds between retry attempts.
sensitiveRuby Type: true, false | Default Value: false
Ensure that sensitive resource data is not logged by Chef Infra Client.
notifies Ruby Type: Symbol, 'Chef::Resource[String]'
A resource may notify another resource to take action when its state changes. Specify a 'resource[name]', the :action that resource should take, and then the :timer for that action. A resource may notify more than one resource; use a notifies statement for each resource to be notified.
If the referenced resource does not exist, an error is raised. In contrast, subscribes will not fail if the source resource is not found.
A timer specifies the point during a Chef Infra Client run at which a notification is run. The following timers are available:
:beforeSpecifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayedDefault. Specifies that a notification should be queued up, and then executed at the end of a Chef Infra Client run.
:immediate, :immediately
Specifies that a notification should be run immediately, per resource notified.
The syntax for notifies is:
notifies :action, 'resource[name]', :timer
subscribes Ruby Type: Symbol, 'Chef::Resource[String]'
A resource may listen to another resource, and then take action if the state of the resource being listened to changes. Specify a 'resource[name]', the :action to be taken, and then the :timer for that action.
Note that subscribes does not apply the specified action to the resource that it listens to - for example:
file '/etc/nginx/ssl/example.crt' do
mode '0600'
owner 'root'
end
service 'nginx' do
subscribes :reload, 'file[/etc/nginx/ssl/example.crt]', :immediately
end
In this case the subscribes property reloads the nginx service whenever its certificate file, located under /etc/nginx/ssl/example.crt, is updated. subscribes does not make any changes to the certificate file itself, it merely listens for a change to the file, and executes the :reload action for its resource (in this example nginx) when a change is detected.
If the other resource does not exist, the subscription will not raise an error. Contrast this with the stricter semantics of notifies, which will raise an error if the other resource does not exist.
A timer specifies the point during a Chef Infra Client run at which a notification is run. The following timers are available:
:beforeSpecifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayedDefault. Specifies that a notification should be queued up, and then executed at the end of a Chef Infra Client run.
:immediate, :immediately
Specifies that a notification should be run immediately, per resource notified.
The syntax for subscribes is:
subscribes :action, 'resource[name]', :timer
A guard property can be used to evaluate the state of a node during the execution phase of a Chef Infra Client run. Based on the results of this evaluation, a guard property is then used to tell Chef Infra Client if it should continue executing a resource. A guard property accepts either a string value or a Ruby block value:
0, the guard is applied. If the command returns any other value, then the guard property is not applied. String guards in a powershell_script run Windows PowerShell commands and may return true in addition to 0.true or false. If the block returns true, the guard property is applied. If the block returns false, the guard property is not applied.A guard property is useful for ensuring that a resource is idempotent by allowing that resource to test for the desired state as it is being executed, and then if the desired state is present, for Chef Infra Client to do nothing.
PropertiesThe following properties can be used to define a guard that is evaluated during the execution phase of a Chef Infra Client run:
not_ifPrevent a resource from executing when the condition returns true.
only_ifAllow a resource to execute only if the condition returns true.
The following examples demonstrate various approaches for using the windows_user_privilege resource in recipes:
Set the SeNetworkLogonRight Privilege for the Builtin Administrators Group and Authenticated Users:
windows_user_privilege 'Network Logon Rights' do
privilege 'SeNetworkLogonRight'
users ['BUILTIN\Administrators', 'NT AUTHORITY\Authenticated Users']
action :set
end
Add the SeDenyRemoteInteractiveLogonRight Privilege to the Builtin Guests and Local Accounts User Groups:
windows_user_privilege 'Remote interactive logon' do
privilege 'SeDenyRemoteInteractiveLogonRight'
users ['Builtin\Guests', 'NT AUTHORITY\Local Account']
action :add
end
Provide only the Builtin Guests and Administrator Groups with the SeCreatePageFile Privilege:
windows_user_privilege 'Create Pagefile' do
privilege 'SeCreatePagefilePrivilege'
users ['BUILTIN\Guests', 'BUILTIN\Administrators']
action :set
end
Remove the SeCreatePageFile Privilege from the Builtin Guests Group:
windows_user_privilege 'Create Pagefile' do
privilege 'SeCreatePagefilePrivilege'
users ['BUILTIN\Guests']
action :remove
end
Clear all users from the SeDenyNetworkLogonRight Privilege:
windows_user_privilege 'Allow any user the Network Logon right' do
privilege 'SeDenyNetworkLogonRight'
action :clear
end
© Chef Software, Inc.
Licensed under the Creative Commons Attribution 3.0 Unported License.
The Chef™ Mark and Chef Logo are either registered trademarks/service marks or trademarks/servicemarks of Chef, in the United States and other countries and are used with Chef Inc's permission.
We are not affiliated with, endorsed or sponsored by Chef Inc.
https://docs.chef.io/resources/windows_user_privilege/