Collection based on logged in PC's? 2

[cstowell]

I have recently gotten SMS up and running and I am currently trying to resolve some of the client installation issues as I run across them. I have GP's in place to drop the firewall and am running scripts to force on the administrative shares.

To help troubleshoot the clients which for one reason or another just will not get the client I thought I could make a collection consisting of just the machines without the client installed that also happen to be currently logged into the network.

Anyone have and idea whether this is feasible or not? I have the sql code for the Non-client machines already, I just need the code for the currently logged in PC's or the appropriate attribute class and attribute upon which to query. If anyone has a resource that goes into more detail about exactly what each of the attribute classes do and how best to use them that would be greatly appreciated.

Thanks in advance!

 

[tbrennans]

You cant really do that as a sms client will only inventory who was the last logged on person or who was logged on the last time an inventory was run. So if you inventory once a week it will show you who was logged on up to last week, but it doesnt do realtime updates, if it did your network would be swamped with inventory deltas.

What is your installation method? Personally I like using gpo machine script to install the client.

 

[ncotton]

If you have push installation enabled, make sure you have enabled heartbeat discovery, and set it to like once an hour, if they dont install that way, then you have a bigger problem.

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[cstowell]

I was afraid of that. There are a few dozen machines that won't take the client and I wanted to get them all into single collection to narrow down the list of "active machines" but machines without the client.

I have the heartbeat set to 4 hours but I will reduce it to see if it helps. The number of machines without the client goes down a few per day so I guess thats progress.I am only using AD system / AD group discovery /hearbeat to target a few specific OU's for testing and evaluation.

I guess the problem relates more to my limited rollout, I haven't enabled client push yet. I have been pinging live machines and forcing the the client install individually from the collection to work out installation issues before I just let it loose.

Thanks a lot for the help!

 

[ncotton]

Really, if you enable client push, it will only "let loose" on machines that are a) detected/discovered and appear in your All Systems Collection, and are b) Assigned, any machines that aren't detected or are detected but not assigned, you dont have to worry about recieving the client, if you are worried about overstepping the boundaries of your SMS juristiction.

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant