# Licensing and Brain deployment overview ## Licensing Overview Appliance code has been encrypted to protect Vectra’s intellectual property and a license is required to enable successful decryption of the file system and complete deployment. The licensing for Vectra NDR (formerly Detect for Network) running on VMware Brains also governs the ability of the system to create Detections. {% hint style="warning" %} **Please Note:** After deployment, if your Vectra NDR license expires, Detection algorithms will cease operation until a valid license is applied. Recall and Stream operation are unaffected if your Vectra NDR license expires and your Recall and/or Stream license is valid. {% endhint %} ## Licensing Enforcement Vectra NDR (Detect for Network) supports licensing functionality regardless of the type of deployment (physical appliance, cloud IaaS, VMware). All versions will be able to see license status and enable requests for and application of licenses. Enforcement of NDR licensing is only enabled on VMware and Nutanix Brains. Any other Brain type does NOT currently have licensing for NDR enforced. Vectra does plan to add licensing enforcement for other Brain types in the future. It is recommended that all customers work with their account teams to ensure their licensing is up to date. Please refer to the following table for additional detail:
ProductDeployment TypeLicense Enforcement
NDR (Detect for Network)VMware Brain
Nutanix Brain		Algorithms stop producing Detections when expired.
NDR (Detect for Network)Physical or Cloud BrainsNot currently enforced. Planned for future (timing TBD).
Other Vectra products are also licensed but enforcement of the license is a matter of contract compliance between sales teams and customers or partners. ## VMware Brain Deployment Overview Deployment of a Brain appliance in VMware environments can be done on both standalone ESXi servers using the embedded host client or in full vSphere environments using vCenter to manage your virtual infrastructure. {% hint style="info" %} **Please Note:** * If deploying on standalone ESXi servers using their embedded host client, configuring a static IP is not possible until after the deployment is completed and you have access to the Brain CLI. * DHCP is the only supported IP assignment method while using the embedded host client. * Deployment using vCenter allows for Static or DHCP IP assignment of the Management port for the Brain appliance. {% endhint %} The main steps for the deployment are summarized below. For additional detail see [Brain Deployment in VMware](#brain-deployment-in-vmware). {% stepper %} {% step %} #### Download the .OVA * Download the .OVA Brain appliance image from * To see the download option, you must be logged into your Vectra Support Portal account. {% endstep %} {% step %} #### Deploy the .OVA Deploy OVA in VMware and power on the appliance using one of the below methods: * Using the embedded host client on standalone ESXi will require that DHCP be available to the Brain appliance when booting for an IP to be assigned. * After the system is licensed and the CLI of the Brain is available for login, if a Static IP is required, the initial DHCP setting for the management port can be changed to a static assignment using the CLI of the Brain. * Using vCenter with a vSphere client to do the deployment in VMware allows for either a Static or DHCP address assignment for the initial boot of the Brain appliance. {% endstep %} {% step %} #### License the Brain * Browse to the IP assigned to the Brain’s management interface to see the initial boot status messages. The status message screen will update but a manual refresh is required to display any new information. * When you are able to see the **System Setup and Provisioning** screen, enter proxy information if required for your environment and then enter the **License configuration** screen. * Copy the licensing request code from the Vectra UI. * Back on the Vectra customer portal, paste the license request code into the Licensing Request form in the **Enter Authorization Code** box available at . * Copy the license once generated and paste it into the Vectra UI **Licensing Information** box. {% hint style="warning" %} **Please Note:** If your Brain deployment will not be online (connected to Vectra’s provisioner/updater system, this is only supported for Quadrant UX deployments), check the **Offline** box to enable an offline deployment. This means all licensing functions will be done manually offline. * If the **Offline** box is not checked prior to hitting the **Save** button, the deployment will fail and will need to be started over with a fresh deployment of the OVF template. * [Offline updates](https://docs.vectra.ai/operations/readme-1/offline-updates-v89) mode is automatically enabled when selecting the offline deployment mode. * VMware Brains deployed in offline mode can **never** be updated online. {% endhint %} * Click **Save** on the licensing configuration screen. {% endstep %} {% step %} #### Complete Provisioning * After the license is validated, the file system will be decrypted, a performance test will be run, the Brain will reboot, and the Brain will reach out to the Vectra provisioning server and complete provisioning (if the deployment is in online mode). * Offline Brains follow a similar process but do not need to communicate with the provisioning server and can validate the license locally. * Finally, a success message will be presented with a button to redirect to the main UI login screen. * For RUX deployments, please see the deployment process in the [Vectra Respond UX Deployment Guide](https://docs.vectra.ai/deployment/getting-started/respond-ux-deployment-guide). {% hint style="warning" %} **Please Note:** When doing a RUX deployment, you should **NOT** login and configure anything in the Quadrant UX (which would be available at this point) before Vectra connects your Brain to the Vectra cloud. Once the Brain is connected to the Vectra Cloud, the UI for your deployment (Respond UX) will be served from Vectra's cloud and the local UI (Quadrant UX) will no longer be available. {% endhint %} * For QUX deployments only: * Initial login credentials for the UI: * `admin` / `changethispassword` * Initial login credentials for the SSH access to the CLI: * `vectra` / `changethispassword` * You will be asked to change the password after the initial login. * Complete your configuration using instructions available in the [Vectra Respond UX Deployment Guide](https://docs.vectra.ai/deployment/getting-started/respond-ux-deployment-guide) or [Vectra Quadrant UX Deployment Guide](https://docs.vectra.ai/deployment/getting-started/quadrant-ux-deployment). {% endstep %} {% endstepper %}