Active Directory Users and Computers not showing all tabs in Windows 10 build 1511

Issue:
Missing tabs in AD Users and Computers (dsa.msc) in Windows 10 build 10586 (1511). Also unable to perform certain actions in AD Users and Computers.

Cause:
Problem is with the latest RSAT KB

Solution:

• Start > Type Features, Click "Turn Windows features on or off"
• Uncheck Remote Server Administration Tools, Click OK.
• Open administrative command prompt and run:

wusa /uninstall /kb:2693643 /norestart

• Reboot the computer
• In "Turn Windows features on or off", "Remote Server Administration Tools" should no longer be available. 
• Download and install the old RSAT version from 

https://drive.google.com/file/d/0B-meMiJiVDGATkpyS3J0Q29yZ1U/view?usp=sharing

Credit: jletellier on SpiceWorks

Mirror: https://www.dropbox.com/s/h9u963vz4t0w1b4/Windows10RSAT_100105850.msu?dl=0

• Check RSAT is now ticked in "Turn Windows features on or off"
• Run dsa.msc
• Check version in Help > About AD Users and Computers - should now be 10.0.10585.0 and should now show all tabs.

Reference: SpiceWorks Thread

Configure Hyper-V Client Tools on Windows 10 to manage non-domain Server 2012 R2

Out of the box, it's not possible to manage a non-domain joined Hyper-V 2012 R2 server from Windows 10. The following steps can be taken to enable WinRM and allow management.

Check the scripts before running them as they will install Hyper-V and the Management tools. If you've already done this you can remove those lines.

Bear in mind this uses NTLM encryption (Negotiate authentication) over HTTP. You will need to check to see if this is secure enough for you. Here is some further reading.

Windows Editions Used

Server: Windows Server 2012 R2 (I used the RTM disk, fresh installed no updates)
Client: Windows 10 Pro (I used Insider Preview 14965, fresh installed no updates)

Server Configuration Script



Client Configuration Script


Manual Client Configuration
This is an additional step to the client configuration script and must be completed for this to work

• Click Start > Run > type 'dcomcnfg' > OK
• Browse 'Component Services' > 'Computers'
• Right Click 'My Computer' and Click 'Properties'

• Click the 'COM Security' Tab, then click the 'Edit Limits' button in the 'Access Permissions' section.

• Check 'Allow' on 'Remote Access' for the 'ANONYMOUS LOGON' user group. Click OK.

• Management should now be possible.

If you want to manage the host with a non-admin account you can additionally follow this guide.

How to Enable Hyper-V Manager for Non-Administrators from Windows 10

After adding a user or group to the Hyper-V Administrators local group on a host, you are still unable to connect to the host with Windows 10 Hyper-V Manager.

The error is as follows:
"You do not have the required permission to complete this task. Contact the Administrator of the authorization policy for the computer 'SERVERNAME'."

This is due to a change in the way Hyper-V manager connects to the server in Windows 10 / Server 2016. 

To re-enable the functionality, the user or group needs to be added to the "WinRMRemoteWMIUsers__" and "Hyper-V Administrators" groups. It also needs to be given the "Enable Account" and "Remote Enable" permissions to the root\interop WMI namespace.

To do this in the GUI, open Computer Management and add the user or group to the "WinRMRemoteWMIUsers__" group. On 2016 this group doesn't exist, I added the user/group to the "Remote Management Users" group on my 2016 hosts. 

Also, open "Services and Applications -> WMI Control" properties. Click the security tab, open Root\interop and click the Security button. Add your user or group and check Remote Enable.

To do this with PowerShell, execute the following script (needs to be done with Administrator privileges)


For Windows Server 2016 Hyper-V Servers you will need to change the group "WinRMRemoteWMIUsers__" to "Remote Management Users" in the above script.

For more information on the permissions code please see the below post, I have used only the specific lines required for enabling the specific permissions I require. The following post has a more generic script for WMI permissions:

http://vniklas.djungeln.se/2012/08/22/set-up-non-admin-account-to-access-wmi-and-performance-data-remotely-with-powershell/