What needs improvement with Fortra's GoAnywhere MFT?

I am not able to go in and say 'forgot password.' I need to access the admin portal to change the password from there. I would like to be able to do MFA and reset the password via email.

The biggest weakness I have seen in the product is scheduling. It is very limited in that aspect. It needs more flexibility and more ways to schedule. It is very strict with no customization options. The monitors are limited in how you can set them up. Handling errors is challenging as errors are hard to understand. The help guide does not cover error messages well. It is Java-based, so it is hard to understand Java error messages.

On the platform side, I would like to see some improvements in the dashboarding and telemetry data. We take a lot of that data today, and we end up writing some custom dashboards so that we can run the day to day operations. We are sending and receiving millions of dollars a day, and for us, the dashboards are a bit lacking. It works great if you have one job that needs to run successfully. However, depending on how you build it, there may be dependencies that fail, and you may need to do certain alerting to teams and things of that nature. What we are looking at right now is potentially rebuilding our dashboard a second time to improve it a little bit further based on the operations of the team. We would love to see some improvements there. That is one area where they could improve. Everything else is the best of the business from what I have seen.

For what we are using it for, it is doing the job, so I would not be able to say how to improve it. For us, it is perfect. It is a good solution that we are using, and we are going to continue to do so. However, it should be advertised more as a solution. I did not see it out there beforehand.

I tried to copy a file from an S3 bucket to another storage class. I don't know if it is a limitation from AWS, not the MFT. If I copy a file from the AWS S3 bucket to that storage class, it can't be transferred. It says that I can't remember the exact error, but it cannot be processed. I want MFT to be more compatible with cloud-based applications or services like AWS.

The reporting could be more customizable.

The technical support has room for improvement. It takes between three to five days to get a resolution from them. I would like better integration between GoAnywhere MFT and other MFT solutions. We request the ability to customize the user interface of Fortra's GoAnywhere MFT, specifically by incorporating our company logo. This feature would provide greater flexibility and brand recognition within the software.

My only technical difficulty has been finding certificates nearing expiration. While this suggests room for improvement in certificate management, it's more likely I just need to consult the documentation. Upgrading was a challenge and I ran into some problems along the way.

Fortra needs to offer more use cases for GoAnywhere MFT during training.

In some cases, the logs need deeper information. In terms of communication and checking, they need to go a little deeper. In some scenarios, when you are in a cluster environment, the load-balancing capabilities of the gateway need to be improved a little. This functionality needs some improvement. In general, workflow features are good, but when you need to use the transformation capabilities, there are some problems in terms of the way they manage the resources of the machine. There are some limitations in the size of the file, so the transformation capability has to be improved.

I want to be able to use GoAnywhere to create customizable reports that I can share with the MSP containing any information related to file transfers.

The solution's support for the Unix platform and AS2 should be improved. The solution's scalability needs to be improved as it has very limited scalability. The solution could include some multi-factor authentication (MFA), one-time password, or secondary authentication.

The security features must be updated regularly. The newer versions must be released sooner. The solution must add new features at least every year. The solution must provide integration with SSO.

The security could be upgraded to address novel cyberattacks. I'm not sure whether the product's security is being updated periodically.

I'm on the admin side of it, and one of the complaints is that it times out too quickly for the people who are using the internet-based part of it. It could be that there is a way to do it, but I just don't know how. One of the things that I wish is to not necessarily have to set up a username and password for people with whom we don't frequently share files. For instance, if I want to share files with a patient who is not somebody with whom we share files all the time, I would like them to somehow verify who they are and be able to push the file to them. I shouldn’t have to set them up as a user with a password. It should be almost like Dropbox.

Pretty much everything we've needed to connect to has been done fairly seamlessly. The only issue I've had with connectivity, database or otherwise, revolved around an SSH key. I tried to create a key, but it was incompatible with a vendor's SFTP. And when that vendor has tried to create a key and share it with me, I have not been unable to import it into GoAnywhere. I had to use a third-party app to create the key and find something that was mutually compatible. I've submitted tickets on that to GAMFT for consideration. They could possibly improve the error handling on jobs. Whenever it generates error logs, sometimes the error is very generic. It takes a little work to diagnose what's really going on. It may just say "IO Exception" and that doesn't really tell you much.

They need to increase the number of Cloud Connectors and speed up their development of them. Also, there are a number of built-in tasks in GoAnywhere. One, in particular, the write to CSV task, is slow. If you have, say, 100,000 records in your row set and you want to write them to a CSV file, it takes a long time. That definitely requires performance improvement.

Apart from ICAP, it will be more efficient in terms of marketing if a native integration opportunity can be provided with DLP solutions currently used by customers.

There's one persnickety issue about NAS permissions. That is a problem we have run into with GoAnywhere. I would like to see more focus on compatibility with/enforcement of user roles and access permissions across NAS, among other things. We have filed a couple of tickets on that in the past.

GoAnywhere's interface could be a little more intuitive. It can be hard to grasp at first, but once you have a decent understanding, it's pretty straightforward.

When it comes to GoAnywhere's workflow features, there are a couple of areas where I'd like to get a little more consistency. The two aspects of scheduling that we use are scheduled jobs and monitors. And there's cross-capability between the two. We've done some philosophical thinking about when a function should be handled by a monitor and when it should be handled by a scheduled job. When a monitor invokes a project to accomplish something, that gets logged as a job. I've had a little difficulty figuring out where to look to see the monitor's activities itself, to see if the monitor is having a problem. For instance, if an account on a secure FTP server has expired, the monitor that uses that account doesn't announce to us that it's having a problem. I want to work with them on this to get it fixed. Another aspect would be greater visibility into exactly what's happening. But part of that is because we haven't learned how to look at it. I still need to establish some training for my people who support this. We've learned a lot and done a lot with the documentation, which is pretty good, but some formal training would really help tie together a lot of the little tidbits of knowledge in our heads.

It doesn't need much improvement, other than tiny idiosyncrasies. I've run into one or two things for which I've put in change requests to the software developers at GoAnywhere, but they are very minor things, the types of things that don't come up much. We've created in the neighborhood of 80 to 90 projects in GoAnywhere and, out of all of those, there have only been a couple where we've run into something and that made us say, "I wish they could improve this little thing here." For example, when it comes to interacting with files, there is a function referred to as write CSV, to write a general text file. In this scenario of creating a simple text file, I ran into a situation where, if the product saw a quote or a double-quote in the data, it started wrapping all the text fields in double-quotes. The request I put in asks them to provide a feature that leaves my data alone and does not interpret anything. If I don't want double quotes, please don't put them in. It should have the option, on certain write CSV operations, of not inferring anything.

There's not a lot of improvement I can think of. Maybe in the tools section, there is a SQL Wizard which works really well. I think that the SQL Wizard could use some improvement- it's little slow when moving from page to page.

Its user interface can be improved. The current user interface is a little basic for some of the use cases. We have to use an external component to enhance it. When we need a more appealing user interface, we use an additional component, and that works okay.

Until now, I think the solution very good for me and my clients. If I had to name one thing that I think should be improved, I think it is that there are quite a lot of features and we do not use all of them. So a thing that could be done to improve this situation is maybe for HelpSystems to offer a lite version that also costs a bit less.

I think that this product has most of the features we require, although the license is expensive. DNS support needs attention. If the hostname has a dash in it then it does not work. Without a dash being included, it works fine. This is something that needs to updated in the next release. The shared mailbox support for OWA in the cloud needs to be improved. The shared mailbox does not have a password, and we cannot use it. If there is a password for it then it works well. if you have host name with example aaa-fgju than in web user ip filter list the name aaa-fgju will not work. If you have host name fghhg1 then it will work. The agent is good feature but license is bit expensive.

In using this product, I have not found many areas of the product or service that need to be completely improved. However, with any product, improvement of a service or product can always be reviewed. If one were to look to improve it: * Continue to look forward and listen to its customers. * Improvement in support or product relies on being ingenious, supportive, and listening to its customer base.