For more context - we utilize MDT for windows deployment. MDT runs task sequence, basically install OS, install microsoft office, runs updates, then installs sentinel one agent and then couple scripts at the end. No fat/golden image or anything - pretty basic stuff.

SentinelAgent installs this way:

SentinelOneInstaller_windows_64bit_v24_2_3_471.exe -a "WSC=true" -t "token_goes_here" --qn

Every time my helpdesk reimages laptop we got, say, entry BobLaptop in management console. If windows deployment doesn't finish successfully - helpdesk needs to restart it - and we got second entry BobLaptop. If tomorrow Bob decides to force shutdown laptop during nighttime windows updates - windows may brick itself, thus the need to reinstall windows again - we got 3rd entry BobLaptop in management console. And so on.

All of that times 800 employees. As you can imagine it's a giant mess.

How do you avoid this situation from happening without manual intervention? Maybe some parameter for installer exists to reuse agents or something? Or any other approach?

Of course I can and I occasionally do manually log into management console and right click > decommission on old entries - otherwise we run out of licenses. But it's a pretty lengthy and tedious process where I have to find and decommission 50+ duplicates monthly. Other approach would be to get involved in each and every windows deployment and decommission 1 by 1 at the time of deployment. Which Is what I really want to avoid as it converts pretty highly automated process done by 1 employee (helpdesk) to now relying on manual intervention of me (2nd employee) - and I obviously will not give helpdesk access to management console.

Looking for advice how do you approach that issue. Or maybe some steps you do to avoid it from happening in the first place. Thank you.