Manually deploying a new BigFix Virtual Relay instance

In case of manual deployment, the network parameters request is automatically displayed.

If you specified "y" (yes) to the DHCP mode when creating the template, you are required to enter the host name used by the virtual machine instance and review the displayed DHCP information.



If you specified "n" (no) to the DHCP mode when creating the template, you are required to enter the host name used by the virtual machine instance and all the related network parameters.



Enter the static IP parameters of your network.



Review or confirm that the displayed parameters are correct by pressing ENTER.



Confirm that the network configuration is correct by entering "y" (yes).

If during the template creation you specified "n" (no) for the masthead setup, the following panel is displayed:



Enter the BigFix server parameters, IP address and port number.

Note: You cannot provide as an input into the configuration procedure of Tiny Core an authenticating relay (_BESRelay_Comm_Authenticating=1), because the current configuration procedure does not allow you to enter the password required to perform a registration to an authenticating relay. Therefore, the first parent relay of a Tiny Core relay cannot be an authenticating one. But once registered, the Tiny Core relay can be moved as a child of an authenticating relay and it can be configured to be itself an authenticating relay.
Note: Even if you specify the relay IP address, the Virtual Relay will connect directly to the server and not to the indicated relay.

The instance was configured successfully and the BESClient and the BESRelay services begin to start.



Log in as tc user.

After logging in, the following information is available:
  • The Virtual Relay name.
  • The BigFix server IP address.
  • The VMware Tools status (Running, Not running, Not installed).


You can check the status of the BESClient and the BESRelay services as follows:



The Virtual Relay instance is ready to use.