Imperva Cyber Community

Hi all,

I have a question about the configuration of Remote Directory for Windows Server FTP.

End customer have a Windows Server 2012R2 as FTP Server without any FTP Software running apparently. They have a DAM of other vendor configuring "/" in remote directory. Their IT department created another partition in Windows Server for Imperva DAM, but when we configure Remote Directory with "/" in FTP Action Set of Imperva DAM, how do we know that archiving data will send it to tha new partition?



#DatabaseActivityMonitoring

------------------------------
Jesus Sandro Mitma Ancari
Head of Presales - Cybersecurity Deparment
Think Networks
Lima
------------------------------

Hi Jesus,

This falls out of scope for Imperva Support as this pertains windows FTP.

But best way to test is to send one file and see where it shows up.

FYI: All paths are relative between the client and server, if FTP is configured to G: as base path where all files get stored, that is "root" from a client's perspective. The client just is not aware that its on G: . A file uploaded on root / will be under G:

As long as the FTP server has switched its base path to (if that is what it would be called in windows FTP) G:, you should be fine.

Regards.

------------------------------
Sarvesh Lad
Tech Lead @ On-Prem Managed Services (WAF, DAM, DRA & Sonar)
------------------------------