Date: July 5th, 2017
Intigua 3.6 includes the following features
New SMBv2 protocol
Following the recent vulnerabilities discovered in the CIFS/SMBv1 protocol, Intigua now supports SMBv2 instead. The default mode (if no configuration is specified) is currently CIFS, but will change to SMB2 in the next Intigua version.
CIFS mode is now considered deprecated, and will be removed in a future version.
In order to switch existing deployments of Intigua to SMBv2, go to intigua.config.xml file and replace <priority>CIFS</priority> with <priority>SMB2</priority> (Server restart required)
Support for WinRM protocol
The WinRM protocol has been added for Intigua Connector deployments. The support for WinRM will allow for the initial deployment only and communication with the Intigua Connector will then resume VIA the Web/vSphere/SMB/SSH protocols normally according to the priority configuration.
To enable WinRM, enter this line <priority>WINRM_SMB</priority> above <priority>SMB2</priority> (Server restart required)
vSphere protocol optimizations
Intigua can communicate with vCenter Virtual Machines VIA the hypervisor channel, a protocol that has been optimized and improved in Inituga 3.6.The ability to fine tune the vSphere communication protocol has been added allowing to now set the maximum vCenter calls per minute for any vCenter discovery source.
New server statistics
Basic monitoring of servers is now available in Intigua. The following columns have been added to servers tab:
- CPU cores - Number of CPU cores on a server (equivalent to CPU count column in vCenter)
- % CPU - Percentage of CPU consumption on the server
- Memory - allocated memory size
- Memory in use - Amount of memory consumption
- Disk space - Storage size
- Disk space in use - Amount of used disk space
To control the monitoring sampling intervals, go to the relevant Intigua service and modify the attribute 'Get servers statistics every' in Container tab. Make sure to reconfigure the desired servers with the modified service in order to apply your change.
Search management services on deployment
When applying a management service on a server, it is now possible to search for the required service in addition to selecting it from a dropdown list.
(Beta) New Services Page
The old library tab is being gradually being shifted to the new console. Now every tool has the management services listed in the new Compliance Dashboard UI. The ability to create and remove management services can now be done using the new UI.
(Beta) API for Creating services
Control the amount of time without communication before a managed server gets labeled as "disconnected". This is another tool for optimizing and fine-tuning the communication between Intigua and managed servers. Go to advanced settings and set 'Show server as disconnected after' as required. It is recommended to modify this only when your environment contains servers that do not communicate with Intigua via HTTPS, and there are rate limits on hypervisor-based communication with managed servers. For example, set a high value when your VMs communicate via vSphere and the number of vCenter calls is limited.
- CPU consumption has been reduced and optimized during throttling events.
- Redundant communication between Intigua and managed server has been eliminated.
- To prevent flooding Intigua with obsolete exceptions, Intigua purges old exceptions and stores in a separate DB. The time it takes for Intigua to remove a closed exception is configurable.
- When migrating an endpoint server with a management service between Intigua servers, if the agent image of that service is missing in the Intigua server, user would succeed to install the same tool again. In 3.6 Intigua would prevent this by replacing the service with a new service for which the image file exists.
- Fixed an issue where in some rare cases in which a user could install two different management services of the same agent on a server.
- The connector version will now be appended to all built-in Intigua services, to prevent cases in which policy rules did not work for Intigua services.
- Fixed bug in which the command line did not properly worked for some commands on ubuntu 16.04.
- Fixed bug in that prevented expanding the library when an Intigua service is installed on a nameless server.
- In order to reconfigure a tool on a server from the 'Apply/remove management service' dialog, it is required to clear the current selection in order to view the other available management services.
- A management service can only be reconfigured from the actions menu by selecting 'Apply/remove management services'. Reconfiguring from servers dialog is currently disabled.
- In advanced settings, the value of 'Show server as disconnected after' should be higher than 4 minutes.
- On cases in which a server that communicates via vSphere becomes disconnected, and any action on that server fails due to discovery source deactivation error, it is required to either perform another action or to clear and re-assign server account.