LogLauncher Version 3.6.
A simple tool that brings ConfigMgr related and other logs together, in one view
Automatically 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 open multiple LogLauncher instances.
Choose a single or multi-select several logs, tap the Launch Logs button, or press Enter, or right click the log area and select Open.
Zip all or a selection of the logs discovered.
Monitor log changes visually using a colour gradient, easier on the eye to detect changes that processing a date\time stamp.
Please note: to use this tool you'll need a Tracing tool. You'll find CMTrace in the ConfigMgr distribution media, and on Site servers, and you can download Configuration Manager Support Center to obtain CMLogViewer
a more modern version of CMTrace.
Source code: Published on GitHub
Pretty simple to use, read the Help built into the tool, get ready, point it at a device, click Scan and off you go.
NOTE: Will update all images to V3.6 soon, see changes in-tool using the Help button
- Get to ConfigMgr, OS, OS Role logs easily, quickly
- Scan multiple devices and navigate between them in the Navigation Panel, rather than opening a LogLauncher instance for each device you want to scan
- Visualise changes to logs over time using the monitoring feature
- Choose your own Tracing Tool such as CMTrace, CMLogViewer, or any tool that can read files and render them in real-time such as Notepad++
- Open multiple logs in one trace tool, or open a trace tool for each log
- Integrates with the ConfigMgr Console, located in the Devices node and context menu\ribbon (Uninstall to remove integration)
- Log hints for known SCCM\ConfigMgr logs (hover over a log to see a tooltip description of the log, not reliable when monitoring is running)
- Add custom locations for log scanning, using Fixed Drives (C:) or Shares (SHARE:) as custom locations which are then included in scans of devices
- Launch Configuration Manager Support Center directly from LogLauncher (if it is installed)
- Change a ConfigMgr Site or a Clients Log Settings, using the Log Settings feature (Restart the Site or Agent service for changes to take effect)
- Hiding Archive logs (*.lo_)
Hiding CM Crashdump folder
Automatic sorting of logs based on their last modified date
Tracer should open log files as merged\multiple, or as single instances of the trace tool per log
- Automatically scans the device the tool is run on at launch time, remembers what devices you’ve scanned for easy access
- Info tab showing diagnostic output for when things are happening, or when they go wrong
- Accepts device name entered on the command line (LogLauncher.exe <DEVICENAME>) for automation purposes (facilitates integration into the ConfigMgr Console)
- Progressive search, focus on the Log Panel and start typing a logs name
- The Navigation Panel can be unpinned to increase the Log view size, the slide effect is disabled in RDP sessions and instead snaps open and closed
- Right-click context menu available for Logs and Navigation panels
- Zip fully integrated into the tool. Zip functionality accessible from the Navigation Panel from where you can zip up logs from the root node to the Product nodes, or from the Logs Panel where you can zip up a log or a selection
of logs, and from both you can open the Zip folder, which is configured by default to C:\WINDOWS\TEMP, and which can be changed on the Configuration Tab. The Ribbon button for ZIP allows you to perform all Zip operations
- Automatically refresh logs when moving around the navigation panel (can be toggled on\off)
- Change font and font size in the Configuration tab
- Rescan a device, useful for when custom locations have been added and a device rescan is require to detect the new rules
- You can now monitor the Product and Category (ConfigMgr, IIS, SQL), whereas before you could only monitor a Category (Site)
- Press F5 when in the Navigation or Log panel to refresh just like File Explorer
I'd like to take the opportunity to thank the tool testers who kicked the tyres as I developed from V1 to V2, not only did they find fault where faults where, but they also contributed some great ideas to the tool!
My thanks to:
- Zeng Yinghua (Sandy)
- Mark Aldridge
- Simon Dettling
- Paul Winstanley EM MVP
- Niall Brady EM MVP
- Ami Casto EM MVP
- Duncan McAlynn
- Others who have given me tips and feedback on Social platforms, thanks!
If you want, you can tweet me on @RobMVP with suggestions for new log locations, as well as if it errors :-P
Have fun with the tool.