Windows 10 Pro and 2003 Domain Login

[lcoughey]

Let's preface with the fact that I have at least 6 Windows 10 Pro systems that work without issue.

We just replaced a 6 year old Acer laptop that was running Windows 10 Pro 32bit right up last week. But, the display stopped working and we figured it might be time to replace the unit. Bought another cheap Acer laptop, pre-installed with Windows 10 Home.

Forgetting that the old laptop was running 32 bit, went through the process of moving the SSD over to the new laptop and it was working fine, with the exception of the 32 bit and not accessing the 8GB of RAM. Knowing how easy it is to install a fresh copy of Windows 10, I did a complete fresh install on the system, thinking that I would be prompted to install pro, but it installed home.

No worries, just did the windows 10 pro upgrade via the Microsoft store. Joined the domain, added the user as an administrator, rebooted and bam! We get a message that the password is incorrect. Weird. Even went as far as resetting the password on the server, just to be sure we are using the correct password.

When I go to Computer Management, the Users and Groups snap-on isn't showing by default, which is odd, as it shows by default on all my other Windows 10 Pro systems.

So, I've re-installed Windows 10 several times, looking for a prompt for pro, but none has been given. I think I have figured that out, by entering the generic windows pro key, which matches the key that shows when I upgraded to pro via the store.

But, assuming that I will still have issues with the domain login issues, I thought I'd ask if anyone has encountered this and what was the solution? If it were a security setting on my server, I'd think that none of my windows 10 systems would work, though I must admit that the others were all upgrades from windows 7 pro or windows 8.1 pro.

Any suggestions?

 

[lcoughey]

Doh! Now, I'm not getting prompted for the license key during the boot process, which means every time I install, I get defaulted to home. Grrrr.

My next step may be to image a working copy of 10 pro from another system to this drive and deal with all the challenges that come with that.

 

[trevm999]

There's another thread somewhere here with the solution to this... but I don't remember what it was.

 

[trevm999]

NVM, if you're not getting prompted for a key, image might be the only way to go without doing an upgrade

 

[4ycr]

I had your problem, windows 10 automatically reads the key from the BIOS when installing so always installs home. I am sure I installed win 10 pro and imaged it across

 

[nlinecomputers]

There is no way to avoid installing Windows 10 home on that machine. You have to do the install and then change the product key. Using the product key you got from the Windows store will force an in place upgrade.

Upgrading the system should NOT cause any issue connecting to a server. Pro is Pro.

 

[lcoughey]

Anyone have suggestions on how to fix the issue with the domain authentication? I'm assuming that windows 10 is set to be more secure than windows 2003, by default. When upgrading earlier versions of windows pro, it probably just left the settings. Leave it to Microsoft to make something so simple turn into something much more complex.

 

[nlinecomputers]

Note if you are having connection problems disable the firewall. If that lets you join the domain then you need to reset the firewall to default. Domain problems are usually related to NetBIOS, DNS, or firewall issues.

 

[lcoughey]

Note if you are having connection problems disable the firewall. If that lets you join the domain then you need to reset the firewall to default. Domain problems are usually related to NetBIOS, DNS, or firewall issues.

Problem is, it lets me join the domain, but just won't allow domain users to login afterwards.

Before I joined the domain, I tested to see that I can connect to a domain share on the 2003 server with domain authentication.

 

[nlinecomputers]

Turn off ipv6

 

[trevm999]

Is the computer getting DNS settings via DHCP? Make sure your DHCP server only gives out your DCs as DNS servers, and make sure it also gives out the domain name.

Do you happen to have a Samba DC on your domain?

 

[lcoughey]

IP6 Off - did not fix it
changed to static IP with domain controller as only DNS - no dice

Plan F - install windows 7 pro 64 bit, join domian, upgrade to windows 10 pro

 

[nlinecomputers]

What do the server's logs say about each attempt?

 

[Porthos]

Image one of your 10 pro machines and put the image on this laptop. Win 10 is good at adjusting drivers and you can usually use SDI for the rest. Just change the computer name before connecting to server.

If 10 pro was activated already on that machine no problems.

 

[lcoughey]

Got it figured out with the help of http://www.askvg.com/fix-cant-select-windows-10-pro-edition-during-clean-installation/

After adding the ei.cfg file I created to the install thumb drive sources folder, it prompted for the version to install, chose Windows 10 Pro 64 and installed a fresh copy. Joined the domain and worked fine right away.

 

[nlinecomputers]

That is great but I would sure like to know what the upgrade is futzing up. It should work without a clean install.

 

[lcoughey]

That is great but I would sure like to know what the upgrade is futzing up. It should work without a clean install.

Agreed...but, 24 hours to setup a new Windows 10 system on my network is enough time wasted for me today.