Forum Discussion

Copper Contributor

Oct 04, 2017

Solved

RSAT missing DNS Server Tools?

Hi, on a fresh Win 10 insider client (16278 updated to 16299) I installed Windows_InsiderPreview_RSAT_x64_16279 but it seems to be missing DNS Server Tools, the MMC snap-in. All other tools like AD,...

management

Samuel Li
Jan 18, 2018
[UPDATE] The final 1803 release of RSAT is now on the public RSAT download page. Look for the WS_1803 package there, thanks!

-----

Here's the official KB workaround published by the DNS team:

https://support.microsoft.com/en-us/help/4055558/rsat-missing-dns-server-tool-in-windows-10-version-1709 (thanks Christoff MOrlOck for posting this previously)

The RSAT download page now also has this info under Additional Information:

Issue: DNS Tools missing
Impact: WS_1709 RSAT package users
Resolution: Use the WS2016 RSAT package or apply this workaround

The DNS team has also fixed the root cause for RS4 and so the workaround will not be required for the upcoming RS4 RSAT package update.

Jim Harle

Brass Contributor

Nov 06, 2017

Attached are the files I've been using for the workaround. Agreed that this issue needs to be fixed - it is a bit ridiculous. Literally - Windows haters ridicule Microsoft over stupid little things like this, and preventable mistakes just reinforce the stereotype.

DNS.zip594 KB

rjt87

Copper Contributor

Nov 15, 2017

The "Additional Information" section of https://www.microsoft.com/en-us/download/details.aspx?id=45520 now recommends to use the WS2016 RSAT package instead if DNS tools are missing. We are using 2012r2, so the WS2016 RSAT package is what I should use anyway.

When to use WS_1709 RSAT Package: When managing Windows Server, version 1709
When to use WS2016 RSAT Package: When managing targets older than Windows Server, version 1709

There are known issues that may impact RSAT functionality
Issue: DNS Tools missing
Impact: WS_1709 RSAT package users
Resolution: Use the WS2016 RSAT package

Jim Harle
Brass Contributor
Nov 15, 2017
Yes, the "Additional Information" section on the download page does clarify things. The problem is, Microsoft has moved the goalposts on this. We are conditioned that RSAT gets broken after feature updates (upgrades), and that we need to go fetch the latest version to get things working again. In other words, match the version of RSAT to the client version.

Now there seems to be a directive to "install the RSAT version to match the server version being managed." What happens when you have a mixed environment with old and new? Dumb. The newest version of RSAT should always be (within reason) backwards-compatible.