ConfigMgr LogFile Opener

Script and Content relocated to GitHub: https://github.com/simondettling/ConfigMgr-LogFile-Opener

 
 
 
 
 
5 Star
(4)
Add to favorites
System Center
9/8/2020
E-mail Twitter del.icio.us Digg Facebook
  • One Trace as a log Opener and Right Click feature
    2 Posts | Last post December 13, 2019
    • Hi Simon, 
      
      Thank you for your tool. I like it.
      Possible 2 new features
      
      Integrate in the future release the One Trace Log Program as default open log files?
      
      Possibility to have the "Right Click" in SCCM under Device, that start directly ConfigMgr LogFile Opener?
      
      Thank you
      Regards
      Mauro
      
      
    • Hi Mauro
      
      OneTrace is on my to do list, right now however the process for calling OneTrace via the CommandLine to open multiple log files doesn't work properly.
      
      There is a Console Integration feature in the Settings Menu (X), that will add ConfigMgr LogFile Opener to the right click menu in the Console, for every device.
      
      Regards
      Simon
  • Suggestion for future; Include app\update workflow logs
    2 Posts | Last post May 01, 2019
    • Hey mate, love the tool; suggestion for improvement. I've updated the code myself with extra entries to open all files relevant for an App deployment and an entry for Software updates. This includes all log files that should be relevant while troubleshooting each instance. Could possibly take out or add logs if desired (ie add or remove clientlocation.log or locationservices.log for possible boundary issue)
      I find this amazingly handy to open more than one log at once, in this instance everything needed to troubleshoot an app issue (appintent through download through to appenforce) or update issue.
      
      Code updates below:
      Line 169:
      	'Updates' = @{
              'path' = $clientLogfilesDir
              'logfiles' = @('UpdatesDeployment.log','ScanAgent.log','WUAHandler.log','UpdatesHandler.log','ContentTransferManager.log','CAS.log','LocationServices.log','UpdatesStore.log','DataTransferService.log')
          }
      	'AppDeployment' = @{
              'path' = $clientLogfilesDir
              'logfiles' = @('AppDiscovery.log','AppIntentEval.log','AppDiscovery.log','CAS.log','ContentTransferManager.log','DataTransferService.log','AppEnforce.log')
          }
      
      Line 921:
          Write-Output ' [19] Updates.log'
          Write-Output ' [20] AppDeployment.log'	
      
      Line 955:
         19 {Open-LogFile -Action 'Updates'}
         20 {Open-LogFile -Action 'AppDeployment'}
      
      
    • PS; I found that with the cmtrace.exe located in c:\windows\ccm by default, it now needs elevation to run which isn't ideal. Can change it using the switch but ive got this as a function in a module, so changed the parameter default in the code and copied cmtrace to c:\windows.
  • What if you dont have access to c$
    2 Posts | Last post December 16, 2016
    • Any way this could be done using a service account - with, of course, the password obfuscated somehow (encryption?)??
      
      also would be cool if there was a copy log local option if you were unsure how long the remote computer was going to remain online. 
      
      Thanks!
    • Thanks for the feedback
      
      Service Account will be tricky, as the way PowerShell interacts with CMTrace. However, you can launch PowerShell with a Service Account and launch the LogOpener from there.
      
      Copy local option will most likely not be implemented. You will loose the Realtime Updating of the logs as they remain static.