RG048 – Configuring RES Hyperdrive

By Rob Aarts


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
  • Android
  • 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)


Login with the password you created during installation.



Start by adding the storage for the appliance by clicking "Browse"









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.


Now configure your database. Note: Don't forget to configure your SQL Server to listen on port 1433 and use a SQL account with rights to create a new database.





Select your certificate choice; in my case I didn't use an public SSL








Setup you active directory connection. In the LDAP User settings, you need to add the account in NETBIOS "domain\user" format. Also don't forget to change the "Base CN" to reflect the domain name.







Enter your mail config. In this case I didn't setup a complete exchange config, but just used the SMTP address from my provider. Keep an eye on your mailbox after you hit the "Test" Button.






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.

As an alternative, you can create/Delete/Manager HyperDrive Accounts with Automation manager after you have downloaded and  imported the before mentioned building-blocks.


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! ;-).




  • By BrianE, July 18, 2012 @ 14:51

    Hello Rob,
    First of all thanks for the write-up it is very helpful. I am attempting to install this software in a similar configuration, and it seems my installation always hangs when it attempts to format the LUN partition. We are using the Microsoft iSCSI Target Initiator software with a 500GB LUN. Once it hangs for about an hour at formatting partition, it eventually errors out and if I attempt to search for iSCSI devices again i can watch on my RES VM it scrolls "refused I/O connect to dead device", but after a few tries or a reboot it always connects again. Any advice or ideas would be greatly appreciated.

  • By Javier Lecanda, July 19, 2012 @ 08:34

    One question… is it possible to setup HyperDrive without Active Directory authentication? Can I just create local users in the VA?
    We are having trouble getting clearance from security to connect to our production AD and that would help a lot for a POC/trial.
    Many thanks and good article!

  • By Filip Herman, August 21, 2012 @ 02:16

    Hi Javier,
    At the moment, you can only authenticate against Active Directory.  There is no other way.  You can't create local users.  If you wouldn't get clearance for your Active Directory, just setup a lab-environment with a demo domain controller in a new forest/domain.
    Res Partner

  • By Netmask, August 24, 2012 @ 02:37

    Nice article!
    However, I got one showstopper for me here.
    I can't get the license file because we are using web proxies. Do you know any workaround for that?

  • By Bjorn Nornes, September 28, 2012 @ 02:41

    Why am I unable to use the Windows Client, this always tries to log on using my AD user, when HyperDrive is not in our local domain. ?

    Is there a way to configure the Client  ?

Other Links to this Post

RSS feed for comments on this post. TrackBack URI

Leave a comment

You must be logged in to post a comment.