I have seen some of issues coming up where we cannot generate the configuration file because machine does not exist in database. Can anyone explain in what scenario can machine get deleted from safeboot database.
Also is there any criteria where machine has not sync with database for some duration and it gets deleted.
the only way is for some one (or a script) to delete it - assuming you are using online installs.
to confirm, get the machine ID from the recovery screen of the preboot, then go look that ID up in the database itself (using the usual mod 512 logic if you have more than 512 machines etc).
if the object directory is COMPLETELY missing (and you're sure you got the logic right), then some external factor deleted it. If the directory has .RMV then the machine is in the bin, if it's got a .WPE then someone (or script) did a permanent delete on it).
If the directory is there, has files in it, but does not appear in a group, then it's an orphan and you simply need to do a group scan from the groups menu to find it.
Group scan shows 0 machines and I have also checked in deleted machines and it does not show there also. I along with the other person are the admins and noone else has access to it and we both know that we have not deleted this machin..
I have posted a command to use on the database to find who deleted a machine from the DB previously. When a delete goes, it logs to the User performing it in their audit log.
Note: You'll need the Machine's Object ID - this dump of the User's audit will give you a listing of all Delete actions taken and the user associate with it but usually doesn't show the computer name anymore.