Administrative Templates (.admx) for Windows 10 April 2018 Update (1803)

[mrwoberts]

1803 ADMX templates

https://www.microsoft.com/en-us/download/details.aspx?id=56880

[Jaan]

I'm getting the following error after updating the templates to my sysvol:

 

"Resource '$(string.Win7Only)' referenced in attribute displayName could not be found. File \\SysVol\...\Policies\PolicyDefinitions\SearchOCR.admx, line 12, column 69"

 

Found other people are having the same issue in the Microsoft link below:

 

https://social.technet.microsoft.com/Forums/en-US/cb97affb-9724-457b-a113-32cbd3d53331/searchocradmx-error-after-installing-win101803-admx-templates?forum=winserverGP

 

Anybody Else had this and been able to resolve it?

 

cheers

[Jaan]

Update:

 

Reverting to the previous versions of SearchOCR. admx & SearchOCR. adml fixes the issue. (I backed up the policies folder in sysvol before hand).

 

Waiting for official word from Microsoft

[Arthur]

Anybody else had this and been able to resolve it?

Not had this issue myself. I upgrade the ADMXs every time Microsoft release new templates so have gone from 1703 > 1709 > 1803 over the past year.

 

Which version of the templates did you have in your central store before upgrading to the 1803 templates?

[Jaan]

Not had this issue myself. I upgrade the ADMXs every time Microsoft release new templates so have gone from 1703 > 1709 > 1803 over the past year.

 

Which version of the templates did you have in your central store before upgrading to the 1803 templates?

 

1709 before i updated.

[arh1a]

Just updated a few sites now and not having any problems. Previous was 1709

[Jaan]

Just me then

[arh1a]

What server OS are you running? I'm on 2016

[ollyyllo]

The 1511 templates are the only ones to include a SearchOCR.admx which has a reference to Win7Only.

1803 is the only template after 1511 to introduce a new searchocr.adml, which has the Win7Only reference missing.

 

So I think you'll only get the error if you have installed the 1511 templates and then the 1803 template??

Edited May 8, 2018 by ollyyllo

[Jaan]

2016 also

[arh1a]

I'm not sure of the official way of updating the ADMX files but I do it this way which has worked for me.

 

1 - Install ADMX template on a computer then copy the PolicyDefinitions from Program Files (x86)

2 - Move the old PolicyDefinitions folder from C:\Windows\SYSVOL\domain\Policies to a temp location.

3 - Copy the new PolicyDefinitions folder to C:\Windows\SYSVOL\domain\Policies

4 - Then copy over specific ADMX files, Chrome, Office2016 etc to the new PolicyDefinitions folder with the latest ADMX files

[Jaan]

yeah this is the process i used to update.

[bduran71]

Lots of folks having this error, including me. What I have found is here:

 

https://www.grouppolicy.biz/2018/05/how-to-fix-searchocs-admx-error-after-upgrade-to-windows-1803-admx-files/

 

Followed the steps outlined and the issue is resolved.

 

One posting also referenced "the SearchOCR.ADMX file is only installed in the PolicyDefinitions folder if you have the "Windows TIFF Ifilter" option installed. If you have ever done this on an old version of windows and then copied it across to the Policy Definitions folder then this will be an old version of the file as it wont be updated using the ADMX/ADML bundel that Microsoft publishes. "

 

He recommended..."either 1. Delete the SearchOCR.ADMX file if you don't use any of the policy settings or 2. Install Windows TIFF Ifilter on a computer running Windows build 1603 (server or workstation) and copy that SerchOCR.ADMX file into the central store. "

[Arthur]

Lots of folks having this error, including me.

Microsoft has a KB article with a fix for this error now...

 

https://support.microsoft.com/en-us/help/4292332/error-when-you-open-gpedit-msc-in-windows

[mullet_man]

Microsoft has a KB article with a fix for this error now...

 

https://support.microsoft.com/en-us/help/4292332/error-when-you-open-gpedit-msc-in-windows

 

I just removed the adm files - seems to have sorted it.

[free780]

Update here:

https://www.microsoft.com/en-us/download/details.aspx?id=56880

 

I'm getting errors with WindowsDefenderSecurityCenter.admx when using GPMC and gpresult on 1709.

 

Anybody else get issues?

[DJ-1701]

I'm just wondering what has changed with them.

 

When I updated one of the schools to 1803 admx before this update, I had to clear everything and start from scratch because of the weird admx issues that kept popping up when editing a policy.

[free780]

I saw similar warnings when using gpmc on Server 2016 when we updated to 1709 admxs. Policy is still applied. I can't imagine anywhere having an environment with every client and server on 1709 or 1803. Microsoft did a similar thing with IE11 GPMC only working on Windows 8. It works the other way as well legacy settings left in GPOs can only be removed via powershell.