Mark Litin
asked on
After Windows 10 Home to Pro upgrade, cannot join domain. Receive error "The specified domain either does not exist or could not be contacted.
A client purchased a number of PCs for their business with Windows 10 Home, but require Pro because they're on a domain (Hanson1.local)
They have a server running Server 2012 Essentials also as the DC with 12 active users.
After upgrading one of the PCs to Pro through the settings/activation app without a hitch, I rebooted and confirmed the PC was in fact Pro. I have confirmed the SysvolReady flag was 1 and turned it off and then back on on the server, and IPV6 was turned off on client machine. The PC is listed in users and computers.
Nothing i have done has allowed this PC to connect to the domain.
Any ideas?
Thanks much for any info you can offer.
Mark
They have a server running Server 2012 Essentials also as the DC with 12 active users.
After upgrading one of the PCs to Pro through the settings/activation app without a hitch, I rebooted and confirmed the PC was in fact Pro. I have confirmed the SysvolReady flag was 1 and turned it off and then back on on the server, and IPV6 was turned off on client machine. The PC is listed in users and computers.
Nothing i have done has allowed this PC to connect to the domain.
Any ideas?
Thanks much for any info you can offer.
Mark
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Good points! Thanks. I will first point directly to the server, and then reinstall if that does not work.
Cheers!
Cheers!
I have found Windows 10 Repair Install via Media Creation Link to be highly successful. Good luck.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It's somewhat off-topic, but I'm curious about the comments about not disabling IPv6 on workstations. What sorts of issues can one expect with that? I've not run into them. Why isn't a properly-functioning IPv4 adequate?
It's 2016. IPv6 has worked properly since XP SP3. Server 2008 R2 and newer use IPv6 when ever possible instead of IPv4. Why disable something that woks because it was a solution that sometimes solved problems with XP SP2.
That being said if disabling it has to be done in the registry, not the NIC configuration.
That being said if disabling it has to be done in the registry, not the NIC configuration.
Nope it is 2017, but I support the rest of your comment
Thanks Shaun, I stand corrected :-)
@mlitin: This was a upgrade from Home to Pro and such upgrades can and do go wrong. Did you try the repair install? Your issue may not have anything to do with IPv6 or DNS.
ASKER
Hi All
The issue was that DNS was not pointed to the server. Once it was, it sailed through.
Thanks all for your input. Nice responses from all.
The issue was that DNS was not pointed to the server. Once it was, it sailed through.
Thanks all for your input. Nice responses from all.
Thank you for the update.
Go to the Media Creation Link
https://www.microsoft.com/en-us/software-download/windows10
Click on Upgrade to Windows 10 (even if Windows 10 is running), click on the Download button, select Open (Run) but NOT Save. Allow the program to run. Allow drivers to update. Then select Keep Everything.
This always works for me and I never lose anything. But since the upgrade did not go well, back up first.