Put Directory keyword didn't work properly under Win10

Nobody has claimed this yet.

_observe:_
Unfortunately we found different behavior of SSHLibrary on systems running under Win10 and Linux (Fedora22).

Especially we mean keyword: "Put Directory" which is covered by our own keyword: "Upload Files ${format}" => "Upload Files decoder/ => take *.pcap files" inside is only simple chain:
Put Directory resources/files/callrec/pcaps/${format} /opt/callrec/data/pcap/
- under Linux everything proceed correctly
- for some reasons under Win10 was files taken from Source correctly, but they was stored in Target system with new and wrong patch: /opt/callrec/data/pcap/resources/files/callrec/pcaps/${format}

_expect:_
same and correct behavior under both OS -> pcap files will be taken and saved in correct patch, without creating sub-folders from Source patch

INFO ABOUT SYSTEMS:
#

_Failing system:_
Windows:
OS Name Microsoft Windows 10 Pro
Version 10.0.10586 Build 10586

RF:
RIDE 1.4

Libraries:
beautifulsoup4 (4.3.2)
cx-Oracle (5.2)
decorator (4.0.6)
docutils (0.12)
ecdsa (0.13)
JPype1 (0.6.1)
jsonpatch (1.11)
jsonpointer (1.9)
numpy (1.10.0rc2)
paramiko (1.15.2)
pika (0.10.0)
Pillow (2.8.1)
pip (7.1.2)
psycopg2 (2.6.1)
pycrypto (2.6.1)
Pygments (2.0.2)
pypyodbc (1.3.3)
python-dateutil (2.4.2)
rabbitLibrary (1.0)
requests (2.7.0)
robotframework (2.8.7)
robotframework-cplibrary (0.9)
robotframework-databaselibrary (0.6)
robotframework-DiffLibrary2 (0.0.2.dev0)
robotframework-httplibrary (0.4.2)
robotframework-jmxlibrary (0.5)
robotframework-lint (0.6.2)
robotframework-requests (0.3.8)
robotframework-ride (1.4)
robotframework-selenium2library (1.7.4)
robotframework-selenium2screenshots (0.5.0)
robotframework-sshlibrary (2.1.1)
robotframework-uccelibrary (0.5)
selenium (2.49.0)
setuptools (18.5)
six (1.9.0)
waitress (0.8.9)
WebOb (1.4.1)
WebTest (2.0.18)
wheel (0.24.0)
#

_Correctly running on system:_
Linux:
Fedora 22
4.0.4-301.fc22.x86_64

RF:
ride 1.4.1

Libs:
beautifulsoup4==4.4.0
cx-Oracle==5.2
decorator==4.0.2
docutils==0.12
ecdsa==0.13
JPype1==0.6.1
jsonpatch==1.11
jsonpointer==1.9
numpy==1.9.2
paramiko==1.15.2
pika==0.10.0
psycopg2==2.6.1
pycrypto==2.6.1
Pygments==2.0.2
rabbitLibrary==0.1
requests==2.7.0
robotframework==2.8.6
robotframework-cplibrary==0.9
robotframework-databaselibrary==0.6
robotframework-httplibrary==0.4.2
robotframework-jmxlibrary==0.4
robotframework-ride==1.4.1
robotframework-selenium2library==1.7.3
robotframework-sshlibrary==2.1.1
selenium==2.47.1
six==1.9.0
waitress==0.8.9
WebOb==1.4.1
WebTest==2.0.18
wheel==0.24.0
wxPython==2.8.12.0

Start by reproducing the SSHLibrary "Put Directory" case described in the issue on Windows 10 and Linux, using the shown source and target paths. Inspect the Put Directory implementation and its path handling, then verify that files are stored directly in /opt/callrec/data/pcap/ without recreating the source directories on both systems.

Written by the indexing model from the issue text.