LogLauncher Version 3.6.A simple tool that brings ConfigMgr related and other logs together, in one viewAutomatically scans the local device on startup, to scan remote devices tap in a device name.Scan multiple devices and store the results in the Navigation Panel, no need to ope

4.9 Star
5,939 times
Add to favorites
System Center
E-mail Twitter del.icio.us Digg Facebook
  • displaying locale Logs
    1 Posts | Last post October 08, 2018
    • Hi,
      I have installed that tool on my sccm server. If I click on one of devices and right click on that and select "LogLauncher", is not displaying the logs of client machine. Is there any way to do that?
  • MDT log Monitoring:
    2 Posts | Last post September 03, 2018
    • Thanks for this tool
      it's very useful
      Is that possible to include MDT MONITORING? Like Deploymenshare$\LOGS or Deploymenshare$\Dynlogs ?
      Could be great ¡¡¡
      Thanks in advance
    • You can do ths today, using "Locations", add deploymentshare$\LOGS and populate the rest of the fields, connect to the MDT server and you'll see the MDT logs area show up.
      When I turn out V3.7 I will add these log areas in by default so you don't have too.
  • Silent Install error
    2 Posts | Last post September 03, 2018
    • I was hoping to deploy this to app to all of our workstations, but I'm getting this error when I try to install silently (msiexec /i LogLauncher.msi /q /norestart)
      "MSI (c) (20:84) [08:35:48:658]: Failed to grab execution mutex. System error 258."
      This indicates a chained MSI installation error. Any idea what's happening?
    • Hi Nurnay, I believe I know why, the MSI invokes an embedded EXE that handles the registration into the CM console (only works if CM installed to C:), no doubt that is causing the issue.
      It looks like I'll be rolling V3.7 soon, I will move the CM console integration away from the MSI and plug it into the actual tool, that will make the MSI plain and simple. Stay tuned.
  • Automatic SCCM Integration
    4 Posts | Last post December 30, 2017
    • I was wondering if there was a command line argument to run the ConfigMan Console integration without having to open it first. I am trying to automate the deployment of this to all the tech's who have a console.
    • Great idea. Added to the TODO list for 3.6.
      Due to already implementing for 3.6 "console integration removal" during MSI uninstall, "console integration" during install will be a cinch.
    • Just released version 3.6, the MSI will perform the integration into the console, uninstall MSI and it will remove the integration, both feature requests, thanks for yours!
    • I wrote a separate tool called LogLauncherConsoleHandler, and bundled it into the LogLaucher MSI, which then executes so as to integrate into the Console, but this doesn't meet your requirement to do this before installation. So use MSIEXEC /A to unpack the MSI, grab the tool that does the registration and run it where you want. I will need to update to LogLauncher 3.7 to fix a bug in this tool which manifests if ConfigMgr is not installed on C:
  • User-based Config data
    3 Posts | Last post December 30, 2017
    • Any chance you could set the default registry to HKCU instead of HKLM, to allow for standard user operation on a workstation for remote log viewing?
    • Shouldn't be that difficult to do. I'll look at releasing 3.7 with this feature. I have to re-release because the Console Intergration only works if using C: for ConfigMgr.
    • I had a look over the source, been a while :-) I see I don't really put much in HKLM only the location of CMTrace, which I figured at the time is universal for all admins using LogLauncher on a shared device. As long as everyone has access to where CMTrace is located it should work fine. Can you expand on what you are after here buddy?
  • SCCM Deployment
    3 Posts | Last post December 30, 2017
    • Are there install parameters for LogLauncher to set the path to cmtrace.exe and add custom log Locations? 
    • If there is no public property in the MSI properties table, you can wrap the installation with a script and append a registry update to HKLM\Software\SMSMarshall\LogLauncher, Value = TracerPath (reg_sz)
    • There is no automation from the command line for registering CMTrace or Managing the Custom Locations, only specifying the target device to connect too. You can easily hit the Registry to do this, CMTrace details are stored in HKLM\Software\SMSMarshall\LogLauncher and same path in HKLU for the CustomLogLocation. Example: D:\Apps|*.log|True|Volume D|Apps, the separator is |, Path, Filename, Recurse Directory, Log Category, Log Product. As Skatterbrainz says you can work around this by wrapping the MSI with a script, or just running a script ahead of the MSI installation or Loglauncher startup.
  • Opening Mutiple Logs versus Merge
    2 Posts | Last post March 08, 2017
    • Like the tool and very useful, but was curious if there is an option to use the merge functionality of Trace rather than opening up multiple log with trace for easier troubleshooting and readability?
    • You have to do merging manually with CMTrace by using CMTrace's open logs dialog and selecting merge, is not a surface that can be automated. If you try using CMLogViewer from Support Center you'll get the merging take place.
  • CMtrace not opening
    3 Posts | Last post December 02, 2016
    • I have CMTrace set as default viewer for log files on my system, and cmtrace.exe in c:\windows\system32. But when I view a log file in Log Launcher, it opens the file with Notepad.
    • Hi Vern, thanks for this feedback.
      Can I ask you to form the path to a log, and include the log name, put this in Run, and see if it launches Notepad or CMTrace to view the log.
      Put this into the Run box: C:\Windows\CCM\Logs\CAS.LOG
    • Also, curious, are you running the tool using another account than which you are logged in with? It could explain CMTrace not being associated if this is the case.