Installation guide
Table Of Contents
- COPYRIGHT
- TABLE OF CONTENTS
- INTRODUCTION
- Support OS - VM ESX
- PRE-REQUISITES
- ADDITIONAL INFORMATION
- WHAT’S NEW IN VOYENCECONTROL 4.1.0
- FIXED ISSUES
- (20112) – Cut-Through not offering a "more" Option when Viewing Configuration
- (21536) – User passwords – Visible in commmrg.log when using Cut-through
- (21555) – Device Data Fields- Cleared Despite no User Input
- (21618) – Network Navigation Tree – Problem with Display
- (21661) – Network Navigation Tree – Right-Click Options not Working Properly
- (21690) – Network Navigation Window – Right-Click Options – Working Intermittently
- (21759) – Pulled Cisco IOS Devices – Self-Check rule Failed
- (21834) – Database Size - More Space than Required
- (21878) – Failed Policies – Not Displaying in the Comments Section
- (21994) – Customize Column Sizing not being Maintained
- (22062) – Clicking "Schedule" after running Compliance Audit – Devices Missing
- (22147) – Repeated Error Message - Server and jboss logs
- (22157) – Audit Trail – Incorrect Hierarchy
- (22319) – Graphical User Interface - Slow Response/Jboss stuck at 100% CPU
- (22407) – Cannot Schedule OS Update for Multiple Devices
- (22521) – Large Auto Discovery Jobs do not Complete
- (22534) – Random "Resource Not Found" Error at Login
- (23074) – Compliance Error When Attempting to Execute Compliance Audit on Nokia Appliance
- KNOWN ISSUES
- (22192) – Data Field Names – New Data Field Names are not Replacing the Old Data Field names after Migration
- (22386) – Disabling SNMP causes Failing Request
- (22556) – Schedule Configuration Change - conflict with Velocity Template Commands
- (22579) – Upgrading from VoyenceControl 4.0.1 to 4.1.0 causes Exception on UI Load
- (22595) – Intermittent deadlock - Importing/Exporting Automation Library items.
- (22607) – Compliance Steps – Existing RegEx Compliance Test
- (22883) – SAML Enable Script - Source /etc/voyence.conf before Installation
- (22906) – Connection to SSH Proxy Fails
- (22943) – "Error: Version Already Installed" Message after a Failed install or Upgrade
- (23027) – Upgrading a Device Server from VoyenceControl 3.6.2 to 4.1.0 does not Retain Multi-Level Mode
- (23089) – Upgrading to VoyenceControl 4.1.0 - Report Advisor URL Points to "http:///web"
- (23118) – System Management Console - Password gets reset to 'sysadmin' after Upgrading (Windows Only)
- (23150) – Config Pulls After Auto Discovery - Not Getting Scheduled when Using a Remote Device Server
- (23542) – Installing from a Read Only File System – Components Needed
- (23548) – Can Not Install Integration Modules under the VoyenceControl 4.1 API in VoyenceControl version 4.1.0
- INSTALLING VOYENCECONTROL 4.1.0
- UPGRADING TO VOYENCECONTROL 4.1.0
- WHERE TO GET HELP
EMC VoyenceControl – Release Notes
INSTALLING VOYENCECONTROL 4.1.0
When installing VoyenceControl 4.1.0, review the following documents for detailed
instructions.
Installing VoyenceControl on Red Hat Enterprise Linux 4 and 5
Installing VoyenceControl on Windows Server 2003
Installing VoyenceControl on Solaris 10
UPGRADING TO VOYENCECONTROL 4.1.0
Upgrade Instructions for VoyenceControl 4.1.0 – Application Servers,
Combination Servers, and Device Servers
Note: Be sure to read the contents of the ReadMeFirst.pdf document before continuing
with the installation procedures.
When upgrading from VoyenceControl 3.6.2 (or higher), or 4.0.1 (or higher), review the
following documents for detailed instructions.
Migration on Red Hat Enterprise Linux 4 and 5
Migration on Windows Server 2003
Migration on Solaris 10
Note: You must have VoyenceControl 3.6.2 (or higher), or 4.0.1 (or higher) installed before
upgrading to VoyenceControl 4.1.0.
Obtaining a New License Key – VoyenceControl 3.6.2 customers only
For VoyenceControl 3.6.2 customers who are upgrading to VoyenceControl 4.1.0, you must
obtain a new EMC license key. This key can be obtained by emailing your request for a new
license key to
licensekeys@emc.com. VoyenceControl 4.0.1 customers who are upgrading to
VoyenceControl 4.1.0 do not need a new license key; your current key will work with
VoyenceControl 4.1.0.
Additional Migration Information
The data migration is not completed during the software upgrade. To properly maintain data
integrity, data migration
must be completed prior to upgrading the software.
Release Notes Version 4.1.0
Page 19