Urgent help - 2012 R2 connecting to Windows 10

ShivP

ShivP

ShivP

Soldato
Soldato
Joined
26 Oct 2013
Posts
9,977
Location
Leicester
Hi guys

I am really struggling with 2x server 2012 r2 to connect to Windows 10 client computers on the domain.
The Web based client connector does not work and states it only works up to win 8.
The documentation I can see says that win10 Pro should be supported.

Any help please?
 
Are they on the same LAN with a route to the Domain Controller? What error are you getting? Not sure what you mean by
 
I just gave up and decided to do 2016 Server Essentiasl in-place upgrade. It's doing it now - stuck on Working on updates but I am still hopeful. I will give it 30 mins and then force reset it.
 
ShivP said:
I just gave up and decided to do 2016 Server Essentiasl in-place upgrade. It's doing it now - stuck on Working on updates but I am still hopeful. I will give it 30 mins and then force reset it.
Click to expand...
Takes ages, don't reset it.
 
xb3Kx3s.png
 
PiKe said:
Clean install?
Click to expand...
Yep. Tried it 5 times using various Google "fixes" which simply didn't work. I am going to have to get in a fresh install and re set everything up again.
Is there any recommended way I can do this to avoid redoing the domain and reconnecting the workstation computers to the new domain and log on server?
 
Will do
Apologies for all this... I am definitely a server noob and struggle with all the terminology etc...
 
There was an updated client connector for Windows 10 support and failing that you could have manually joined them to the domain. This seems like it got a little extreme just to get a couple of workstations connected.

If you are rebuilding the domain you will probably want this to migrate your user profiles on the client machines https://www.forensit.com/downloads.html
 
There was an updated client connector for Windows 10 support and failing that you could have manually joined them to the domain. This seems like it got a little extreme just to get a couple of workstations connected.

If you are rebuilding the domain you will probably want this to migrate your user profiles on the client machines https://www.forensit.com/downloads.html
 
There was an updated client connector for Windows 10 support and failing that you could have manually joined them to the domain. This seems like it got a little extreme just to get a couple of workstations connected.

If you are rebuilding the domain you will probably want this to migrate your user profiles on the client machines https://www.forensit.com/downloads.html
 
nightmare99 said:
There was an updated client connector for Windows 10 support and failing that you could have manually joined them to the domain. This seems like it got a little extreme just to get a couple of workstations connected.

If you are rebuilding the domain you will probably want this to migrate your user profiles on the client machines https://www.forensit.com/downloads.html
Click to expand...
I found the updated client connector. It didn't work
 
Long shot, but make sure the "DNS Client" service is set to Automatic and is started on the PC. Also, as Throrik says, make sure the primary DNS of the network card is set to the IP of your "server".

I always do the manual domain join via "This PC, properties, etc.". Make sure your PCs are running the Pro version.

I can't remember the last time I did an in-place upgrade (if ever!). I always migrate to new hardware when I'm updating the server OS. You would attach the new domain controller to the domain and copy the Active Directory data as part of the migration.
 
You must log in or register to reply here.
Back
Top Bottom