G
gwagn
I was assigned migrating our office (10 Clients) from an old SBS 2008 to a new Server running "Windows Server 2016 Standard". In that process I am stuck a little with connecting Clients to the new server (using the "Client Connector for Windows Server Essentials" (after cutting the pre-ecisting connection to the legacy SBS 2008).
All problematic Computers are members of the our local domain domain (both Servers currently having a AD DC role). And I am wondering whether I really have to fix this before moving on with the migration (moving the shared Data is my next bullet point).
Some questions in that regard:
I am completely new to Windows Server and only have a litle background in Linux, but things like managing a domain controller and Windows Server in general are pretty unknown territory, so please bear that in mind in case my question seem too basic, borderline dumb. I am actually dumb in this field but still need to get this over with
Continue reading...
All problematic Computers are members of the our local domain domain (both Servers currently having a AD DC role). And I am wondering whether I really have to fix this before moving on with the migration (moving the shared Data is my next bullet point).
Some questions in that regard:
- What is the benefit of connecting the Computer to the server (which seems to create a Computer account on that Server) is there beyond being a domain member?
- Can I move on and solve this issue at a later point in time or will anything bad happen if I skip the connection process for some Computers?
I am completely new to Windows Server and only have a litle background in Linux, but things like managing a domain controller and Windows Server in general are pretty unknown territory, so please bear that in mind in case my question seem too basic, borderline dumb. I am actually dumb in this field but still need to get this over with
Continue reading...