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
Several enhancements have been provided that give Step Compliance much more flexibility
and power. They include:
The ability for a step to use the configuration text as input, or to take input from the
stanzas generated in a previous step
The ability to iterate over the input stanzas, sub-dividing them into sub-stanzas
The ability to define a named variable that holds the values that matched a regular
expression grouping for each sub-stanza
Policy Editor
A new Policy Editor design offers a listing of Policy Tasks, where you can complete
the following:
Adding a Standard to the Policy
Adding a Test (Attributed Test or RegEx Test) to the Policy
Designating Enforcement areas for the Policy
Enabling a Policy
Setting up Scheduling options
Adding an Attributed Query to an Attributed Test
Removing items from the Policy
Running an Attributed Test or Query
Enforcing the Policy
Once you have completed the tasks, a check mark appears to indicate the policy task
is now successfully completed.
You can also edit a Standard and Test within the Policy, using the Policy Navigation
tree. You can also edit a Standard and Test within the Policy, using the Policy Navigation
tree.
Samples in the Library Manager
An extensive category of Samples for Compliance Tests, Queries, Saved Commands, and
Templates are shipped in the Samples folder.
Once copied, you can then edit the samples to produce customized Compliance Tests,
Attributed Queries, Saved Commands, and Templates. You can also select to Export or Move
these samples anywhere within your network.
Release Notes Version 4.1.0
Page 9