Thanks @just Unfortunately, that’s part of the issue. If I could just put it up somewhere and set and forget I would, but the data we want to share with various groups is sorta sensitive so that model is not an option.
The competitor name isn’t as important as they seem better geared towards taking enterprise money from someone that has to jump through some hoops to generate a check or wire transfer and make the justification (see my first post, every enterprise has different rules, these are my company’s not mine)
Agree it would be nice to have someone help out, It does take some chops and troubleshooting to get up an running, but I did.
Jumping off that thought:
Implementation challenges and why support is desirable (not flaming, commenting)
The feature set shared and unique between GUI and occ console/cli and config.php can be a bit challenging unless you really dig to see what they do and what you want to do.
Locking down sharing in multiple places maybe could be easier (have to explore still if workflows will block WebDav clients… (and I have seen the discussions, they don’t hold up well when you would rather not make it easy to have copies of everything everywhere, bad actors zipping and downloading and logged as such right before their quit date aside).
the LDAP dropdown for folder to AD mapping could be better, doesn’t seem to show everything (missing groups, know there are threads out there), sorted by type and alpha would be nice, but the json cli remote file mapping to sftp shares works well enough after you figure it out that it is there.
The AD integration is somewhat confusing at first glance, but workable.
Wish there was more application hardening information, found info here in the forum and docs for that and to move the data dir, but occ in the web dir makes me nervous… that php/apache/sql hardening is common practices and referenced like that makes sense.
Skipping the cron.php and sticking to occ I think for traditional cron so others can lend a hand I think–TBD
They are all beasts to configure, but ongoing operational ease is important–this upgrades really cleanly so far compared to a couple of others things I have used.
Oh yeah, DUO integration challenge up next after I demo it internally.
Our use case?
We need non-collaborative software that allows us to add authentication and authorization and auditing to various shares/mapings to shared remote storage controlled by a vendor… what else is new? lol.