Forum Discussion
VasilMichev
Aug 05, 2017MVP
Check out the new PST collection tool
Microsoft has released the successor of the PST Capture tool, named PST Collection tool. Apart from helping you with "collecting" PST files in your network, it can also "lock down" their usage. Detai...
Richard Innes
Aug 22, 2017Copper Contributor
Hi,
Set the location as \\pc-name\c$ and the .csv was generated, have around 100 machines to scan so will give the OU scan method a go to see if that generates the .csv successfully.
Thanks,
Richard
Carlos Rondan
Aug 28, 2017Copper Contributor
I'm getting the same results. The .csv file is generated when you use the UNC path. DN and FQDN output files are .xml and .log file
- Richard InnesAug 29, 2017Copper Contributor
Wonder if it is a bug in the tool, who would we contact at Microsoft about this?
- Jan 25, 2018
Vasil Michev or Paul Cunningham, do you know who the product manager is or the best way for a user to file a bug report?
- VasilMichevJan 25, 2018MVP
No, sorry. You can ask on the Exchange list I guess, or just submit it via support ticket.
- Derek GreczynSep 01, 2017Copper Contributor
No luck here either. Using UNC path (\\machinename\c$) it won't even connect successfully in FIND mode. I haven't yet been able to get csv output in any tests.
- Ken AppelSep 20, 2017Copper Contributor
Nice to see I'm not the only one with issues. I didn't find this thread previously.
I posed my experience here: https://social.technet.microsoft.com/Forums/msonline/en-US/a0b21547-8456-4b4f-b368-f4e59bb8d28f/new-pst-collection-tool-completely-and-utterly-broken?forum=onlineservicesmigrationandcoexistence
Long story short, the tool is 100% broken.