Paul
Fri Mar 14 18:55:03 CDT 2008
As promised, I have added an article that explains how to apply WMI
filtering to Group Policies, hope it helps.
http://www.servercare.nl/Lists/Posts/Post.aspx?ID=33
cheers,
Paul
Paul Weterings wrote:
> I've looked into it a little further;
>
> I'm sorry to say that it doesn't work that way, this .adm file actually
> makes registry changes in the HKCU registry, so not on machine level.
> (Regional settings are user based)
>
> In fact, if you only want to change this once on only one machine you
> might want to play with that. For your reference:
>
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/34666.mspx?mfr=true
>
>
> So changing the .adm file would not help. What you need to to is assign
> the .adm template to the user configuration administrative templates,
> this will 'add' a regional settings folder in the control panel settings.
>
> Then you assign the GPO you created with these settings to a OU that
> contains the users you want the GPO to have effect on.
>
> Since you seem to want to narrow it down to a single system you might
> want to investigate WMI filtering to get that result. It's really pretty
> simple: in the group policy management console you create a WMI Filter.
>
> Suppose the system you want to target is named PC1, then the WQL (WMI
> Query Language) line would be something along the lines of:
>
> SELECT * FROM Win32_ComputerSystem WHERE Name = 'PC1'
>
> Now you assign that WMI filter to your GPO.
>
>
> Good question...! I feel inspired to expand my article to include this
> part. In the next few days I'll make some time to update it, if the
> above didn't quite cover it; make sure to check:
>
>
http://www.servercare.nl/Lists/Posts/Post.aspx?ID=22
>
> In the next few days.
>
> cheers,
>
> Paul
>
> Derek Da Silva wrote:
>> Hi Paul,
>>
>> How do I apply the GP to the computer configuration? Do I change the
>> first line to "Class Computer"?
>>
>> Thanks,
>> D
>>
>> "Paul Weterings" wrote:
>>
>>> Derek Da Silva wrote:
>>>> After reviewing the information in the article i noticed it only
>>>> reflects how to update the user OU. Is there a way to update a
>>>> computer. For instance, I have 6 computers and I want the date
>>>> format to be mm/dd/yyyy, however, on the 7th computer I would like
>>>> the date format to be m/d/yyyy.
>>>>
>>>> Any suggestions?
>>>> Thank you,
>>>> D
>>> In the example the template is applied to the administrative
>>> templates of the user configuration. I haven't tested it, but it
>>> seems to me that the same template could also be applied to the
>>> computer configuration.
>>>
>>> From there on it depends on you how you would want to apply the GPO.
>>>
>>>> "Paul Weterings" wrote:
>>>>
>>>>> Derek Da Silva wrote:
>>>>>> Hi Everyone,
>>>>>>
>>>>>> I have a unique problem. Everytime my users log onto a
>>>>>> workstation and attempt to run a specific application it reports
>>>>>> that they need to change the system date format from m/d/yyyy to
>>>>>> mm/dd/yyyy.
>>>>>>
>>>>>> I currently have a script which updates the system everytime the
>>>>>> user logs onto the workstation. Is there a way I can invoke the
>>>>>> system date change during workstation bootup rather than when the
>>>>>> user logs onto the workstation?
>>>>>>
>>>>>> I appreciate anything you can do to assist with this issue,
>>>>>>
>>>>>> Thank you,
>>>>>> D
>>>>> Hi Derek,
>>>>>
>>>>> You might not even need scripting...
>>>>>
>>>>> Depending on your situation (are you admin on a managed network or
>>>>> not) I may have a tip for you; you could use a group policy with a
>>>>> customized ..adm file that changes the computers registry. Then
>>>>> apply the setting to only the systems that need to run the
>>>>> application you mentioned (using either an OU or even security of a
>>>>> WMI filter)
>>>>>
>>>>> A detailed example of a custom Group Policy that changes date and
>>>>> time format can be found here:
>>>>>
http://www.servercare.nl/Lists/Posts/Post.aspx?ID=22
>>>>>
>>>>> I hope this helps you in the right direction.
>>>>>
>>>>> cheers,
>>>>>
>>>>> Paul
>>>>>
>>>