Assigning systems to collections based on their subnet
I have created collections where I want my systems to be assigned based on their subnets.The systems are all present in 'All Systems' collection.I have defined membership rules for collections as - Resource Class-System resource > Attribute name-IP Subnets > Value - Subnet under which systems are > Search in tis collection - All systems. The problem is that new systems joining in the subnet do not get assigned to the collections I have to add them manually .I have an Active directory boundary. Please suggest how can I do this.Thanks
March 9th, 2010 9:39am

Your criteria seems to be ok. How do you have to add systems manually? By adding direct memberships or by running a collection update? If it's the latter you can shorten the collection update cycles, but it will never be updated real time.
Free Windows Admin Tool Kit Click here and download it now
March 9th, 2010 1:04pm

Yes Manu,the query brought in more systems,but it also brought system references which existed say a week ago but are no more in that subnet.Let me observe few collections for a while.Eirik,I do it manually adding direct membership specifying the system either by its netbios name or ip address.Collection update somehow did not work for me.Realtime updation is a dream but the collection update cycle is too long and frustrating.could you please suggest proper adjustments considering my situation
March 9th, 2010 5:46pm

The query I executed for a IP subnet 192.168.32.0 brought in 400 hosts against 30 actual systems to the collection The system property of a system discovered shows - IP Address(0) 192.168.50.245 IP Subnet(0) 192.168.32.0 IP Subnet(1) 192.168.50.0 This system belongs to 50.0 subnet but it came in as it carries reference of 32.0 subnet also. Do i need to specify the mask in the query Can you please suggest a proper query to call in only the systems with 192.168.32.x address range.
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2010 10:41am

As mentioned, this is not a realtime process, so you can not rely on it being precise no matter what query you use. If you say something about why you want it/what these collections are for, then there may be other solutions entirely.
March 10th, 2010 11:17am

I have multiple collections that contain systems from different VLANs/Teams/Subnets in my environment .Based on their subnet I intend to keep my collections updated with the change in system membership .I use these collections for generating several reports periodically.As I told the new systems joining in the subnet do not get assigned to the specified collections based on the criteria I follow.Please suggest.
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2010 12:49pm

As mentioned by Eirik, in order to find your computers in the collection, you must1 - Update informations in db with DDR or inventory data2 - update your collectionIf you absolutly want to automaticly join your client to a collection you must create a application (like a WMI event responder on DHCP) to insert data into SCCM.
March 10th, 2010 1:48pm

I read a guide for SMS/SCCM once where the introduction ended:"Remember, SMS is not a sprint, it's a marathon".This is still very true, and it was not designed for the sort of dynamic behavior that you try to achieve, where computers continously move between collections based on dynamic criteria. You have to work within the limitations of inventories, collection updates and client polling intervals.
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2010 1:49pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics