image)While this post isn’t about how you could sleep 120 more seconds, it may actually help you fall asleep.
This is a bit of a personal one, because I’ve been really invested in it.
For the last few years, Something that has always annoyed me was waiting for a SUP sync to finish, seeing “Sleeping 120 more seconds” in the wsyncmgr.log and just having to wait for it, never really knowing what it’s actually doing during that snooze.
Logs, Again!
This is a bit of a followup on my last post about collecting log files using Intune.
The log files generated by the Intune Management Extension are extremely useful when troubleshooting a variety of issues, although I focus primarily on Win32 app related problems.
Recently, I have noticed that the IntuneManagementExtension.log is filled with more and more information about the GRSManager, Win32AppInventory and ReevaluationScheduleManager as well as log lines related specifically to Win32 app installations which generate a vast amount of log lines.
Throughout the years of being a SysAdmin, I regularly saw weird and horrifying ways to display notifications to users; usually revolving around VB logon scripts and scheduled tasks :nauseated_face:
You can also display notifications with PowerShell, I’ll share some really useful blogs related to PowerShell notifications at the end.
Let’s talk about Organizational messages.
Well, they’re a pretty cool feature that let’s you get information out to targetted users easier by displaying branded content in visible areas of the desktop.
In many support roles, when troubleshooting an issue, logs are critical, especially troubleshooting Intune-related issues.
My day-to-day role sees me looking at logs for Intune-managed devices, and Win32 Apps, and collecting those logs can be a pain for the admins I speak with for various reasons.
It may seem reasonable to say, “X isn’t working” or “Y gives me an error message”, but these statements are not always helpful without the context provided by log files. Log files give us a detailed view of most things that happened in the run-up to the error and potentially a more helpful error message than was presented to a user.
This post is one in a series about using Graph API with C#, It’s broken down into the following parts
In this post, and Part 2.2, we’ll look at 2 methods of authenticating with Graph API using our app from part 1 as a foundation.
This post is one in a series about using Graph API with C#, It’s broken down into the following parts
Over the last 12 months, I’ve thrown myself into the deep end of learning C#, and part of that rabbit hole has been working with Microsoft’s Graph API.