I’ve got a Windows device acting up (configs not applying properly, no clear errors in the portal).
Was thinking of pulling logs, but not sure if that actually helps or just ends up being a dump of useless data. Anyone here actually rely on logs for this kind of thing?
39 Views
Yeah, 100% worth it. Portal usually just tells you that something failed, logs tell you why. Especially for config stuff.
Makes sense. I’ve never really gone deep into logs before, though. How do you usually grab them? Is there some built-in option?
We usually use the device support logs action. It gives a full bundle—pretty straightforward, no extra setup needed.
Hmm, but @diane_ , I don’t think I’ve seen that anywhere. Checked the device actions and policies, couldn’t find anything like that.
Wait! @leo_scott, what device are you working with?
Windows.
Ohh, sorry @leo_scott! ChromeOS brain kicked in there 😅. I was thinking of the support logs action we use on ChromeOS. That one’s kind of a “click and get everything” situation.
Hey all!
For Windows devices, the process differs from that of ChromeOS. You can use the Execute Custom Script action to collect logs. This involves uploading a script to the Hexnode File Repository and running it on the target device to gather the required diagnostic data.
The script can be tailored to collect specific logs such as system logs, application logs, or other relevant files based on your troubleshooting needs.
For more details, refer to our help doc about Script to Fetch Windows device logs.
Best Regards,
Isabel Lora
Hexnode UEM
Ohh, that clears it up.
Thanks for sharing the docs, @isabel_lora. That helps a lot. I’ll go through it and try setting this up 👍.
Don't have an account? Sign up
