The Recovery Manager for Active Directory Management Shell uses the Windows PowerShell help cmdlets to assist you in finding the appropriate information to accomplish your task. The following table provides some examples of how to use the Get-Help and Get-Command cmdlets to access the help information that is available for each cmdlet in the Recovery Manager for Active Directory Management Shell.
Table 38: Getting help
|Get-Help||When you use Get-Help without any parameters, you are presented with basic instructions on how to use the help system in Windows PowerShell, including Help for the Recovery Manager for Active Directory Management Shell.|
When you use Get-Help with the name of a cmdlet as an argument, you are presented with the help information for that cmdlet. For example, to retrieve the help information for the Get-RMADCollection cmdlet, use the following command:
Get-Command without any parameters lists all the cmdlets that are available to the shell. You can use the Get-Command cmdlet with the Format-List or Format- Table cmdlet to provide a more readable display. For example, use Get-Command | Format-List to display the output in a list format. To display a list of all the Recovery Manager for Active Directory Management Shell cmdlets that are available to the shell, use the following syntax:
Get-Command -PSSnapin Quest.RecoveryManager.AD.PowerShell
When you use Get-Command with the name of a cmdlet as an argument, you are presented with information about the parameters and other components of that cmdlet. The <Cmdlet> entry allows for wildcard character expansion. For example, to retrieve information about the cmdlets with the names ending in Member, you can use the following command:
The Active Directory Virtual Lab is a component of Recovery Manager for Active Directory Disaster Recovery Edition that helps you create virtual test environments from an Active Directory forest. You can use the created test environments to design and evaluate Active Directory disaster recovery scenarios, test planned Active Directory changes before deploying them to production, train your staff to perform Active Directory-related tasks, and more.
When creating virtual machines from the source computers, the Active Directory Virtual Lab uses third-party virtualization software, such as Microsoft System Center Virtual Machine Manager (SCVMM), VMware ESX, or VMware vCenter. For a full list of supported virtualization software, see the System Requirements section in the Recovery Manager for Active Directory Disaster Recovery Edition Release Notes.
You can create virtual machines that maintain all the data available on the source computers, including Active Directory, installed programs, and files. To manage the created virtual test environment, you need to use the native tools provided by the virtualization software with which the Active Directory Virtual Lab created the virtual machines in the test environment.
To create a virtual test environment from an Active Directory forest, you first need to select the source computers (domain controllers or standalone servers) you want to include in the test environment, configure settings to create a virtual machine from each source computer, and then have the Active Directory Virtual Lab create the test environment for you.
For instructions on creating a virtual test environment, see How to create a virtual test environment.
This section lists the permissions required to create a virtual test environment by using the Active Directory Virtual Lab.
Table 39: Required permissions
|Install and use Active Directory Virtual Lab.||Be a member of the local Administrators group.|
Create a virtual machine from a source computer.
NOTE: This includes access to the source computer, Forest Recovery Agent installation, and virtualization agent installation.
|Create a virtual test environment using Microsoft SCVMM.||
Have the Delegated Administrator role on the Microsoft SCVMM server.
Be a member of the local Administrators group on the target Hyper-V host.
|Create a virtual test environment using VMware vCenter/ESX.||
VMware vCenter/ESX server:
To install Converter Standalone agent, use built-in Administrator account to connect to the source machine or disable User Access Control (UAC) on the source machine.