Hello Rayman1980,
By best practice there should be different mechanisms to avoid duplicate hostnames. This includes:
- Do not run parallel deployment for same environment
- Use differential hostname topology: by site, by department, by type of user, by type of computer
Unfortunately, WDS will not provide a mechanism to avoid duplicate hostnames in this case.
Another option to clean up the hostnames in case of refurbishing and avoid GUID duplication too, would be to run the next script before proceeding to a deployment, ensuring that there will be no duplicates to start with:
Get-ADComputer -Filter {NetbootGUID -like "*"} -Properties Created | ? {$_.Created -le ((get-date).addDays(-5))} | Set-ADComputer -clear NetbootGUID
------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept as answer--