Over the past several months I have observed that Dropbox periodically “forgets its identity” on cloud VMs, probably because of changing hardware signatures. I told them about this:
William Gross, Aug 14 04:34 AM:
For the past several months I’ve been running the Dropbox Windows client on Amazon EC2 and Microsoft Azure virtual machines. Sometimes, when I shut down and later restart one of these, Dropbox “forgets its identity” and asks me to log in again. After I do this, I get an email saying I’ve linked a “new” computer to my Dropbox account, and when I look at my account page (security tab), I see the VM’s computer name listed twice (once from before the restart and once from after). This is a bit annoying, but the major problem is that sometimes files that I’ve deleted while the VM was shut down end up reappearing in my Dropbox after the VM restarts and I log in again.
I suspect this problem has something to do with the “hardware signatures” of these VMs changing across restarts. Is there any way I can configure the Dropbox Windows client to keep the same computer identity even if a machine’s hardware signature changes?
Dropbox support told me they have no plans to address this:
Thanks for your e-mail. Sorry to hear about the difficulty you’ve been experiencing when running Dropbox on VMware. Unfortunately, if the machine’s hardware signature continuously changes, Dropbox will recognize this as a different device and therefore register this as a new linked computer. At this time, there’s not a workaround for this.
Disappointing. Does anybody know if any of the other file-sync services (OneDrive, Google Drive, etc.) have a solution for this?