Collection Consolidation

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Collection Consolidation

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> Collection Consolidation

Page: [1]

Message

<< Older Topic Newer Topic >>

Collection Consolidation - 8/1/2008 2:12:40 PM

gurltech

Posts: 2
Score: 0
Joined: 8/1/2008
Status: offline

I am trying to consolidate collections as I move to SCCM I inherited this SMS 2003 from someone who left it a mess.

Here is the issue. When they built the SMS server the original software advertisement collection worked fine. as far as I can tell they stopped using it and put that core software in the image, now half the machines have some core software installed with the image.

Then they created another collection with additional core software and that is the one I continue to use. But the original group still has the machines in it that did not receive the software via the image.

Now that I am migrating to SCCM I would like to consolidate the two collections and not have the workstations re-installing the software. But I would like new workstations coming online to get all the software that was in both collections which are now being consolidated. My line of thinking is to have OSD drop the image and let collections install the software as it should be.

How do I keep the current machines from getting software that they already have from being re-installed when I combine the collection?

Am I on the right path combining the collections?

How would you do it?

Thanks in advance for any suggestions with this.

Post #: 1

RE: Collection Consolidation - 8/1/2008 11:33:38 PM

skissinger

Posts: 2114
Score: 134
Joined: 9/13/2001
From: Sherry Kissinger
Status: offline

I don't know if this suggestion is "the right way". I don't know if there is a right way. But I think what I would do is have more collections, not less. Using Subselect queries, individual collections for "computers that do not have Widgets v3.1"; and target widgets 3.1 to that. Another for 'Computers that do not have Really Important Line of Business Application 1.6"; and target RILBA 1.6 to that collection. You get the idea. Of course, you'd have to wait for HW Inventory, and collection eval before a newly imaged machine would get certain applications, but you'd be assured that computers that already have Widgets 3.1, won't get it again.

Of course, there may be other factors in your environment where the above suggestion simply won't work out--either technical or political reasons. So the basic "your mileage may vary". "Just a suggestion". etc. etc. apply here.

_____________________________

mofmaster@smsexpert.com (version 2007) | http://www.smsexpert.com | http://www.sccmexpert.com
My Blog
Microsoft MVP - ConfigMgr

(in reply to gurltech)

Post #: 2

RE: Collection Consolidation - 8/3/2008 3:23:22 PM

mhudson

Posts: 539
Score: 12
Joined: 4/1/2007
From: College Station, TX
Status: offline

One thing that we did to ensure software is done quickly and the correct way was to have a HW inventory just after the image is complete. This way you can "hope" the computer is removed from collections that it doesn't need to be in. As Sherry stated subselected queries are the way to go.

_____________________________

Matthew Hudson
http://sms-hints-tricks.blogspot.com/
http://www.sccm-tools.com

(in reply to skissinger)

Post #: 3