Considerations for managing CylanceHYBRID
CylanceHYBRID
CylanceHYBRID
is deployed as a single instance. CylanceHYBRID
does not currently support multi-node clusters for load balancing or high availability.Item | Description |
|---|---|
CylanceHYBRID local user account password | Currently, there is no mechanism to reset or recover the password unless you have configured CylanceHYBRID to use Microsoft Active
Directory .
For more information, see Change the password of the local user account. |
Communication through another CylanceHYBRID application | A CylanceHYBRID application cannot communicate to or through another CylanceHYBRID application. |
Static IP address | CylanceHYBRID does not support management-console static IP addresses. |
Cylance API | The Cylance API cannot be used to modify the CylanceHYBRID application. |
Cylance Endpoint Security management console | A CylanceHYBRID application appears in the Cylance Endpoint Security management console, but currently it cannot be managed from the console. |
Devices connected to CylanceHYBRID | Devices configured to communicate with CylanceHYBRID must be able to communicate with the DNS host name that you created for CylanceHYBRID over TCP port 443. After a device is registered with the CylanceHYBRID console, disconnecting the device from the corporate network (for example, taking a laptop home), results in the device being offline. In offline mode, agents will continue to function as designed, using the last policy update received while the device was online. |
Virtualization high availability | If your virtualization application has a redundancy feature, you should use it to provide failure protection against hardware and operating-system outages for your CylanceHYBRID environment. As an example, see VMware's article on high availability on their website. However, the active node and redundant node(s):
|