Hi Glenn.

The ListShares action will output the list of shared foders (often abbreviated to "shares"). Each shared folder is the root of a directory tree under it. Note that these "shares" are not directories (even though in Windows Explorer they have the same icon as a directory), instead they are an entry point to the directory tree. I think they are very similar to having many hard drives, so this might help you understand: you first have to select which hard drive before listing the files, because each hard drive has its own directory tree.

All other actions that deal with directories and files require the Share parameter, which is the name of the share you will be using. For example, ListFiles has a Share parameter, and also FolderPath, and it lists all files inside the directory FolderPath, under the corresponding Share.

The WriteFile action works in the same way. You need to specify which share to write to, but also which FilePath under the share to write to.

If you're used to work with UNC paths, then a path to a file would be something like \\hostname\share\path\to\file.txt - and in this case:

• "hostname" is the name of the host
• "share" is the name of the Share (note how it could be confused as the first directory in the file path, but it's not, it's the share name)
• "\path\to\file.txt" is the FilePath, which determines that the file is located inside the "to" directory, which itself is inside "path" directory at the first level of the share.

You can also use the action ParseUNC to extract the hostname, share, and path information, from a UNC string.

So judging by your screenshot, all you have to do is specify the Share parameter (which maybe you're confusing as being part of the FilePath), and make sure that the FilePath includes the filename as the last component of the path.