Windows 10: Issue of joining windows domain presented on windows 10 and windows server 2016

Dear Windows community Team,

I am having trouble with windows 10 pro 64bits and windows server 2016.

I am having this issue where all machines running windows 10 and the servers running windows server 2016 are refusing to join the domain and the error which comes while trying to join the domain is "Network path was not found".


I did multiple change trying different machines running different build of windows 10 however no one of them has joined the domain.

The organization is running 7 domain controllers and also the forest and domain functional levels is windows 2008 R2.

One of the colleague has advised to go for windows 2012 for forest and domain functional level but I doubted on that because the lab I set up is running windows 2008 for forest and domain functional level and the machines running above OS are well joining the domain.


Kindly advise if any thing should be done for better operation.


Thanking you and Regards,

:)

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

Help setting up Hyper-V to test Windows Server 2016


In addition to the Hyper-V tutorial @essenbe mentioned above, here are a few more tutorial links for you:

• Windows Server 2016 - Setup Local Domain Controller Windows 10 Tutorials
• Join Windows 10 PC to a Domain Windows 10 Tutorials
• Remove Windows 10 PC from a Domain Windows 10 Tutorials

 

Windows 10 GPO Printer Add issues

A total shot in the dark since this is a very specific issue to our environment, but here it goes...

A little background on this issue, my school district is moving to windows 10. We partially deployed Windows 10 LTSB to some of the labs in the district. We are seeing sporadic issues with our Group Policies deploying printers. We have below 50% success rate with printers actually installing on the Windows 10 client machines.

Thinking it was an issue with LTSB, we downloaded and installed Windows 10 Education version 1709 on a test VM and joined it to the domain. I then applied GPO’s from 4 different servers. 3 Physical Server 2012 R2 servers and the original problem Server 2012 R2 VM Server.

What I found was the same inconsistency after rebooting the Win 10 Edu Test VM. I am getting the same Event 513. See below:





I am 100% sure the naming is right because I can manually add the same printer using the \\SERVER\FerLib path. All printers that fail to add have the Event 513. I am also going to post this on other forums.

We are only seeing this on student accounts which are domain guest accounts, meaning their profiles are non-permanent. We do not have the option to turn them into regular users per district policy. If you need more info that I omitted please let me know. We are getting desperate.

Thanks!