Hi Waqas-AM,
I don't know a whole lot about scripting, and most of my work with the add-in installations revolves around pushing them out, but here are a few points:
-Your script seems to remove the registry key and the cache folder, but not remove the add-in folder. That does still beg the question of how the header cache is being mounted as a pst in Outlook; that I'm unsure of. But either way, the add-in could still get loaded by Outlook in that regard.
-After you run the script and then launch Outlook, does the path for that EV Vault Cache now exist again?
-Why use that method, rather than some kind of GPO that just blocks the EV add-in all together? I'm sure there's a good reason, I'm just wondering what benefit you get from doing it this way. If the add-in was not loaded, nothing would attempt to load that header cache file.
-I'm wondering if it's possible that machine had multiple Vault Cache instances existing, or if maybe somehow there's a .mdc file remaining, while all the .db files could be gone. The .mdc is the header cache, and is the only one that would have "Vault" in the title if mounted as a pst.
Anyway sorry it's not an exact answer, but the only thing I could tell you for sure is that it's not uninstalling our add-in, so something is still holding on to those Vault Cache files. Hope this helps at least a little.
