Avatar of Rusty Waltz
Rusty Waltz
 asked on

ADMX files not being loaded

4 Windows 2016 STD servers serving Active Directory Services on a single domain.   Functional Domain level is 2012 R2.  Having trouble loading ADMX and ADM files to support 2016 server and Windows 10 Build 1809.  I  copied the 1809 ADMX files to the \\"domain server"\SYSVOL\"FCDN"\Policies\PolicyDefinitions  for testing and had no success.   Server restart was also performed.
Windows 10Windows OSActive Directory

Avatar of undefined
Last Comment
Rusty Waltz

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
McKnife

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Brian Murphy

Just to supplement what McKnife has stated and looking for no additional credit here but I generally spin up a VM for every down level client and add the appropriate Group Policies their first then make the changes using Group Policy Management relative to the domain and Sysvol.  It was a tad more simple when their was a direct correlation to server OS and Client like WIN 7 SP1 and 2008R2 or 2012 and Win 8 but with Win 10 and 2016 that has changed some what.   It is simply easier to bring up a version of that Windows 10 client and release with the corresponding GPO files and apply them that way.  This way, you know that what you are applying is specific to that OS and that release.

Otherwise, it just causes problems.   AD stores the references, GUIDS, to the GPO's, but the ADMX/L files are still file level specific to SYSVOL.   You will have disparities between Win10 client and 2016.  Unless your patching both at the same time using WSUS or some other mechanism.   Not so simple.
Rusty Waltz

ASKER
So I went to add the Group Policy Management as part of a optional "features" and it failed.

GPO-failure.png
Rusty Waltz

ASKER
Tried as elevated /local admin also.......  No luck.

Powershell resulted in this also....

PS C:\WINDOWS\system32> Add-WindowsCapability -Online -Name Rsat.GroupPolicy.Management.Tools~~~~0.0.1.0
Add-WindowsCapability : Add-WindowsCapability failed. Error code = 0x800f0954
At line:1 char:1
+ Add-WindowsCapability -Online -Name Rsat.GroupPolicy.Management.Tools ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Add-WindowsCapability], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.AddWindowsCapabilityCommand
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
McKnife

Rusty Waltz

ASKER
McKnife,  The DISM cmd failed.  Attached is the logdism.log
McKnife

I am not sure if you are saying that you tried what was linked. Since it shows how to overcome that error, it should help.
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Rusty Waltz

ASKER
Still working on this.  Will be trying again over the weekend
Rusty Waltz

ASKER
Completed software installs.   RSAT installed on Win 10 for version 1809.  Issue resolved