Install Active Directory for Windows 10 as use Windows 10 Professional or Enterprise. On a Windows server, this is part of the standard Windows Server administration tool but released as a downloadable tool that can be downloaded for Windows 10. Removing restrictions which Administrator or Remote Desktop must use in Windows Server to manage their domain
Install Active Directory for Windows 10 Driver
- When you install Windows Update 10 October 2018 (1809) or later, to manage Windows Server 2019 or earlier versions.
- See the “Installation instructions” section above for details on how to install the RSAT feature on request (FODs) directly from Windows 10.
Download and install the Active Directory for Windows 10 package here:
Active Directory for Windows 10 Tools Driver Download
- When you install Windows Update April 10 2018 (1803) or earlier, to manage Windows Server, version 1803 or Windows Server, version 1709.
- When you install Windows Update April 10 2018 (1803) or earlier, to manage Windows Server 2016 or an earlier version.
Known issues that affect various versions of RSAT:
Problem: The RSAT FAT installation in Active Directory for Windows 10 failed with error code 0x800f0954. Effects: FAT RSAT on Windows 10 1809 (update October 2018) in the WSUS / SCCM environment. To install FOD on a computer connected to a domain that receives updates through WSUS or SCCM, you must change the Group Policy settings to allow downloading FOD directly from Windows Update or local sharing. For details and more instructions on how to change these settings, see this topic.
Problem: Installing RSAT FAT is not displayed through the Status / Progress settings application. Impact: FOD RSAT on Windows 10 1809 (Updated October 2018). Solution: To see the progress of the installation, click the Back button to see the status on the Manage Optional Features page.
Problem: The process of removing the RSAT installation might fail FOD over application settings. Impact: FOD RSAT on Windows 10 1809 (Updated October 2018). Solution: In some cases, deletion failure returns to the need to manually delete dependencies. In particular, if the RSAT A tool is required by RSAT B, the option to uninstall the RSAT A tool will fail if RSAT B is installed. In this case, first uninstall the RSAT B tool, then uninstall the RSAT tool. See the FAT RSAT list, including dependencies.
Problem: Installing the FOD RSAT doesn’t seem to work, but this tool is still installed. Impact: FOD RSAT on Windows 10 1809 (Updated October 2018). Solution: The restarting computer will complete the removal of the tool.
Problem: Missing RSAT after Windows 10 Upgrade. Effect: Each RSAT .MSU package installation (before the RSAT FOD) is not reinstalled automatically. Solution: RSAT cannot continue to be installed through operating system upgrades because RSAT .MSU is sent as a Windows Update Active Directory for Windows 10 package. Please reinstall RSAT after updating Windows 10. Note that this limitation is one of the reasons that prompted us to switch to FOD starting with Windows 10 1809. FAT RSAT will still be installed on the upcoming Windows 10 update.
Problem: The DNS tool does not exist. Impact: WS_1709 RSAT package user. Solution: Use the RSAT FOD, or use the RSAT WS_1803 or RS2016 package or apply this solution
Problem: Each RSAT component cannot be turned off. Impact: WS_1803 and RS_1709 RSAT users on Windows 10 1803/1709 (update / fall maker update in April 2018). Solution: Use RSAT FODs, or use the RSAT WS2016 package on Windows 10 1607 (Birthday Update)
Problem: Tab missing from MMC property. Effect: Windows 10 clients before 1607 (anniversary updates). Solution: Update to the latest version of the Windows 10 client and reinstall RSAT
Problem: The File Data Shield Wizard cannot create a shield data file. Impact: WS_1709 RSAT Package User on Windows 10 1709 (Fall Creators Update). Solution: Use RSAT FODs, or use the RSAT WS_1803 package on Windows 10 1803 (Update April 2018), or use the RSAT WS2016 package on Windows 10 1607 (Birthday Update) to make data files protected for Windows-protected VMs, or built-in in RSAT Windows Server, version 1709 to create protected data files for Windows and Linux protected VMs.
Issue: The template disk created from the Template Disk Wizard does not run. Impact: WS_1709 RSAT Package User on Windows 10 1709 (Fall Creators Update). Solution: Use RSAT FODs, or use the RSAT WS_1803 package on Windows 10 1803 (April 2018 update), or use the RSAT WS2016 package on Windows 10 1607 (Birthday Update) to create a template disk for a Windows-protected VM, or on the RSAT tool in Windows Server, Version 1709 to create protective data files for Windows and Linux protected VMs.
Problem: IPAM in Server Manager asks you to install even though IPAM is installed. Impact: IPAM users on Windows 10 1803/1709 (updates fall / fall updated in April 2018). Solution: Use FAT RSAT, or use IPAM from the RSAT package installed on Windows 10 1607 (Birthday Update) or 1703 (Update Maker) in Active Directory for Windows 10.
Incoming search terms:
- active directory tools windows 10 1809
- active directory windows 10 1809 install