In some cases, you will be unable to use the Faddom Sensor deployment feature to automate the deployment of sensor appliances in your VMware environment. This may be due to the version of vCenter you are using, or due to the parameters being provided to Faddom not being sufficient.
To work around this, you can deploy the Faddom Sensors using the PowerShell script below.
To run this, you will need to install the VMware PowerCLI. If you don't have it already, you can do this from the PowerShell Gallery as described here or by downloading and installing it using the instructions here.
After installing PowerCLI, you will need to download the sensor ovf and vmdk files. You can get these from the server UI. Go to Settings->Sensors->New. There you have a link to download the ovf file.
To download the vmdk file, use the link for the ovf file, remove the ".ovf" extension and append "-disk1.vmdk". The link should look like to: "https://<Faddom-Server>/Installations/Sensors/Template/Faddom-Sensor-Appliance-<Version>-disk1.vmdk"
After you have saved the vmdk and ovf files in the same folder, you need to create a configuration file for the deployment script. Below is an example of a configuration file:
vcenterHost: "<IP Address or host name of vCenter>",
esxHost: "<Name of ESX Host 1>",
datastore: "<Datastore for Sensor on Host 1>",
portGroup: "<Name of network to use for communication with the Faddom server>",
ip: "<Free IP address to assign to the sensor>",
netmask: "<Network mask for the ip address>",
gateway: "<Network gateway for the ip address>",
password: "<Password for the sensor VM minimum of 8 <charecters>"
portGroup: "VM Network",
To execute the script, open PowerShell and run:
.\DeploySensor.ps1 <Configuration File>
After the script has finished deploying the sensors, it will provide you with a list of IP addresses for the deployed sensors. You will need to add the sensors through the Faddom UI under Settings->Sensors if they are not defined there already.