SCCM 2007 R2 - Advertisement required to constantly poll AD for new devices

We have the SCCM 2007 R2 environment with Active Directory System Discovery turned on in addition to Heartbeat discovery.

I have reduced the polling interval for the Computer Client Agent within Site Settings - Client Agent to 30 mins to enable clients to be discovered quickly when they are joined to the domain.

However in addition to the above, I was thinking of creating an open ended advertisement to poll AD every 5 mins or so for new machines that get added to the domain.

Is there a way of doing this?

Also I am unable to find the MS System Centre zone to post this question - hence posting in IT Admin
tedcbeAsked:
Who is Participating?
 
merowingerCommented:
You do not have to configure the Advertisement to run every five minutes. If a Client has not executed it yet it will run as soon as the client gets it.
You have to make sure that the Advertisement is mandatory. Also make sure the Membership Schedule of the Collection where the Advertisement is linked to, is set to run every X minutes/hours.

Try this one :)
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Systems_Management_Server
0
 
KezziCommented:
If you install R3 it comes with dynamic updating so you can set your AD imports to discover dynamically every 5 min.  only if it detects a change will it run the import so it wont hammer your infrustructure.  you can have collections dynamically updating as well if youre using queries.
0
 
merowingerCommented:
@Kezzi: Great addition
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
tedcbeAuthor Commented:
The issue is even though we are licensed to use R3 on the servers, we can only use R2 on the clients. Hence we have decided to stick to R2 throughout the estate both on servers and clients.
0
 
KezziCommented:
You can have R3 on the servers without the clients neededing that update.  i didnt know R3 had a seperate licensing as our volume license covers it all.

The only thing that wont benefit you from avoiding upgrading the clients, is power management but the R3 features on the server side will definitely help you with what you are doing.  
0
 
tedcbeAuthor Commented:
thanks for your update Kezzi and merowinger.

If we do decide to update our servers to R3 and keep our clients at R2, will there be any reporting issues like in SMS 2003.

We've had SMS 2003 till a few months back and had issues with reporting total physical memory and processor information because the servers were SMS SP3 and clients were SMS SP2.
0
 
merowingerCommented:
Not as i know.
0
 
KezziCommented:
with R3 it gives  you the option to add a reporting services role which will be either your SQL server or local if SQL express is used.  You then have the option to subscribe to the reports, essentially moving the reports over to reporting services.  As long as you dont do that, you shouldnt have a problem with reporting that i can think of.  All my Servers are R3 but not all my clients are R3 and I have no issues reporting off them.
0
 
tedcbeAuthor Commented:
thank you kezzi and merowinger.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.