Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
Yes.
The normal method would be to place all your workstations in a single OU and
apply the policy there. I'm guessing that all your computers (both servers
and workstations) are still in the default "Computers" container and that,
because you can't apply a GPO to this container because it's not an OU,
you're applying the GPO at the root of the domain.
So, just create another OU, place your workstations in it and link the GPO
at this point instead of where you're currently linking it.
Hope this helps
Oli
"flekso" <flekso@vip.hr> wrote in message
news:ce596c73.0411280744.1d3c8c8a@posting.google.com...
> Is there a way to limit the GPO software installations to workstations
> and avoid the server(s) ?
Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
But what happens when new workstations are added to the domain, it's
not future proof.
"Oli Restorick [MVP]" <oli@mvps.org> wrote in message news:<eal9VrW1EHA.1452@TK2MSFTNGP11.phx.gbl>...
> Yes.
>
> The normal method would be to place all your workstations in a single OU and
> apply the policy there. I'm guessing that all your computers (both servers
> and workstations) are still in the default "Computers" container and that,
> because you can't apply a GPO to this container because it's not an OU,
> you're applying the GPO at the root of the domain.
>
> So, just create another OU, place your workstations in it and link the GPO
> at this point instead of where you're currently linking it.
>
> Hope this helps
>
> Oli
>
>
> "flekso" <flekso@vip.hr> wrote in message
> news:ce596c73.0411280744.1d3c8c8a@posting.google.com...
> > Is there a way to limit the GPO software installations to workstations
> > and avoid the server(s) ?
Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
You either add them by script to the correct place, create the computer
accounts ahead of time, or move them afterwards.
Oli
"flekso" <flekso@vip.hr> wrote in message
news:ce596c73.0411290408.5c799800@posting.google.com...
> But what happens when new workstations are added to the domain, it's
> not future proof.
>
> "Oli Restorick [MVP]" <oli@mvps.org> wrote in message
> news:<eal9VrW1EHA.1452@TK2MSFTNGP11.phx.gbl>...
>> Yes.
>>
>> The normal method would be to place all your workstations in a single OU
>> and
>> apply the policy there. I'm guessing that all your computers (both
>> servers
>> and workstations) are still in the default "Computers" container and
>> that,
>> because you can't apply a GPO to this container because it's not an OU,
>> you're applying the GPO at the root of the domain.
>>
>> So, just create another OU, place your workstations in it and link the
>> GPO
>> at this point instead of where you're currently linking it.
>>
>> Hope this helps
>>
>> Oli
>>
>>
>> "flekso" <flekso@vip.hr> wrote in message
>> news:ce596c73.0411280744.1d3c8c8a@posting.google.com...
>> > Is there a way to limit the GPO software installations to workstations
>> > and avoid the server(s) ?
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.