After the release of RES HyperDrive, here is an article that will walk you through the configuration. Underway, I will also share my installation experience as well. This is found in a separate article RG047 here.
First let me tell you what to expect from RES HyperDrive. The following paragraph is the official gospel (ripped from the sales slides ;-) "RES HyperDrive is a secure way to deliver follow me data and file-sharing with the enterprise-class security of on-premises technology. Available on any device, anywhere, RES HyperDrive empowers IT organizations to better serve an increasingly mobile, next generation workforce that demands convenient access to data from personal devices, applications, and cloud-based services. At the same time, it meets the stringent standards of IT professionals and executives by providing an on-premises technology that keeps data access secure, with true cross-platform portability”
Okay, so that was the official part, so let's dig into it. The HyperDrive appliance runs on a Linux (Centos) operating system. Whats that? – You don’t know Linux and managing it doesn't sound like your idea of fun? Don’t worry – managing your HyperDrive appliance is done through either a web browser or the RES Automation manager. You can download some nifty buildingblocks from the RES Portal
The RES HyperDrive Virtual Appliance supports the following client platforms:
- Microsoft Windows
- Apple MacOS
- Apple iOS 3.2 and later (iPhone, iPad, iPod Touch)
- Windows Phone
- RIM Blackberry
- Any web browser
First you need to get the backend up and running. Download the correct version of the virtual appliance for your environment. At the time of writing you can chose between (in no particular order):
- VMware ESX or Workstation
- Microsoft Hyper-V
- Citrix Xenserver
Get the appliance running by following the mentioned article RG047
After the installation you can start configuring the hyperdrive, go to https://<ip-adress>/va (that’s va for virtual appliance)
I used iSCSI so I will talk you through this setup. Enter the "IP address" of you iSCSI device and select search. this will show
your available LUNs (logical unit numbers). This make take a little while). Next, use the "Select" button to choose the right LUN.
Select your certificate choice; in my case I didn't use an public SSL
Next enter the name off you RES Automation Manager Dispatcher. Second, you have the option to "Allow users te create their own RES HyperDrive Account" checkbox.
Editors's note: The Automation Manager uses the Linux Agent for AM to manage the HyperDrive appliance. In order to work with the tasks associated with Linux machines, you have to set the following registry key on the computer running the Automation Manager console:
x86: HKEY_LOCAL_MACHINE\Software\RES\Automation Manager\WMC: REG_DWORD ShowLinuxTasks = 1
x64: HKEY_LOCAL_MACHINE\Software\Wow6432Node\RES\Automation Manager\WMC: REG_DWORD ShowLinuxTasks = 1
I'm told these tasks should be permantly visible in Automation Manager 2012 SR2, hence no more need for these reghacks.
At the end of the wizard, follow the instructions for getting your appliance licensed and choose commit.
Now all you need to do is open port 80 and 443 to access your on-premises HyperDrive fileservers from the internet. Note: When using IOS (iPad or iPhone) open port 8080 instead of 80.
I have been using the HyperDrive appliance on a Server2012 and the Windows PC client on Windows 8 for a while now. In a future article, I will cover the installation of the HyperDrive clients and their general usage.
Your feedback makes my articles better! ;-).