Imaging Laptops, System Config renaming machine to existing name and knocking off domain
Our current environment is SMP 7.1. We are currently having issues when imaging a laptop using initial deploy. Our defined computer range is 250-259 currently. Most of our systems were originally imaged with 6.9 instead of 7.1. When we image a system it will image and join to the domain but has a tendency to utilize a name which is already in existence and will knock the pre-existing system off of the domain. Has anyone else experienced this or know what needs to be done to address the issue. We need to get this solved as soon as possible. This only happens to our laptop images.