Quest vRanger
Installation/Upgrade Guide
4.2.1.f
33
Complete the Installation
The installation continues until the Completing the Setup Wizard Dialog displays.
1. Select Run vRanger Backup & Replication to launch the application immediately.
2. Click Finish.
Note: Refer to “Chapter 3 - Configuration” chapter of the vRanger User’s Guide for procedures on
completing the vRanger Startup Wizard or performing other configurations.
4.2.2
Install vRanger on an Existing SQL 2005/2008 Server
This procedure assumes that you have already downloaded the vRanger software and saved it to an
accessible location.
4.2.2.a
vRanger Setup
1. Double-click the vRanger--Setup.exe file.
2. The vRanger Backup and Replication Setup Wizard opens. Click Next.
3. The License agreement screen displays. Click I Agree.
4. The Choose Components screen displays.
5. Select the components you wish to install.
Note: Both vRanger and Catalog Manager are selected by default. You can choose to deselect
catalog manager, and install it separately at a later time, if you wish.
6. Click Next.
7. The Choose Install Location screen displays.
8. You can accept the default folder, or browse to another location of your choice. Press Next.
4.2.2.b
User Credentials
The User Credentials dialog displays. This configures the account that vRanger will use to run the
vRanger Service. The user account needed for this step must have administrator privileges on the
local machine.
If you plan on using Windows Authentication for your SQL database, the account configured here will
be used.
1. In the Domain field, enter the domain in which the user account is located.
2. In the Username field, enter the username for the account.
3. In the Password field, enter the password for the account.
4. Click Install.
4.2.2.c
Install Database
1. The vRanger Database Setup screen displays. Press Next.
2. The Install Database screen displays
3. Click Install/Upgrade on an existing SQLS Server 2005/2008.
4. Select a server authentication method.
SQL Server: Enter and confirm the system administrator (sa) password when you select
Mixed Mode authentication. Setting strong passwords is essential to the security of your
system. Never set a blank or weak sa password.
Windows: When a user connects through a Windows user account, SQL Server validates
the account name and password using information in the Windows OS. Windows
Authentication uses Kerberos security protocol, provides password policy enforcement