OU based query fails for SMS 2003 clients in CM07 (Full Version)

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



Message

mlindgren -> OU based query fails for SMS 2003 clients in CM07 (9/26/2008 2:58:03 AM)

We have an old image with the SMS 2003 sp2 client in it. When this image is installed, everything works great, except that it is not possible to create a query based on OU membership with the newly installed SMS 2003 client. Seems like the System group discovery is not working as expected when updating DDR´s created for the SMS 2003 client. The problem goes away when upgrading to CM 07. Someone else that experienced this problem?

Site server is CM 07 sp1/R2.



jnelson993 -> RE: OU based query fails for SMS 2003 clients in CM07 (9/26/2008 10:46:48 AM)

I'm not following the correlation between the image and the OU discovery.

If the client is installed fine and returning HW/SW inventory, then that part is probably fine.  If you're not getting OU values for any of these new machines, that's a function of system discovery.  Are you only discovering in a certain AD container?



mlindgren -> RE: OU based query fails for SMS 2003 clients in CM07 (9/29/2008 11:11:38 AM)

Thanks for the reply,

I´m only running System group and system discovery in the OU´s that contains the computer accounts, because that should be enough, right?



jnelson993 -> RE: OU based query fails for SMS 2003 clients in CM07 (9/29/2008 11:40:55 AM)

Well, to determine the OUs, you need Active Directory System Group Discovery.

Also, this discovery has to be done on the site that the reporting point gets it's data from.  For example, we have a central administration site where all our management happens, but we have another primary server above it that acts as the reporting point as well.  If we don't turn on discovery on THAT server then we won't see anything because that discovery data stays at the site in which it's enabled and doesn't trickle up.  So it's not enough to have it on for the child primaries, turn it on for the site where the reporting point is getting the data.

So, if both of those things are happening, then perhaps the machines in question aren't in the OUs that you think they are.  Can you turn on ADSG discovery for the root container or for the whole domain and make sure RECURSIVE is checked?



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.1875