Urbackup and sysprep

It seems that urbackup does not really play nice with sysprep.

  • installed a machine, among other software, urbackup
  • ran sysprep and cloned the machine to two others
  • started the first machine, lets say, named DESKTOP-3FFFFF it appeared in urbackup-server ok, made backup ok
  • started the second machine, lets say, named DESKTOP-3DDDDD and it seems that the server presumed it was renamed DESKTOP-3FFFFF and renamed the server entry.

How to totally zero out the client side configuration if sysprep does not do it so that the server discovers it as a new client?

It’s based on clientuid_ in the misc table in “C:\Program Files\UrBackup\urbackup\backup_client.db”.
Deleting/changing that would “fix” it, or I guess you could just delete "C:\Program Files\UrBackup\urbackup\backup_client.db*" during sysprep (stop urbackupclientbackend service beforehand).


net stop urbackupclientbackend
del "C:\Program Files\UrBackup\urbackup\backup_client.db*"

during sysprep seemed to do the trick.