I get this question all the time:

“What happens if I apply Vista-specific settings to my XP machines?”

So, here’s the answer: If you have a “newer” policy setting, and it affects an “older” machine… (in general) NOTHING BAD HAPPENS.

Let’s figure out why.

Let’s take the case of a “newer” policy setting, say, “Remove Games link from Start Menu” which is a Vista-only function. XP doesn’t have a Games link to remove off the Start Menu.

So when you affect an XP machine with a Vista-specific policy setting, the interesting part is … something DOES happen.

But it happens under the hood, and we don’t really see it.

That “something” is that a registry entry gets punched in place which gives the edict to “Remove Games link from Start Menu” to Windows Explorer.

Except XP’s Windows Explorer doesn’t know what to do with this information. So it promptly ignores it.

What about the other direction? Can you take an “older” policy (say, for XP) setting and affect a newer” (Vista) machine?

Usually. Like “Prevent access to the control panel.” Works great since Windows 2000,and then XP and now Vista.

Not all XP policy settings are valid for Vista, however.

Why? Well, Vista shook some items up a bit, and some got lost in the shuffle.

How do you know if a policy setting is valid for a particular operating system? Use the GP Editor Filtering capabilities to determine if a setting is valid for a particular operating system. And also check the Explaintext and what’s known as the “Requirements” settings. You can see the “Requirements” indicator when you click on a policy setting and you’re using the “Extended” view (the default.)

Most policy settings will say something like: “At least Microsoft Windows XP” or “Windows Server 2003 family.”

So it’s not really true that “NOTHING” happens when you create a GPO which contains policy settings for “older” machines. Something does, indeed happen.

Except it’s basically ignored, because that operating system wouldn’t know what to do with the directions it just got.

Stay tuned to more group policy goondess from Jeremey over at GPAnswers.com!