Jun
21

RES HyperDrive configuration guidelines

Since the release of RES HyperDrive, we’ve been contacted by lots of enthusiastic people who are using RES HyperDrive. The most questions we received were about the configuration. In this article I will describe some guidelines for configuring the RES HyperDrive appliance.

Configuration of the RES HyperDrive appliance

After starting the RES HyperDrive appliance and changing the password of the ‘root’ account, you have to setup the network configuration.

Ethernet Configuration:
Don’t change the name of the device name! Leave this as pre-configured.

DNS Configuration:
Use the FQDN of the appliance in the Hostname field.

Configure the domain name in the Search field.

If you need to edit this configuration afterwards, use the command:
system-config-network on the command line interface of the appliance.

DNS Record:
Create a DNS record in the Forward and Reverse Lookup Zones for the RES HyperDrive virtual appliance before continuing with the VA setup. Create a Reverse Lookup Zone if none is configured in your DNS environment for the subnet in which the appliance resides.

The rest of the configuration can be done by starting the webpage: https://<hostname>/va

Storage Configuration:
Connect to the local or the iSCSI storage of your environment.

Database Configuration:
Make sure you are using the FQDN of the DB server in the Hostname field.

Use an SQL account which has enough rights to create the database and SQL login (e.g. ‘sa’ account).

Use port 1433 as the standard port for SQL connection.


Webserver Configuration:

Make sure you are using the FQDN of the appliance in the FQDN field.

Active Directory Configuration:
Always use a domain controller which holds the Global Catalog, in the ‘AD Host’ and ‘LDAP Host’ fields.

Make sure you use the FQDN of these server(s).

The Base CN should point to the location in the Active Directory where the user accounts will reside.

Use the [Domain\username] in the ‘User’ field, otherwise the
‘The LDAP bind failed, are your credentials correct? ‘ error message could occur after clicking the Test button.

SMTP Configuration:
Use the FQDN of your e-mail server in the ‘SMTP Server’ field.

Use the full e-mail address in the ‘email’ fields.

RES Automation Manager:
When you don’t use RES Automation Manager in your environment, the ‘Dispatcher host’ field does not need to be configured.

Note:
The option ‘Allow users to create their own RES HyperDrive account’ is disabled by default. If disabled, user accounts can only be created by using RES Automation Manager.

License:
Make sure that the RES HyperDrive appliance is able to connect to the Internet by using HTTPS. A proxy server cannot be used (yet), direct access to the Internet is required.

Don’t forget to click ‘get license info’. Otherwise it’s not possible to commit the configuration.

Commit your configuration and the RES HyperDrive appliance will be configured. In the browser window, the progress will be shown.

The above screen will be shown when the configuration was successful. Before closing the browser window, download the PuTTY key or OpenSSH key for the ‘hyperdrive‘ account to access the RES HyperDrive appliance remotely.

These keys will be deleted after a reboot of the appliance and can be downloaded afterwards by using the following URL’s:

PuTTY:          https://<hostname>/va/keys/putty
OpenSSL:      https://<hostname>/va/keys/rsa

If there is any error reported during the configuration of the appliance, this will be shown in the browser. Make sure to save the log file by clicking on the ‘setup log’ link. This log is needed for further troubleshooting.

Common error messages

Error message:

  • ‘Could not connect to Active Directory’
  • ‘Error 3802: Unknown error occurred. Please try again or contact support.’

Solution:

  • Register the FQDN of the RES HyperDrive appliance on the DNS server in the forward and reverse DNS zones.
  • Make sure the certificates are imported for the users.
  • Place the self-signed certificate in the Trusted Root Certification Authorities key on the client machines which connects to the RES HyperDrive appliance.
  • Enable the self-signed certificate as trusting in Safari is not enough, the RES HyperDrive Client for MAC is not aware that the self-signed certificate is trusted.
  • Check the KB articles:
    ‘Could not connect to Active Directory’
    ‘Error 3802′


Error message:

  • ‘This link is not valid. Contact RES HyperDrive support if you keep having this problem.’

Solution:

  • Re-configure the Active Directory – LDAP configuration in the RES HyperDrive Virtual Appliance. Check the configured Base CN.
  • Check the KB article:
    ‘This link is not valid’



Error message:


Solution:

  • Create an account for the user.
  • OR

  • Enable the option ‘Allow users to create their own RES HyperDrive account’ in the ‘RES Automation Manager’ part of the configuration.

More information is available in the RES HyperDrive Administration Guide. This document can be accessed by using the following link: RES HyperDrive Administration Guide

COMMENTS: 7
FB Share
Martijn Nov 01, 2013

Als je hem in dutch installeert neemt ie ook nederlandse toetsenbord instelling over,dus test je wachtwoord in de appliance dan kun je zien welke tekens veranderen.....had ik ook :-)

Christian Nov 13, 2012

Thanks very much for the Post. @Franz, Your Account at Active Directory Configuration, Administrator: have to the right to create computer accounts.

Cedric 2 hours ago

When I try to connect to the starting webpage, using the root passwd previously configured, i have the following error : Please authorize with a valid password. I've changed the root password, but doesn't work.

Rene Sep 28, 2012

Could not obtain a Kerberos ticket with these credentials.

MLM Software Jul 09, 2012

Nice Post and Thanks for Sharing.

Franz Jul 03, 2012

During the installation a error occur- "Could not logon with the keytab file" When i try to login by https://myhyperdrive/my a kerberos auth massage pop up, but i can not login not even domain admin. The time on the hyperdrive machine is in sync with the dc. (reverse)DNS is proper config. Has someone any Ideas to fix this issue?

Haakon Flender 1 day 18 hours ago

some issues I ran into: If you have issues with connecting to the sql server, you might need to set the default port for IPAll to 1433. Just do the following: - sql server config manager >sql server network configuration > protocols for > tcp/ip If you have trouble connecting to smtp server, check that your smtp (in my case Exchange) has enabled "anonymous users" for the receive connector in exchange mgt. console.

Leave a Comment

Leave a Reply

CATEGORIES:
ARCHIVES: