• Facebook
  • RSS Feed
  • Instagram
  • LinkedIn
  • Twitter
Mar 202012

Yet another frequently asked question when migrating PSTs with Enterprise Vault is :


Why is the scanning for computers/devices taking so long?




The reason is that a remote procedure call is made by the PST Locator Task to each discovered device, in turn, to determine whether it is a NetApp filer or not.  This is not an expensive operation when the machine in question is online, but in some organisations where there is a large number of laptops (for example) many devices may not be connected to the network all the time.  The issue then is that this remote procedure call must wait to time out.  That can take up to 30 seconds.  Consider that against say 100,000 machines.  You can see how it might quickly add up, and besides you might not have any NetApp Filers in the organisation?!

One thing that you can if you suspect it’s this scanning, and checking, that is taking a long time is to look in the DTRACE of the PST Locator Task when it starts up for this entry:


82     03:49:28.427  [2696]       (PstLocatorTask)      <ThreadController:2412>      EV-L   {PstLogFile.LogMessage} Identify NetApp Filers: True


If that is there, you can opt to stop the scanning by performing the following steps:


1.  Copy the file Example PstLocatorTask.exe.config to a PstLocatorTask.exe.config

2.  Edit the following value (i.e. change the default value of ‘true’ to ‘false’


<!– Determine whether computer is a NetApp Filer: Default: True –>

<add key=”LocateNetAppFilers” value = “false“/>


3.  Save and Close the file.


Once you’re done with that you then restart the task (and verify with DTRACE that the scanning is now turned off).  

The discovery should now be much faster.  


What do I do if I have a few filers, but thousands of workstations to discover?

You can then always go in to the list of discovered devices and ‘tick’ the checkbox against the devices which you know are NetApp Filers.  So you can definitely use this method to speed up discovery in pretty much every environment.


Image credit: tj scenes

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>