I know the theory says we dont want to install anything on the servers but..
For Net Folders back-ended by directly accessed active OES or Windows servers, an installed sync agent would provide better change response times and probably less performance hit and network traffic than the current sync method.

Comments

  • Agreed Mark. We have plans to investigate this.

  • Wow, I didn't think in this situation, but many problems can be avoided like: Performance, TCP ports (these agents can run on 443), credentials, etc.

  • Duplicate IDEA https://ideas.microfocus.com/MFI/novell-filr/Idea/Detail/12711

  • This isn't a duplicate of https://ideas.microfocus.com/MFI/novell-filr/Idea/Detail/12711

    This idea is to move the FAMTD and Java file scanning processes on to the file server. Which is moving an existing feature closer to the files to reduce network bandwidth. This would also require the File servers to be well specified with hardware as it is CPU and Memory intensive.

    The other idea is about a new feature, LIVE notification of file changes.

    You could however combine both of these ideas into one agent.

    I like both ideas. Reduceing network bandwith and also would make use of spare CPU capacity on our File servers.