Hello Bill - here are some thoughts.
QlikView Governance Dashboard (qvw) uses file paths, QlikView script and its QlikView Expressor engine to access scan an extract from a variety of QlikView related files - (QVDs, QVXs, QVWs and logs). If installed on a shared storage device and the files are accessed via UNC it may cause some performance related problems depending on where the files are and how big they are when attempting to scan an extract the metadata from them.
There is also a known issue where if using UNC - you must have a sub-folder appended to the share when configured in the QlikView Governance Dashboard.
So for example if your share folder name is folder1 pointing to c:\QVDocuments\sub-folder1
then \\machine\folder1 - will not work for the QlikView Governance Dashboard configuration.
Make sure the UNC share is mapped for example to c:\QVDocuments and then when you use it in the QlikView Governance Dashboard - it is used as \\machinename\sharename\sub-folder1
Please post back here to let us know what you found and how you did.
I just installed Governance Dashboard 1.0 (=GD), and the UNC issue is still there. Seems it can be fixed, as noted buy Michael, by sharing a folder higher in the directory hierarcy (on the server/disk where the the logs reside), and then referring that directory from GD's config tab.
Also, scanning large files over the network is a bad-bad-bad idea, in my experience. Having tried a full scan of many 10s (probably 100+ GByte, actually..) of GByte of QVWs and QVDs, it just isn't practical. After watching lots of network traffic passing in the process monitor, it was time to cancel the experiment and go for a local installation on the server where the QVW/QVDs reside.
I'm glad you are working with the 1.0 GA Dashboard.
The workaround is still there for UNC root folders, as you've described and as noted in the Release Notes (GOV-122).
Concerning the delay in scanning large files over the network, I agree that trying to read large files over the network with any tool is not optimal, so a local install might be better. However, if you have large log files - namely years and years of session logs - that will take longer to scan. If this is the case, you might consider paring down your log files (save copies first!) or just keep more recent (and relevant) sessions history logs in the QlikViewServer folder.