/build/static/layout/Breadcrumb_cap_w.png

Is there a way to create a report or script to show which devices have a ballooning Windows.edb File?

We have had a recent outbreak of users with hard drives filling up due to the Windows.edb file booming to 100GB in size.  It's found at C:\ProgramData\Microsoft\Search\Data\Applications\Windows on all computers.  Is there a way to create a custom report to show all devices with this file above a certain size?


0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
Posted by: Nico_K 3 months ago
Red Belt
1

The easiest way would be setting up a custom inventory rule ( https://support.quest.com/kb/4262543 ) similar to that:

ShellCommandTextReturn(powershell(Get-Item -Path C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb).Length/1MB  |Where-Object{$_.Length -gt 1GB})

It starts the powershell command and formats it for 1MB size and only updates something if the size of the file is bigger than 1GB, take it as start for your own.

Since I have the file on none of my computers I cannot verify this (with other files it works), since this unuseable search function is disabled in my env.

Then you can report it over its name of the CIR.

Posted by: dolczak 3 months ago
White Belt
0

Thank you for the feedback.  The tricky part with the windows index file is that it's a protected file and cannot be accessed through windows file explorer typically.  We have to use our remote software Simplehelp file explorer to see the size.  I did create the CIR that you requested and will provide some feedback as soon as I can.  When I do find an oversized index file I have a script created to rebuild the index that looks like this:


net stop "Windows Search"
REG ADD "HKLM\SOFTWARE\Microsoft\Windows Search" /v SetupCompletedSuccessfully /t REG_DWORD /d 0 /f
del %PROGRAMDATA%\Microsoft\Search\Data\Applications\Windows\Windows.edb
net start "Windows Search"

Comments:
  • you can create this using the scripting engine to create this script to run on any system in the env.
    Then you create a smart label against the CIR you did before so it can run on any system which shows up there.
    Let the script run (you may need to do this as admin, the SYSTEM (which is the default environment of the agent) may not sufficient. And if all is good, the next check in will kick the system out of the smart label. - Nico_K 3 months ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ