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?
 
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.
 
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...
 
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
 
Toughnoodle said:
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.
Click to expand...

I feel so thick.... checking the DNS it was not pointing to the server. I have just connected it to the domain succesfully... what a clown

Well I have the 2016 license now, so I guess I will have to reinstall at some point but it is not as urgent now
 
Toughnoodle said:
Good stuff. DNS underpins Active Directory. For instance, it's how the PCs find an AD domain controller to log in.

Your PCs shouldn't have any other DNS servers set (e.g. don't have external DNS servers that don't hold info about your AD domain). Also, you should be using DHCP on the domain controller to give out IPs on the network along with the options (e.g. IP of the default gateway, DNS server and DNS suffix aka long name of your AD domain).
Click to expand...
OK - what about other stuff like Hikvision NVR and other devices, how do they get their IP addresses? Do I need to disable DHCP on the router?

I am having another side-issue with 2012 R2 on folder redirection. This was set up, however it seems to have just fallen over and not be working anymore especially on the new Win10 machines which just seem to be using their C drive as normal

UfBZWyF.png


T2FVjZh.png


There is a seperate GPO thing set up for it... and all is set up correctly as far as I can see

Anyone got any ideas?
Thanks
 
You must log in or register to reply here.
Back
Top Bottom