For a long time it has annoyed me that every time I go to a new device I have to find CMTrace open it and answer a couple of questions before I can simply click on a *.log file and begin troubleshooting. I have been searching for an answer for a while to fix it in my network globally. It seems that I may have an answer by using Group Policy. This post will take you step by step to fix the issue in your environment.
On a device with Windows Administrative tools installed hit start and type "group". When you do this you will notice that Windows searches for items containing the word group. Select "Group Policy Management" from the menu.
Navigate to "Group Policy Objects".
Right click "Group Policy Objects" and select "New" from the menu. Enter a name that suits your environment. I personally like to use names that are descriptive of what the policy is intended to do. So mine will be "Set log files to use CMTrace.exe"- Action: "Update"
- File extension: "log"
- Associated class: "CCM Debug Log"
- Tick "Configure class settings"
- Icon file path: "C:\Windows\CCM\CMTrace.exe"
- Icon index: "0"
- Actions:
- Click "New..." and in the "New Action" window add the following
- Action: "Open"
- Application used to perform action: "C:\Windows\CCM\CMTrace.exe"
- Click "OK" to register the action
- Tick "Always show extension"
- New File Type Properties should look like the below image.
- Click "OK"
- Repeat the "New File Type" process with the only change being File Extension will be "lo_". Note: "lo_" is the extension used when a log file overflows and a new log is started.
No comments:
Post a Comment