How to fix?
# fleet
e
How to fix?
k
Hi @Eric Ackerman! How long ago was this host enrolled in MDM? It can occasionally take a while for the agent to install. You can check to see if it was installed but isn’t working properly by running
sudo orbit version
in the terminal.
e
like 30 minutes ago.
Let me check
sudo: orbit: command not found
Should I remove it and re-install?
how?
Any thoughts? I am connected right now with the user
k
We can give it an hour or so to see if the agent installs automatically and go from there, or you can manually install the agent now so you don’t need to wait and see.
Either way, you can check the Fleet server logs to see if there are any errors!
e
Manual install the agent is doing all of the steps I originally did correct?
k
You can use the package you’ve already built if you can remote in to that machine.
e
Yes, I will do that. hold on
k
And you won’t need to do the MDM enrollment portion (downloading the profile from Fleet Desktop) since you’ve already installed the profile and the host is MDM enrolled.
e
it worked!!! Thanks
How do I install it for a Windows machine?
k
For a Windows machine, you’ll build a new .msi package and install it essentially the same way.
If you’ve also got Windows MDM turned on, it works a bit differently.
As long as the host isn’t enrolled in another MDM, it should automatically enroll in Fleet. That can take a bit because there are some checks that need to happen first.
(After you install the agent)
e
Can I build the package in a Parallels VM?
k
That should work. You can also build on your Mac if WiNE is installed (or Docker if you have an Intel Mac).
You’ll also need either Docker or the Wix toolset on Windows.