Log purpose/description can be found again in official documentation. TIP: you can use the parameter maxHistory to open archived logs too Get-CMLog function then decides what logs should be opened, output description for each of them, and opens them in preferred log viewer application 👍. For example: ApplicationInstallation, ClientInstallation, PolicyProcessing, Co-Management, PXE, Compliance, etc (its approx 50 of them). I took all these by-functionality-grouped logs and make them available through Area parameter which therefore lets you specify what kind of problem you have. To get some more examples, check official documentation, mainly the Log files by functionality part.Īnd that is what I did too when Get-CMLog function was created. For "PXE" related issues 'Distmgr', 'Smspxe', 'MP_ClientIDManager' etc. For "Application Installation" there are 'AppDiscovery', 'AppEnforce', 'AppIntentEval', 'Execmgr'. logs in the Log Viewer application.įor each issue you can encounter there are different logs to check. Install module SCCMStuff, import it and call function Get-CMLog or download, dot source, and then run Get-CMLog function like thisĪs you can see this test shows debugging SCCM client installation issue so the function opens ccmsetup, ccmrepair, client.msi. So what I've done is that I've created PowerShell function Get-CMLog that solves all those complications I've mentioned above and more 🤯! But it's quite long and it can take a while to find the correct information. There is a nice official page with list of all available logs and their description. Not mentioning the dynamically named logs. And there are also several locations where the logs are stored. Moreover, some logs are stored on the client side, some on the server side. To make it more interesting if you try to solve issue like "why isn't this application deploying?" you have to open not one, but several logs to get the solution. These words some and somewhere are really important though 😀. Almost every action is logged.in some log which is stored somewhere. As you probably know SCCM has great logging capability.
0 kommentar(er)
