Forum Discussion
Check out the new PST collection tool
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
Wonder if it is a bug in the tool, who would we contact at Microsoft about this?
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.
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.
- Is there a way to do this but for OST files that are not where they should be located?
- Is there a way to find OST files that are not located where they should be?
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?
No, sorry. You can ask on the Exchange list I guess, or just submit it via support ticket.
