destination

  • 01 Nov

    Added SharePoint as Destination in Limagito File Mover

    In version v2020.11.1 we added SharePoint as Destination in Limagito File Mover. In the next couple of weeks we’ll add SharePoint as Source. Special thanks to Brad who helped us with the test account, much appreciated.

    Limagito File Mover SharePoint as Destination

    SharePoint Destination Setup:

    We currently provide 2 authentication methods so we realize that there may be cases where your situation is such that it does not work.

    • Online Authentication Method:
      • Is the one we used during our tests. The end result of authentication is to establish an HTTP cookie, named “SPOIDCRL”, that contains a binary security token to be sent in subsequent SharePoint HTTPS requests. This cookie is kept in memory (not saved to disk).
    • NTLM Authentication Method (Windows classic mode authentication):
      • For example, imagine our SharePoint endpoint is ‘https://xyzoffice.mycompany.com/’
        • The Site Url would be: https://xyzoffice.mycompany.com
        • The NTLM Domain would be: mycompany.com
        • The Username would be just the name, not a full email address. For example: myname instead of myname@mycompany.com.

    Limagito File Mover SharePoint Setup

    SharePoint RunTime Log result:

    Limagito File Mover SharePoint RunTime Log

    If you need any help with ‘SharePoint as Destination’, please let us know.

    Best Regards,

    Limagito Team

  • 29 Apr

    Q&A 3: Is there a way to retry to only the failed destination when using multiple destinations?

    Q: I’m using LimagitoX File Mover and find that if a rule has multiple destinations and only one of the destinations fails it retries all of the destinations. Is there a way to retry to only the failed destination? Or another way to work around this?

    A: Yes, please open ‘Function Setup’ and enable the ‘Destination Memory’ option.

    If you need help, please let us know.

    Regards,

    Limagito Team

  • 15 Sep

    Moving file to multiple destinations

    We got the following question recently:

    hello, i am currently running 10.206.20.0. i have a rule that move file to an external ftp destination and also a unc path. if the ftp destination is not available the rule fails to move the file to it but keeps trying to send to the unc path. these means that the same file is sent many times to the unc destination. this keeps happening until the ftp site come back. is there a way to configure the rule to stop this behaviour? thanks robert

    Our reply: Please enable ‘Destination Memory’ in your Function Setup.

    DestinationMemory

    This option will solve the issue because our file mover will remember which destination failed and will not move the file to the destination(s) that was(were) successful.

     

    The feedback afterwards from robert was even better.

    thanks very much, another option i didn’t know about. :-}
    love the product
    robert