@msupport Right! I'm sure it's a great product, the goal for this is to have no licenses, unlimited users, ported for several hypervisors. It's just a pet project I've wanted to do since I started in IT, and if other people besides me can use it, great! I know one of my employers may work on making it a polished project if the Omnissa renewal is too expensive. And if I can build it, why pay for it? I might not be a programmer by trade, but there's no reason I can't learn and ask around for help!

@nathanael-h Dang, do any of you sleep?! This is pretty much what I need, and would actually significantly improve what I'm building! Will wait_for_ip be included? As well as the rest of the Terraform logic? But as you're building a Python script you could implements there the same logic: define a variable for your expected cidr, and poll the IP of the VM until it matches. Duhh, Why didn't I think of that . Thanks for the help!!

@Danp The file is getting removed every time, that's why I was questioning the behavior of the command (whether it is grabbing all records or cached records). We can do that, but if the user is deleted, that user entry would be gone.

That's what it was. For whatever reason, ubuntu defaults to installing these versions for node and npm respectively: v12.22.9 8.5.1 Following the steps here fixed it. As always, thanks!!

@nick-lloyd I think the answer would depend on the state of your XAPI database given the fact that each host thinks that it in the pool master. To convert one or more of the hosts to a slave, you would need to -- edit the file so that it contains slave:<IP address of master> instead of master run mv /var/xapi/state.db /var/xapi/state.db-old to get rid of the old xapi database reboot the host Once rebooted, the xapi database will be regenerated by syncing with the pool master.