I set up multiple terminal servers by exporting and importing a machine I built after joining it to the domain and installing the necessary applications. I thought generating a new ID during import would suffice, so I changed the hostname and IP for each server. Initially, everything seemed fine, but now I'm facing login issues due to SID conflicts. I realize now that I forgot to run Sysprep before cloning, which could be the cause. I've tried taking one server, removing it from the domain, running Sysprep, and using that as a new base image, but that hasn't worked well since local accounts break when I clone. I'm contemplating whether I should rebuild the servers from scratch. Any suggestions on how to fix this or best practices for a clean setup in the future?
5 Answers
I suggest removing one server from the collection and the deployment. Once that's done, you can run Sysprep on it. But honestly, I'd still recommend building a whole new image to avoid future issues.
Honestly, starting with a clean build might be the easiest route. You'll want to create a proper reference image, sysprep it before joining the domain, take a snapshot, and then clone from there. Trying to fix the SID conflicts on your current servers is likely to cause more headaches than just starting fresh.
Some might suggest ditching Hyper-V altogether for a better setup. If you're serious about doing it right, there might be more efficient ways to handle this.
If you run Sysprep on each current server, it should eliminate the SID conflicts and recreate them, but I haven't personally used Sysprep on a server before. Still, starting completely over with a Sysprep image seems like the better option.
Rebuilding with Sysprep is definitely going to save you a lot of trouble instead of trying to fix those SID conflicts now.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures