One issue we faced with auditing PST’s if that if the PST is not connected to Outlook, the registry won’t contain the PST and you end up loosing visibility of it. What we did was execute a PowerShell script to scan all fixed drives for *.PST files, output the path and size to a text file and then we had a property that would read the file.
For the fixlet/task relevance
((windows of operating system) AND (nt workstation product type = product type of operating system)) AND (not exists file "PSTList.txt" whose (exists lines of it) of folder "TEMP" of windows folder)
For the ActionScript
createfile until EOF
Remove-Item $env:windir\TEMP\PSTList.txt
Get-WMIObject Win32_LogicalDisk -filter "DriveType = 3" | select-object DeviceID | ForEach-Object {{Get-ChildItem ($_.DeviceID + "\") -include *.pst -recurse | select-object fullname, length | export-csv -path $env:windir\TEMP\PSTList.txt -append}
EOF
delete {name of drive of windows folder}\TEMP\FindPST.ps1
folder create {name of drive of windows folder}\TEMP
copy __createfile {name of drive of windows folder}\TEMP\FindPST.ps1
runhidden powershell.exe -ExecutionPolicy Bypass -File {name of drive of windows folder}\TEMP\FindPST.ps1
For the Property
(concatenation "" of substrings separated by "%22" of it) of (lines whose (it as lowercase contains ".pst") of files "PSTList.txt" of folders "TEMP" of windows folder)