Let's dig into the Adam X Files a little bit more and see what they're all about.
So I've got the C colon backslash window's backslash policy definitions folder up and I took the liberty
of associating my Adam X extensions with Notepad, so it's easy for me to bring up an admixture file.
And what you see here is the auto play date end that I showed in my previous slide.
And it's small and not necessarily something that's intuitive to author, and that's why I recommended
using an offering tool of some kind.
But essentially how it works is you have a policy and this is a policy tag.
It's got a name.
It's got some strings associated with it.
And these strings are defined in the ADMA file for the particular language that you're working in.
And then it's got some explain text.
Again in the ADMA file, what kind of presentation it uses?
Is it a checkbox or list box, that sort of thing.
What key is affected by this policy?
And you'll see it's one of our four policy keys under current version backslash policies and then it
if you go down underneath this policy, you've got some more elements and this is the value in the registry
that's set.
And then it tells you if the value is set to disabled, then the actual value of the registry is set
to one.
If it's set to no auto run underscore XP, then it's set to two.
And these all mean something.
The strings correspond to text that's defined in the ADMA file.
So essentially that's how the ADMA X file works.
But we can also do is drill into the C and U.S. folder and see all of the ADMA files.
And if I go in under the autoplay dot ADM and I'm going to tell it, I want to open that with Notepad
as well.
You'll see how each of the strings defined in the Adam X file have corresponding text associated with
them.
So the various things that you saw in that Adam X file are translated into nice, easy to read text
within the ADMA file.
So let's look at how we can create the central store that I mentioned.
So what I'm going to do, I have my Adam X and ADMA files defined in this Windows policy definitions
folder on the local machine.
And I'm going to go ahead and copy all of these files.
What I'm going to do is I'm going to go ahead and bring up the Explorer on this PC.
I happen to be on a Windows Domain controller.
So I'm going to go ahead and drill into the sizable folder that's shared out assist wall on this Windows
two main controller.
And I want to drill into Windows sizeable domain policies because that's where the folder is shared
from.
And I'm going to go ahead and create that new policy definitions folder.
And then I'm going to paste the contents of my local policies definitions folder into this one.
And now I have a central store.
That's really all there is to it.
Now, if I were to go in and reload, PMC, go ahead and run that again and edit this policy and expand
administrative templates.
You'll see here, if I highlight the administrative templates node, it says policy definitions are
being received from the central store.
And that's telling you that indeed all of my admin template settings or all of my underlying admin templates
that are building these trees of policy settings are coming from the central store.