The Add-CredentialsVaultAccount
cmdlet lets you manage and create accounts in the credentials vault.
The usage for the command is as follows:
Add-CredentialsVaultAccount [-AccountUsername <string>] [-AccountPassword <string>] [-Description <string>] [-User <string>] [-Core <string>] [-Password <string>] [<CommonParameters>]
The following table describes the options available for the Add-CredentialsVaultAccount
command:
Option | Description |
---|---|
-? |
Display this help message. |
-AccountUsername |
The user name for the Credentials Vault account. |
-AccountPassword |
The password for logging in to the Credentials Vault account. |
-Description |
The description of the Credentials Vault account. |
-user |
Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
If none are provided, then the logged-on user's credentials will be used. |
-core |
Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. |
-password |
Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on.
If none are provided, then the logged-on user's credentials will be used. |
Add a Credentials Vault account to the local Core:
>Add-CredentialsVaultAccount -AccountUsername "user1" -AccountPassword "password1"
The addencryptionkeytoprotectedmachine
command lets you apply an existing encryption key to a machine that the Core is protecting.
The usage for the command is as follows:
/addencryptionkeytoprotectedmachine -core [host name] -user [user name] -password [password name] -name [encryption key name] -comment [comment or description of key]
The following table describes the options available for the addencryptionkeytoprotectedmachine
command:
Option | Description | ||
---|---|---|---|
-? |
Display this help message. | ||
-core |
Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine. | ||
-user |
Ocmdptional. The user name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used. | ||
-password |
Optional. The password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none is provided, then the credentials for the logged-on user are used. | ||
-protectedserver | The name or IP address of the protected machine. | ||
-keyname |
Optional. The name of the encryption key. Specify this option if you know the name of the encryption key that you want to set for the protected machine.
|
Apply an existing encryption key to a protected machine. If you want to disassociate the key from the protected machine, then select <none> or specify the <none> value for the -keyname option:
>cmdutil /addencryptionkeytoprotectedmachine -protectedserver 10.10.8.150 -keyname EKname
The Add-EsxAutoProtectObjects
cmdlet enables auto protection for specified objects on a vCenter or ESXi server.
The usage for the command is as follows:
Add-EsxAutoProtectObjects -core [host name] -user [user name] -password [password] -repository [name] -protectedserver [name | IP address] -autoprotect [object name collection]
The following table describes the options available for the Add-EsxAutoProtectObjects
command:
Option | Description |
---|---|
-? |
Display this help message. |
-core |
Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. |
-user |
Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
If none are provided, then the logged-on user's credentials will be used. |
-password |
Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on.
If none are provided, then the logged-on user's credentials will be used. |
-repository |
Required. The name of the repository that is associated with the Core that you want to use to protect the virtual machine.
Note: You must enclose the name in double quotes. |
-protectedserver |
Show jobs for a specific protected machine, indicated by IP address. |
-autoprotect |
Optional. This option lets you list the new virtual machines that you want to automatically protect. |
Put specific objects from a vCenter or ESXi server under auto-protection by the Core:
>Add-EsxAutoProtectObjects -protectedserver 10.10.8.150 -add -autoprotect "Folder1", "Folder2"
The Add-EsxVirtualMachines
cmdlet lets you add specific virtual machines (VMs) on vCenter or ESXi server under the protection of a Core.
The usage for the command is as follows:
Add-EsxVirtualMachines -core [host name] -user [user name] -password [password] -repository [name] -protectedserver [name | IP address] -virtualmachines [virtual machines collection | all]
The following table describes the options available for the Add-EsxVirtualMachines
command:
Option | Description |
---|---|
-? |
Display this help message. |
-core |
Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. |
-user |
Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
If none are provided, then the logged-on user's credentials will be used. |
-password |
Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on.
If none are provided, then the logged-on user's credentials will be used. |
-repository |
Required. The name of the repository that is associated with the Core that you want to use to store the data of the virtual machine.
|
-protectedserver |
Use this option to edit the vCenter or ESXi objects for a specific protected machine. |
-virtualmachines |
A list of virtual machines each separate by a comma. |
Add two VMs from a vCenter or ESXi server under protection by the Core:
>Add-EsxVirtualMachines -repository "repository1" -protectedserver 10.10.10.10 -virtualmachines "vm1", "vm2"
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center