I configured up the Dude server with admin user account having full access on my office PC.
I went home and installed The Dude client, and connected remotely to my office PC’s Dude Server. Worked perfectly.
Whilst at home I created a user called super, and set the access to full.
I then logged in at home as user account super, I had full access.
I then changed the admin user account to the read only group.
Came back into the office, everything was working fine. I then rebooted my office PC and now I am stuck.
There is no super user account, and the admin account is in the read only group!
Well, long story short I reinstalled The Dude and imported in a backup that I “luckily” made before I rebooted the PC so everything is back up and running.
Everything is now running correctly, but beware of config changes made on a remotely connected client not being saved on the Dude Server when rebooting.
Yes that seems correct. As well, dont count on the Backup (XML export) that you run from the client. You will notice it is not the same size as a backup run on the server. Thats another cold sweat surprise you dont want. Glad I regularly backup installation, but long ago learned, do it on the server. I guess in a way it makes sense. Server backs up server, client backs up ‘on the client’ data.
Good practice to have those ‘recovery points’, but thought I would mention that, since I had a cold sweat moment restoring a client based backup. “Where did everything go!!!” Only happened once! Good luck.