This video describes a step-by-step process to remotely deploy DR2000v within a Hyper-V 2012 R2 environment. For any DR200v deployment the first step is to install the DR200v license within an associated physical DR appliance. With the DR2000v license that was emailed to you, follow the steps for proper licensing.
First, log on to the physical DR appliance that your DR200v will register with. Next, select the License option under the appliance Support management branch. Under the License File Location select Choose File. Now, browse to the DR2000v license file that was emailed to you. Select Install License. You have now completed the one-time licensing step for your DR2000v.
A few prerequisites need to be met when deploying DR2000v's to remote Hyper-V hosts. Both local and remote servers or hosts need to be of similar operating systems. For example, one cannot deploy a DR2000v to a remote Windows 2012 host from a Windows 2008 R2 server.
The following software requirements need to be met on both local and remote servers and hosts-- .NET Framework 4.5, Windows PowerShell 4.0, and Windows Remote Management 2.0. Note, this video demonstrates a DR2000v deployment using Windows 2012 R2 hosts.
As these prerequisites are already included in the operating system image, manual installation here is not necessary. In any case, make sure you have these three packages installed on both local and remote Windows servers and hosts. Also, you will need to perform DR2000v deployment activities using administrator privileges.
Extract the downloaded DR2000v application installation package on the local Hyper-V host to gain access to its files. You can easily access the software to meet these requirements within the downloaded DR2000v appliance Prerequisites folder. For your convenience, both online and offline versions of the .NET Framework 4.5 can be found along with the Windows Management Framework 4.0 update package.
Note, these prerequisite file names may change over time as different DR2000v operating system versions are released. Also other updates may be required.
Next, the prerequisites also call for the following windows commands to be run on both local and remote hosts. The first command enables Windows 2012 server to administer Hyper-V. The second command installs additional PowerShell commands specialized for Hyper-V. After running the third command, only scripts signed by a trusted publisher can run on the Windows 2012 server.
You can run commands on one or hundreds of computers with a single Windows PowerShell command. The syntax to do so is shown here. To issue the three command prerequisites to both local and remote computers in my environment I will issue the following commands. I will now apply these prerequisites to my local and remote hosts.
Now install a digital certificate from DR2000.dll found in the bin directory of the DR2000v install package into the Trusted Root Certification Authorities and Enterprise Trust certificate stores. The DR2000v capacity requirements are 200 gigabytes above and beyond the capacity of the DR2000v. For example, if a 2 terabyte DR2000v is to be deployed, 2.2 terabytes of storage capacity will be required.
If alternate storage locations are desired for the 2000v virtual appliance due to capacity limitations or for some other reasons, the remote Hyper-V host's virtual hard disk and virtual machine pass need to be changed before the DR2000v deployment. The environment within this video has terabytes of EqualLogic iSCSI free capacity that we'll use for a 2 terabyte DR2000v deployment.
Thus, I will now prepare the Hyper-V VM storage pass. Go to the remote host. Open up file manager and locate the volume that has adequate free capacity for the DR2000v deployment. Create a folder in this location. With the storage needs identified and prepared, let's change the Hyper-V VM storage locations.
From the local machine, open up Hyper-V Manager. Now connect to the host where the DR2000v will be deployed. Select this host and choose Hyper-v Settings. Now change both virtual hard disk and virtual machine's pass settings. We're now ready to deploy the DR2000v virtual machine.
It is important to remember that for remote deployments one must access the DR2000v deployment files using UNC path names, not mapped drive shares. By default, the C drive is one of many Windows default administrative hidden shares, so place the DR2000v deployment files here on the local machine.
In this example, I'm at my local machine. And we'll access the DR2000v deployment package using a UNC path name. From here, run the DR2000v command script found at the root of the install package. Once run, a command line Deployment Wizard is presented. Select b for a remote deployment. Add the remote computer host name or fully qualified domain name.
Now provide the proper username to access the remote host. Now provide the password. Enter option 1 to deploy. Enter an appropriate Hyper-V VM name for the DR2000v virtual appliance. Since we're installing a two terabyte DR2000v, enter option b for the proper storage size.
The DR2000v Hyper-V virtual machine code is now being deployed. This process takes two to three minutes. We'll skip ahead to the tail end of this process. Since only one DR2000v will be deployed, enter N for no.
Before any remotely deployed DR2000v virtual appliance can be started, its virtual network adapters need to be manually connected to a virtual switch. Open up the local machine Hyper-V Manager. Right-mouse select the Hyper-V Manager icon and choose Connect to Server. Enter the name of the remote Hyper-V host that the DR2000v was remotely deployed to.
Right-mouse select the DR2000v virtual appliance and choose Settings. Highlight the NIC0 hardware object and choose the virtual switch to connect to. Repeat this step for NIC1. Apply the new settings. Once connected, right-mouse select the DR2000v virtual appliance and select Start to self extract the installation packages and install all the DR2000v components.
Now right-mouse select the DR2000v VM again and Connect to view the installation process. Depending on your system resources, the next 10 to 20 minutes are needed to self extract installation packages and components. We'll