FQDN is Missing in Control

Prev Next

Issue: 

When deleting and creating a new virtual machine (VM) in the Workspot Cloud-Pool, the new VMs are not joining the domain and Fully Qualified Domain Names (FQDNs) are not showing in the Workspot-Control. 

 

 

Resolution: 

To resolve this issue, follow these steps to clone the base template, log in to the cloned Template VM, and validate the configeditor.xml file in the Workspot Config-Editor. 

Steps to Validate Workspot Config-Editor: 

  • Clone the Template: 

  • Clone the base template and log in to the cloned Template VM using its IP address. 

  • Navigate to Workspot Config-Editor: 

  • Go to the path C:\Program Files\WorkspotAgent. 

  • Right-click on the WorkspotConfigEditor.exe file and select "Run as Administrator." 

A screenshot of a computer

AI-generated content may be incorrect.

 

  • Configure Workspot Config-Editor: 

  • In the Workspot Config-Editor, configure the values at the highlighted places (these are typically the settings related to domain and FQDN). 

  • Validate the configuration by clicking "Test Secure Credentials" and then click "Submit." 

  • Start the Workspot Agent Service: 

  • Open the Run dialog (press Windows + R), type services.msc, and press Enter. 

  • Find the "Workspot Agent" service, right-click, and select "Start" if it is not already running. 

  • Log off and Move Template to Published State: 

  • Log off from the Template VM after making the changes. 

  • In the Workspot Control, move the Template to the "Published" state. 

  • Assign Template to Pool: 

  • Assign the newly configured template to the pool WestEUGPUNV12. 

  • Try creating a new VM inside the pool to verify that the domain joins and FQDNs are now appearing correctly in the Workspot-Control.