Windows Server 2012 Essentials UR3 coming soon, will it finally include a DNS fix (for skipped domain join clients)?

[tinkererguy 22]

You may recall this popular thread:

Remote WS2012e client PCs (that skipped domain join during install) can't surf after Update Rollup 2, here's the fix

 

It appears the wait for a fix may soon be over! Listen to SBSDiva's latest podcast to hear the full scoop on what's coming in UR3, as well as in the major new R2 release!

http://homeservershow.com/essentials-2012-r2-ur3-with-the-sbsdiva-chromebook-on-home-server-show-234.html

 

Great episode there, David McCabe and Susan Bradley!

 

I also wrote up a quick summary here. Curious if others are looking forward to UR3, or just ready to move straight to R2, particularly if you're blessed with MSDN.

[Jason 51]

Been working with MS Sr Engineer on their DirectAccess team for 3 weeks to resolve a DA issue. They insist it won't require a reinstall but rather are using my unique scenario to gather data on something they've not seen before.

 

Robert Pearman (Titlerequired.com) has already confirmed same issue was resolved by an OS reinstall. If so, I may just use this opp to upgrade to R2 instead.

[tinkererguy 22]

... or just ready to move straight to R2, particularly if you're blessed with MSDN.

I should have phrased that differently, since it appears there might be no direct migration path from "Windows Server 2012 Essentials" to "Windows Server 2012 R2 Essentials" as discussed in the podcast. Not that terrible, since I've given up on trying to save client PC backups, starting all over with each release (but keeping my ~3TB of shared data between versions).

 

Been working with MS Sr Engineer on their DirectAccess team for 3 weeks to resolve a DA issue. They insist it won't require a reinstall but rather are using my unique scenario to gather data on something they've not seen before.

 

Robert Pearman (Titlerequired.com) has already confirmed same issue was resolved by an OS reinstall. If so, I may just use this opp to upgrade to R2 instead.

Excellent article you refer to there Jason, by Robert at:

http://titlerequired.com/2013/06/17/unravelling-the-mystery-of-client-dns-with-essentials-family-servers/

Thank you!

[Jason 51]

You're welcome. Though exercise caution when implementing DA as it is prone to stop working unexpectedly after months of stability. In my case, even most experienced MS engineers have been unable to determine cause of issue despite uninstalling and reinstalling DA role on server. And these are the guys that developed DA. Scary, I know....

[Poppapete 103]

The article by Robert Pearman is must read for anyone (like me) who is not an expert in the MS server field. I am truly enlightened re the DNS resolution interactions of Client, Server and Router. The diagrams are excellent. A picture is worth a thousand words. Thank you Jason and Paul for the links.

[Jason 51]

Honestly I set all my client machines to DHCP for IP and DNS (obtain automatically) and disable to Windows Server LAN Configuration service and there's no issue.

[tinkererguy 22]

I agree, it is usually that simple!

(others have hard coded to Google DNS at 8.8.8.8 and 8.8.4.4, an alternative approach).

 

Exceptions are hidden devices, so they can't (easily) be tweaked via the GUI. What if they spring back to life when reinstalled, but the DNS IP is hard coded? Such as the Yoga 13 story I started this article with:

TinkerTry.com/windows-server-2012-essentials-ur3-coming-soon-will-finally-include-the-dns-fix-i-requested/

 

another nuisance is with every update rollup, which means the fixes have to be done again.

 

I admin about 8 systems that aren't in my house (client connector over VPN), so it's a bit of a hassle when their internet breaks.  Looking forward to this longstanding issue going away for good.  Just one less point of failure!

[Jason 51]

FWIW if you have 8 client PCs connected via VPN already then running DirectAccess on the server would be ideal. It's essentially a persistent, client-less VPN connection to the domain via Internet.

[tinkererguy 22]

FYI, Microsoft did acknowledge and (sort of) resolve this DNS issue in the now released UR3:

http://homeservershow.com/forums/index.php?/topic/6480-remote-ws2012e-client-pcs-that-skipped-domain-join-during-install-cant-surf-after-update-rollup-3-heres-the-fix/