We will be discussing the Credential Object. In our VSA Basics series, we introduced you to the concept of Policies, and how objects can be configured to automate endpoint settings within the VSA. If you need a refresher on this, you can find it on our channel!
Step by Step:
In this video, we’ll be discussing the credentials object let’s get into it.
The credential object allows two things first if combined with another policy object it forces the policy to use a specific account to perform the actions of the policy.
Second, if used by itself allows you to configure machines to have a specific username-password created on the machine or to update the password of the account if it is already present. It also ensures the account is added or updated to future machines as they check into VSA, I recommend only using this for workgroup machines.
The first checkbox requires credentials to be configured under audit module manage credentials functions and, in most cases, you will not be using this option.
Enter a username and password that you wish to use ensuring it’s secure. For example, you can see I have MSP admin and then the password, select local user account, and, select create new account as administrator. This ensures that the account is created if not present and is sent to administrator.
Do note if this account does not require administrative credentials do not use the as administrator option and that concludes the credential object discussion.
As always remember to save and apply and ensure that the policy is placed into organizations and machine groups to apply the machines in the view.