I'm the guy that gave you the answer re: the password policies... >smile<
Sam's answer is basically correct. To make it a bit more specific to your circumstance, you wnat to link the GPO with your password policy settings onto the OU where the server computer that needs the different password policy is located. Be aware that if there are other computers in that OU they will apply the policy as well. That may not be exactly what you want.
Consider the following:
[domain] domain.com
|
|- [OU] Member Server Computers
| |
| |- [Computer] SERVER01
| |
| |- [Computer] SERVER02
Supposing that you want only SERVER02 to have the altered password policy settings, your best move is to create a sub-OU of the "Member Server Computers" OU and place SERVER2 into it, like so:
[domain] domain.com
|
|- [OU] Member Server Computers
| |
| |- [Computer] SERVER01
| |
| |- [OU] Relaxed Local Password Policy Computers
... | |
... |- [Computer] SERVER02
In this way, all the GPOs that already apply to "Member Server Computers" will still apply to SERVER2 (since it's location in the directory is still below "Member Server Computers"), but the GPO that you create and link to "Relaxed Local Password Policy Computers" will only apply to SERVER02.
Doing this with the sub-OU is also nice, assuming that there are other computers in the same OU as "SERVER02", because it limits the application of the policy in cases where you do something you don't mean to. You can damage a lot of computers very quickly and efficiently with group policy... >smile< It's an excellent tool for amplifying human mistakes.
(There are other ways to make the GPO only apply to SERVER02 w/o creating a sub-OU. This isn't the place to discuss them, but when you're ready, search for the phrase "group policy filtering permission" with your favorite search engine and you can learn about it.)
I've found that the OS documentation for Group Policy is really convoluted and terrible-- what w/ all the talk about "precedence", etc. It's a very simple algorithm that Group Policy uses to determine the "effective" settings based on applying a bunch of GPOs to a user or computer, but Microsoft technical writers seem to want to make it seem "magical" and, thus, they seem to make the documentation too complex. I ought to sit down sometime w/ a microphone and a screen capture utility and do a "tutorial on Group Policy application" video or something. (Yeah... in my copious free time...)