I ended up rebuilding it a third time with their senior engineer who found an obscure GPO which was preventing the domain join from happening. Neither of them could figure out what was going on and in the end, their advice was rebuilding the VM from scratch. I’ve already sunk six hours in to building the VM, mostly on the phone with their Level 1 and Level 2 support guys trying to get the VM to join to the domain. I am now building our second customer-facing deployment and it isn’t going well either.
EGNYTE DESKTOP SYNC FOR PC WINDOWS
I spent about 30 hours over a weekend merging the three sets of data back together for the rollback (old on-prem Windows share, on-prem Egnyte share, cloud Egnyte) and it sucked badly. That client has millions of files and it was a 700GB set of files.
![egnyte desktop sync for pc egnyte desktop sync for pc](https://helpdesk.egnyte.com/hc/article_attachments/360013821151/DS_menu_options_windows.png)
It refused to remain a member of the domain, time wouldn’t stay synced, storage sync didn’t work, the web management portal was broken, the VM locked up, refused to boot, and finally the file system went senile and we just turned it off. The entire file system ended up becoming hosed and we had to roll back out of Egnyte completely because it was unusably damaged. Quite a bit of that was the fault of the engineer who deployed the product without much common sense, but the Egnyte VM was also extremely unstable.
![egnyte desktop sync for pc egnyte desktop sync for pc](https://helpdesk.egnyte.com/hc/article_attachments/360013456472/DS_windows_confirm.png)
Our internal deployment works well enough (minus the annoying lack of WebDAV authentication persistence), but our first client deployment was an absolute catastrophe that caused us to lose that client. I’ve had a pretty bad experience with Egnyte so far.