I found this thread as we searched for a reason why restore does not work. When you try to restore from client, you see a list of all the backup folders by date/time, but when you go into those folders you see only the desktop.ini and Default user folder, nothing else. The actual user folder is not shown, so you can’t restore any data. If you log in as admin via the web, you can go in to the backups and see everything.
Based on this thread, I added the user account with read/execute/list to the root client folder on the server (Windows 2012R2) and we tried again to restore on the client (Windows 7 Ent) logged in to the workstation as the account that has been given permission on the server. No change.
What makes no sense based on the above is that one file and one empty folder show up for restore, but everything else does not. Permissions on all items are identical, so either everything should be listed, or nothing should be listed. It appears there is some other factor at work here that identifies who is trying to restore and if they are allowed to see the data.
The end need is for users (they do not have admin on their machines, we install the software and configure the backup rules, and they do not have user accounts in URBackup) to be able to backup on demand (works) and restore on demand (not working) from the client icon. Can the software do this? At the moment we do have a user account made that matches the domain account the user is logged in with, but this seems pointless as there is no link between URBackup and the domain. Or, is that the issue, and this won’t work until such time as LDAP is implemented, and until then only an admin can restore data?