Variables in VPN Password Field
When trying to streamline one of our connections in RDM, I discovered that trying to use the $PASSWORD$ or even $USERNAME$ variables in the Password field of the VPN wasn't being amended to the correct password. However, if the $PASSWORD$ variable was used in the Username field, it was replaced as expected with the correct value.
I have tried looking through the documentation, but have been unable to determine if this is intentional or not:
Are variables able to be used in password fields at all, or are variables not allowed in password fields due to security reasons?
Create Private Vault Credential Entries from Powershell Script
Thanks, Erica!
I missed that one when going through all the commands... Your help is greatly appreciated!
Create Private Vault Credential Entries from Powershell Script
I am currently working on making a Win10Enterprise image for our laptops, and as part of that, setting up RDM. For all our existing users, they already have their Private Vault credentials setup and will not need to do this again.
However, for new users, I need a simple way to create all the required Private Vault credentials we use. Ideally, this would be in the form of some script in RDM that gets run for each new user as part of onboarding.
I can see that there is the New-RDMSession powershell command, but I am unsure if it is able to create entries in the Private Vault?
Alternatively, is there a way to make "User Templates" that can be used for creating new users that will already have these Private Vault credentials created?