Users love to keep their email for as long as they possibly can, but when IT Admins start telling them to archive their email because their mailbox is too big, sometimes things get worse and PST files end up being created all over your corporate Filestores. Even worse than that, users will create their PST files and keep them locally on a computer in some obscure location (normally AppData…!) and when it comes to rebuild time, they do not tell you about these PST files and it’s all your fault that you have exterminated 15 years of emails about cakes being in the kitchen!
So, how can we fight back?
Well, first things first, we need to know where these PST files are, be it on local machines or on network Filestores. So using Configuration Manager, we will set our Client settings to inventory PST files when the Software Inventory is run.
To do this, go into your Client Settings within your Configuration Manager Console and click on the Software Inventory option:
Once in the Software Inventory section, click on the Set Types button:
When the pop-up appears, click on the yellow button and add *.pst and click the OK button, this will now appear in your files of files to inventory:
Now what will happen is that your Configuration Manager Clients on the end users machines and servers (if you have the client on servers…) will inventory all the PST files on the machine and then report back to your Configuration Manager server and then inject the data into your database.
Now that you have started the harvesting process of collecting the PST information, you will now want to report on it.
There are many different ways of producing this information using SSRS, PowerBI or just a basic SQL query. For the purposes of this guide, we are going to show you where you gather this information from and you can then edit the query to add whatever extra information you want, like computer name, username etc.