![]() Maybe it’s something that will help you as well. I’d recommend switching to classic.Īll and all, it’s been a good choice for us. I personally like the old interface better, but maybe I’m getting old. If you accidentally delete something and you don’t realize it before it’s purged from the trash, you risk losing it for good.Īlso, they changed their web interface a year or so ago. Also, even though they have version control, which is a nice feature and a trash bin when you delete a file, you only have a certain amount of time before that file is purged from the trash bin. ![]() They have ramped up staffing on that, but we still have issues from time to time. First, we’ve had issues with their support in the past. ![]() It seems like many of those bugs have been worked out, but I’d still trust the ELC more than the OLC. We have a client running both, and they had lots of issues with the OLC on the Netgear, which is why they are running both. If you go this route, I recommend going with the ELC. Instead of installing the Personal Local Cloud on everyone’s machine, you can setup either their Office Local Cloud, which runs on a Netgear NAS, or you can set up the Enterprise Local Cloud, which is a VMware virtual machine. There are some nice features if you are in an office, which we don’t personally use. Since then, we’ve started using the mobile client on phones, tablets, etc, which all seem to work well. It’s been a few years, and it’s still working well. Now, we were able to work with our files like they were local, but the PLC software would keep the cloud updated and everyone else’s local copy updated. From there, you enter your login credentials and specify which folders you want to sync locally. Once the install is done, a web configuration interface opens up. This is a simple install where you’ll tell it where to store the local cache. Next, I had everyone download and install Egnyte‘s Personal Local Cloud software. From there, it was simple copy and paste. Then I simply used Egnyte’s drive mapping application on our file server to map a drive to Egnyte. When I migrated our file server, I simply setup the folder structure that we had on our file server on Egnyte. At that time, I couldn’t believe Egnyte was such an unknown because their solution was pretty damn impressive and extremely cost effective.įirst I’ll explain our setup and then quickly go over some of the other features that we don’t use. We looked at some of the bigger players at the time (Box, Dropbox, etc), and then we stumbled onto Egnyte. We also wanted the ability to share files easily and to have access from anywhere without VPN clients. We wanted our files quickly accessible while working on our day-to-day machines with no noticeable lag time as we dragged the files over our internet line. Constantly accessing files via VPN gets old pretty fast though. We had a site-to-site VPN setup between the office and the datacenter, and we had SSL VPN setup for remote users not in an office. Even the users in the office were virtual considering everything resided at a datacenter. I decided to write about this now, because a client was asking me about it.įor us, we didn’t need a typical file server. We migrated from Exchange to Google Apps, moved our ticketing system from in house to hosted, and moved our Windows file server to Egnyte. A few years ago, we decided to get rid of any server we could.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |