Urgent help - 2012 R2 connecting to Windows 10

[ShivP]

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?

 

[#Chri5#]

Are you trying to join the Windows 10 PCs to the AD Domain or something else?

 

[ShivP]

Are you trying to join the Windows 10 PCs to the AD Domain or something else?

Yeah to the log on domain etc

 

[Throrik]

Are they on the same LAN with a route to the Domain Controller? What error are you getting? Not sure what you mean by

 

[Ploppy2k3]

make sure the DNS is pointing to the IP of the DC and you are all on the same subnet.

 

[ShivP]

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.

 

[PiKe]

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.

Takes ages, don't reset it.

 

[PiKe]

Forum went slow, double post!

 

[ShivP]

Takes ages, don't reset it.

OK I won't!
Stuck at 31% atm. I would have done it earlier but as it is in place upgrade I am scared what it might do!!

 

[ShivP]

Still stuck at 31%.....

 

[ShivP]

Takes ages, don't reset it.

It went to 40%.... then said something like "Windows cannot upgrade certain components of the previous installation"

now it is restoring the previous version
ARGH!!!

 

[ShivP]

 

[PiKe]

Clean install?

 

[ShivP]

Clean install?

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?

 

[Throrik]

Is this your only Domain Controller?

 

[ShivP]

Is this your only Domain Controller?

Yes correct
Is only a small business with around 5 machines so it's effectively a desktop computer with windows server running on it, used for file share and log on server

 

[PiKe]

Just redo the domain if you only have 5 machines.

 

[ShivP]

Will do
Apologies for all this... I am definitely a server noob and struggle with all the terminology etc...

 

[nightmare99]

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]

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]

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

 

[ShivP]

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

I found the updated client connector. It didn't work

 

[nightmare99]

I found the updated client connector. It didn't work

Then I would have gone for manual join personally.

 

[ShivP]

Then I would have gone for manual join personally.

Manual join as in through my computer/this PC? Didn't work either

The server 2012 instance is still running, so I am happy to try any other steps you can recommend...

 

[ShivP]

Manual join as in through my computer/this PC? Didn't work either

The server 2012 instance is still running, so I am happy to try any other steps you can recommend...

 

[Toughnoodle]

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.