Starting Callback

To start On-Premise Callback, perform the following:

• Verify the following services are already started on each Management instance:
  • RabbitMQ
  • VHT Authorization
  • VHT Management API
  • VHT Notification Server
  • VHT Statistics
• Verify the VHT Datastore is already started on each Core instance
• Start the VHT Core Monitor on each Core instance.
• Start the VHT Peripheral Monitor on each Management instance.
• On each Management instance, navigate to the Configuration Management installation directory (default is C:\Program Files (x86)\Virtual Hold Technology\ConfigurationManagement) and confirm that a Mnesia node named Mnesia.confmgmt@domain_name has been created.

If the Mnesia node does not exist, perform the following, as an Administrator.

• If necessary, stop the VHT Configuration Management service.
• Navigate to the \bin directory inside the Configuration Management installation directory.
• Double-click the first_time_initialization_of_configuration_management_datastore_connection.cmd file.
• Confirm that the Mnesia node now exists in the location listed above.
• Repeat these steps on each Management instance.
• Start the following services on each Management instance:
  • VHT Agent Priority (if you plan to use the Agent Priority feature)
  • VHT Configuration Management

Stopping Callback

To stop On-Premise Callback, perform the following:

• Stop the following services on each Core instance:
  • VHT Core Monitor
  • VHT Datastore
• Stop the following services on each Management instance.
  • VHT Agent Priority
  • VHT Authorization
  • VHT Configuration Management
  • VHT Management API
  • VHT Notification Server
  • VHT Peripheral Monitor
  • VHT Statistics
• Stop the RabbitMQ service on all instances.