Forum Discussion
RSAT missing DNS Server Tools?
- 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 workaroundThe 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.
I do not have a 2016 server or a windows.old with relevant dns msc files. Some MSC Admin tools are only used by a very small fraction, but DNS?
Please provide an update soon.
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.
- Mike WestMar 16, 2018Copper Contributor
Jim Harle wrote:
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.
i know this thread is somewhat old but this is still an ongoing issue. just wanted to point out that this workaround worked perfectly for me. Thanks for the files buddy.
- Kevin GoodknechtDec 12, 2017Copper Contributor
Thanks for posting the files, it works now.
- Daniel GreenawayNov 17, 2017Copper ContributorThanks, this worked a treat.
- rjt87Nov 15, 2017Copper Contributor
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 HarleNov 15, 2017Brass Contributor
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.
- David AshcroftNov 07, 2017Copper Contributor
The above worked for me thanks :)
- David HardingNov 07, 2017Copper ContributorThanks! Worked for me. I use DNS all the time as a Sys Admin. I am on the Insiders Program and waiting for 17025.1000 to download and install. I installed 1709 and noticed that my RSAT tool tiles were missing on my Start menu. I found that I needed to install RSAT for 1709. But then missing my DNS tool, I cannot be without, although, I am using PowerShell more to work with DNS.
- David HardingNov 07, 2017Copper ContributorI had to re-install the RSAT again after the preview installation of Build 17025.1000. Also had to re-run the registration and pin the DNS link back to my Start menu.
- Manny LopezNov 06, 2017Copper Contributor
Thanks, I'm able to use DNS Manager now.