Hey all, I am having issues starting connecting my windows machine to fleet. I have an installer that i've used across hundreds of windows machines. I used that same installer (same flags etc) on a virtual machine hosted on vultr. The fleet osquery service is running, but I don't see the new host on fleet. In the logs I see the following recurring message:

ERR: run orbit failed error="found a new hardware uuid, restarting"

. I do have the --host-identifier=uuid flag set. although I'm not sure why that would break anything. In addition, I changed the flag to instance, and then hostname, and restarted the service each time and still didn't work. Any ideas?

It sounds like in this particluar environment, the hardware uuid isn't consistent. Changing the osquery flag will help with the osquery portion, but it doesn't carry over to Orbit. You can build a new fleetd package with the host identifier set to instance to get around this:

fleetctl package --type msi --fleet-url  <url> --enroll-secret <secret> --host-identifier instance [...other options]

Hi folks! We are fixing this issue in next fleetd version 1.28.0 (to be released sometime next week). Issue: #20168.

ahh thanks @Kathy Satterlee. I will try that.

Thanks so much @Lucas Rodriguez

I wonder if affected nodes need to be upgraded manually as they are in a constant crash loop