Windows collector not capturing log data via UNC path from remote Host

Problem:

A new windows collector setup was not capturing data from a UNC path expression example. The collector log reported

2015-03-23 18:54:15,719 [Blade00000000079BB8E3-Scanner] INFO com.sumologic.scala.collector.blade.wildcard.LocalWildcardBlade$$anon$1 - Finished directory scanning. Found 0 applicable files. 

The UNC path expression used was 

\\Some_IP_Address\Logs\Application*.log 

Solution:

The Collector may be unable to properly scan your UNC directory if the user account the Collector is using to run, as set by the Run As User, does not have the necessary permissions to access the remote share indicated by the UNC path. Even if the user is root by default on the Collector host, this user may still not have access to the share on host B so you may need to verify the Collector user has permissions to open and read the defined path/file by using the Windows CLI or File Explorer.