Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-09-2014 04:55 PM
While poking around I noticed this file on some machines that was very large. 1gig i think....
%windir%\system32\wbem\logs\Framework.log
this is a file that holds errors and should only be 64Kb max. there is some bug in windows xp and server that sometimes makes it very large when using wmi it seems.
in any case, I suggest scanning for it in custom file scan and see if you find any large files you can free up. It may also indicate a problem if the service pack IS installed.
%windir%\system32\wbem\logs\Framework.log
this is a file that holds errors and should only be 64Kb max. there is some bug in windows xp and server that sometimes makes it very large when using wmi it seems.
in any case, I suggest scanning for it in custom file scan and see if you find any large files you can free up. It may also indicate a problem if the service pack IS installed.
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2014 05:32 PM
For anyone interested in scanning this file: custom file scanning can be configured in the Lansweeper web console under Configuration/Scanning Setup/Custom Scanning. General file scanning instructions can also be found here: http://lansweeper.com/kb/19/report-based-on-file-information.html
1 REPLY 1

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2014 05:32 PM
For anyone interested in scanning this file: custom file scanning can be configured in the Lansweeper web console under Configuration/Scanning Setup/Custom Scanning. General file scanning instructions can also be found here: http://lansweeper.com/kb/19/report-based-on-file-information.html
