09-23-2024 02:25 PM
We recently converted from the legacy free version of Systems Manager to paid, and now things seem to be working differently.
Previously just downloading and running the Meraki Agent on a new machine was all it took to get it to register with the dashboard, but that doesn't seem to be doing it anymore. I've tried from a few different machines and the registration never comes through.
I was able to get one machine on my adding it through the Windows 11 device managment interface, and for that machine things worked fine -- live tools showed up, etc.
Then I deleted the record for my own machine and attempted to start from scratch to figure out the best process moving forward. Adding it through the Windows 11 interface brought it onto the dashboard right away, so far so good. However, even though the most recent downloadable version of Meraki Agent is running and shows up fine in the Services view, I have lost all access to the "Live Tools" for things like remote desktop, and I can't get them to come back no matter what I try.
The one that says "Live Tools" is what it should look like, but the other one where there's just a blank space where those should be is my problem.
Any help would be appreciated!
Jeff
Solved! Go to Solution.
09-24-2024 03:30 AM
Under Systems Manager/General, have you got it configured to use a recent version of the agent?
09-24-2024 01:57 AM
Hello @sesame_uwash,
Judging by the screenshot, it looks like the machine is only being detected under profile installation, and not the Meraki agent - I'd recommend reaching out to Support and they'll likely ask you to provide the agent logs, to see if the unit has successfully registered and is communicating correctly.
This file can be found for agent 4+ here: C:\ProgramData\Meraki\Endpoint Agent\Logs\m_agent_service.log (https://documentation.meraki.com/SM/Other_Topics/Systems_Manager_Logging_and_Troubleshooting#Windows)
Cheers, Connor.
09-24-2024 03:30 AM
Under Systems Manager/General, have you got it configured to use a recent version of the agent?
09-24-2024 04:14 AM
In the end, it was an agent versioning problem. I assumed incorrectly that since I was downloading directly from the SM menus on my fresh install that I was getting a recent version, and that had worked all along, but in fact it was giving back something older that was no longer compatible. The confusing part, still somewhat, was that it worked fine for the brand new machine, eventually, without changing the network version settings as shown in the solution. That must have been a fluke or I must have somehow donwloaded a higher number by some mechanism.
But after changing those settings to "Latest" and re-downloading and reinstalling the agent on my test machines, all was right within a couple minutes. 🙂
Thanks for the replies!
Jeff
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide