Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: Windows Server » microsoft.public.windows.server.update_services
Thread: Computer grouping

HTVi
TV Discussion Newsgroups

Computer grouping
"Haim Beyhan" <haimb[ at ]enigma.com> 7/2/2007 10:47:46 AM
Hi,

Can someone help me grouping the computers? I have servers, desktops,
laptops and branch offices. Some of those machines use 2000, XP, 2003. The
laptops are roaming.
What strategy should be used?
Do I need to group them according to their location or their operating
system or software that is installed ?


Thanks

Haim Beyhan


Re: Computer grouping
"Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 7/2/2007 4:36:12 PM
"Haim Beyhan" <haimb[ at ]enigma.com> wrote in message
news:%23vuyuZJvHHA.4552[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text]
> Hi,
>
> Can someone help me grouping the computers? I have servers, desktops,
> laptops and branch offices. Some of those machines use 2000, XP, 2003. The
> laptops are roaming.
> What strategy should be used?
> Do I need to group them according to their location or their operating
> system or software that is installed ?

Truthfully -- whatever works for you. Grouping is exclusively a matter of
administrative convenience, although generally you'd want to group according
to where you'll approve updates and where you won't.

In my case, I generally group by function -- servers, desktops, notebooks. I
also have subgroups for my servers: The WSUS server is in it's own group, my
SBS server is in its own group. I separate my desktop group into *my*
desktops, and everybody else's, because *my* desktops get the updates first,
so I can test them.


--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....


Re: Computer grouping
"Haim Beyhan" <haimb[ at ]enigma.com> 7/3/2007 8:57:42 AM
What about operating systems?
If I have 2000/XP in "everybody else" group, do I have to separate them also
or just leave and the OS will decide if it needs the update or not?
We have also a branch office that I want the server there to get the
approvals from me and downloads from microsoft directly.
How should I group those machines? Another remote group and sub groups for
servers, desktops, notebooks etc ?

Thanks,

Haim


"Lawrence Garvin (MVP)" <onsitech[ at ]community.nospam> wrote in message
news:uA0zjcMvHHA.4648[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text]
> "Haim Beyhan" <haimb[ at ]enigma.com> wrote in message
> news:%23vuyuZJvHHA.4552[ at ]TK2MSFTNGP03.phx.gbl...
>> Hi,
>>
>> Can someone help me grouping the computers? I have servers, desktops,
>> laptops and branch offices. Some of those machines use 2000, XP, 2003.
>> The laptops are roaming.
>> What strategy should be used?
>> Do I need to group them according to their location or their operating
>> system or software that is installed ?
>
> Truthfully -- whatever works for you. Grouping is exclusively a matter of
> administrative convenience, although generally you'd want to group
> according to where you'll approve updates and where you won't.
>
> In my case, I generally group by function -- servers, desktops, notebooks.
> I also have subgroups for my servers: The WSUS server is in it's own
> group, my SBS server is in its own group. I separate my desktop group into
> *my* desktops, and everybody else's, because *my* desktops get the updates
> first, so I can test them.
>
>
> --
> Lawrence Garvin, M.S., MCTS, MCP
> Independent WSUS Evangelist
> MVP-Software Distribution (2005-2007)
> https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
>
> Everything you need for WSUS is at
> http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
>
> And, almost everything else is at
> http://wsusinfo.onsitechsolutions.com
> ....
>
>


Re: Computer grouping
"Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 7/3/2007 4:01:46 PM
"Haim Beyhan" <haimb[ at ]enigma.com> wrote in message
news:uM%23X5AVvHHA.5032[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text]
> What about operating systems?
> If I have 2000/XP in "everybody else" group, do I have to separate them
> also or just leave and the OS will decide if it needs the update or not?

Again, really a matter of convenience Haim. The Windows Update Agent has
intelligence built in so that it will only download/install those updates
that are applicable to the OS/SP it is running on.

Conceivably you could put five different versions of desktop OS (Win2003SP3,
Win2003SP4, WinXPSP1, WinXPSP2, Vista) in the same group and they'd all get
the proper updates needed.

In a very small environment with only a couple of dozen clients, this is
certainly a viable scenario.

But also be aware that WSUS 3.0 supports the use of heirarchical groupings.
So, whereas with WSUS 2.0, you'd have all of the above in a single Desktop
group, with WSUS 3.0, you can actually create subgroups under Desktop for
each OS if that makes organization easier.

Also, take note that the COMPUTERS node supports grouping by Operating
System, so that might also be an appropriate solution instead of creating
multiple groups with only a few systems each.


> We have also a branch office that I want the server there to get the
> approvals from me and downloads from microsoft directly.
> How should I group those machines? Another remote group and sub groups for
> servers, desktops, notebooks etc ?

If this is a replica server, there are a couple of ways you could approach
the question.

One way is to create a target group specifically for that remote site, and
then apply your common group organization as subgroups underneath the site
group.

Or, you could just lump all of those remote computers into your normal
computer type groups.

Or, you could make a site subgroup under Desktops, Notebooks, and Servers.

The real answer to the question, really is: It depends on how you intend to
manage approvals of updates.

Also, you may find that the taxonomy of your grouping will change over time
as needs dictate. Don't be afraid to make those changes, if you find it
serves your purpose.


--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....


Re: Computer grouping
antwesor <bogus[ at ]state.mn.us> 7/9/2007 2:11:58 PM
While reading articles in microsoft.public.windows.server.update_services, I
thought I heard someone called haimb[ at ]enigma.com whisper...
[Quoted Text]
> Hi,
>
> Can someone help me grouping the computers? I have servers, desktops,
> laptops and branch offices. Some of those machines use 2000, XP, 2003. The
> laptops are roaming.
> What strategy should be used?

I group them geographically. Since most of our workstations are Windows 2000
or XP this seems to work the best. We only have about 500 units.

We also have single group just for servers. Only a few of those.

Hope this helps.

> Do I need to group them according to their location or their operating
> system or software that is installed ?
>
> Thanks
>
> Haim Beyhan

--
antwesor

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen