This question has a few elements to it so I'll try to describe the problem concisely. I'll explain why I did what I did last Friday and maybe someone will have an idea how to solve it or a better solution.
Local dentist was hacked last month. Easily broken passwords is my guess. Dozens of new user accounts were created but we disabled them. Fearing issues with active directory, I recommended we create an entirely new domain setup. My plan was to get the new network running then connect all the computers even as the old server was still running and operation, so I could connect the computers quickly after work without interruptions for them.
There is a bit of a time issue, I need to do this once they stop working on noon Friday while their dentist management software Dentech is still available for tech support, as they need to do a few things on their end during the installation. Users need local admin rights for the software.
Last Friday happened. New SBS 2011 server had arrived on time and I went to work. Everything is going smoothly and I begin connecting computers to the new domain. That was the plan anyway. The first computer I tried connecting with the "server connector" (consists of going to the server name in a browser with a /connect after to dl software) and I repeatedly get the error "cannot connect to the network. an unexpected error has occured" after the connector has been running a few minutes.
I troubleshooted this feverishly, knowing the deadline marched closer. I did basically everything I could google.
Any idea what was going on? Would a normal migration be better? I'd say yes but I'm leery because of potential AD issues.
This is a unique situation. If I had to guess I would say that there are dhcp issues somewhere. I'm creating a new network alongside a current one. The old server was 2k3. I think it might have had a dhcp role, but I'm not sure if I should do something about it since I'm creating a new network. Thanks for your time.