{"id":381,"date":"2012-06-19T14:24:07","date_gmt":"2012-06-19T14:24:07","guid":{"rendered":"http:\/\/www.foldersizes.com\/wordpress\/?p=381"},"modified":"2021-01-19T20:03:46","modified_gmt":"2021-01-19T20:03:46","slug":"foldersizes-6-network-share-discovery","status":"publish","type":"post","link":"https:\/\/www.foldersizes.com\/wordpress\/index.php\/2012\/06\/foldersizes-6-network-share-discovery.htm","title":{"rendered":"FolderSizes Disk Space Manager Network Share Discovery"},"content":{"rendered":"

In this blog post, we’ll be taking a closer look at the new network share discovery<\/strong> feature of FolderSizes 6.<\/p>\n

Network share discovery addresses a common file system analysis scenario – you need to analyze one or more shares on a remote (network) server, but you don’t know precisely which shares it exposes. Or perhaps you know the share names, but want a more efficient method of accessing them via FolderSizes (versus entering them all individually).<\/p>\n

It’s also tricky with so many remote staff so we strongly suggest that you get some good activity monitoring software<\/a>\u00a0if you have a lot of remote staff.<\/p>\n

In FolderSizes 6, network share discovery is accessible in a couple of different (but related) ways. One option is to click the down arrow adjacent to the Paths button in the main window ribbon bar. The resulting pop-up menu contains a Server or NAS Device option.<\/p>\n

\"\"<\/a><\/p>\n

Choosing this option will reveal a new dialog window that prompts you to enter the host name or IP address of the remote server \/ NAS device.<\/p>\n

\"\"<\/a><\/p>\n

Note that in the screenshot above, we’ve entered the name of two<\/strong> different servers. You can enter as many server names (or IP addresses) as you need, separating each with commas.\u00a0Once done, FolderSizes 6 will enumerate the public shares on the target system and offer a selection dialog.<\/p>\n

\"\"<\/a><\/p>\n

Clicking OK on the Choose Network Shares dialog will initiate a file system analysis for all selected shares.<\/p>\n

You can also initiate network share discovery directly from the FolderSizes path input box<\/strong> that appears just below the main window ribbon bar. To specify multiple servers (or IP addresses), separate them with a pipe symbol.<\/p>\n

\"\"<\/a><\/p>\n

When using the path input box method, you can even mix a combination of server names (which would always be prefixed with two backslashes) and fully qualified paths. For example, you might enter the following combination:<\/p>\n

\\\\mantis | \\\\panda | c:\\temp | \\\\testserver\\share1<\/span><\/p>\n

FolderSizes 6 will simply “do the right thing” when given the input above by selectively resolving shares on the server names while still retaining the fully qualified path inputs.<\/p>\n

Network share discovery features have also been integrated into the File Report and Search<\/strong> windows. In fact, the File Report Generator path input box exposes the same path resolution features that are described above.<\/p>\n

And now for the coup de gr\u00e2ce<\/em> – this same network share discovery capability is also available from the command line and scheduling<\/strong> interfaces. In command line \/ scheduling scenarios, FolderSizes 6 will enumerate (and then analyze all) network shares silently <\/em> – without prompting the user to select from a share listing, etc.<\/p>\n

Ready to try it for yourself? Download<\/a> the free FolderSizes 6 15-day trial now.<\/p>\n","protected":false},"excerpt":{"rendered":"

In this blog post, we’ll be taking a closer look at the new network share discovery feature of FolderSizes 6. Network share discovery addresses a common file system analysis scenario – you need to analyze one or more shares on a remote (network) server, but you don’t know precisely which shares it exposes. Or perhaps […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1,5],"tags":[],"_links":{"self":[{"href":"https:\/\/www.foldersizes.com\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/381"}],"collection":[{"href":"https:\/\/www.foldersizes.com\/wordpress\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.foldersizes.com\/wordpress\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.foldersizes.com\/wordpress\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.foldersizes.com\/wordpress\/index.php\/wp-json\/wp\/v2\/comments?post=381"}],"version-history":[{"count":10,"href":"https:\/\/www.foldersizes.com\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/381\/revisions"}],"predecessor-version":[{"id":868,"href":"https:\/\/www.foldersizes.com\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/381\/revisions\/868"}],"wp:attachment":[{"href":"https:\/\/www.foldersizes.com\/wordpress\/index.php\/wp-json\/wp\/v2\/media?parent=381"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.foldersizes.com\/wordpress\/index.php\/wp-json\/wp\/v2\/categories?post=381"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.foldersizes.com\/wordpress\/index.php\/wp-json\/wp\/v2\/tags?post=381"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}