10-04-2017 05:10 AM
10-04-2017 05:10 AM
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, DHCP, WSUS, RAS etc. are there.
It should be there, right?
10-04-2017 07:59 AM
10-04-2017 08:02 AM
The formatting went wonky on what I just posted but hopefully it is usable.
The last step of course is to make a shortcut to system32\dnsmgmt.msc and copy it into your start menu admin tools folder.
10-18-2017 11:15 AM - edited 10-18-2017 11:26 AM
I've been having problems getting RSAT to install on build 16299 and tried your method above, but get the error "MMC could not create the snap-in."
It seems like Microsoft is trying to get away from MMC. Is there some new way I'm suppose to be managing my servers that isn't powershell?
Edit: disregard, I forgot to run the regsvr32 command at the end. "facepalm:
Edit 2: If you don't have another Windows 10 or Server 2016 machine to copy from, and you just upgraded your copy of Windows (which broke RSAT), you can copy the files from the C:\Windows.old directory.
10-24-2017 11:58 AM
We're also seeing this issue on the current download here:
We'd prefer not to move files around manually in order to get DNS back - when can we expect an actual fix (i.e. a new release) for this issue?
And more importantly, how could this pass even the most basic of QA tests and be released to the general public? :)
10-24-2017 03:17 PM
In my "perfect world" people would get fired over this. Think of all the thousands of wasted hours this will now cause.
10-25-2017 05:44 PM
I was able to accomplish the same thing by just copying the files out of the windows.old directory on the same PC after moving to build 1709. Workaround works, but MS should actually fix the actual issue...
11-06-2017 02:42 PM
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.
11-06-2017 03:08 PM
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.
11-07-2017 07:36 AM
11-07-2017 10:01 AM