Re: What part of SMS inventories the OU-path for computers?
- From: "Mathias" <maha.nospam@xxxxxxxxx>
- Date: Mon, 5 Feb 2007 13:12:26 +0100
I've solved my problem it seems.
I didn't understand that the System Group Discovery *only* discovers data for the computers in in its own site even if you point out the top of the Active Directory as search path for each site.
Clients in other sites than the site running the SGD aren't detected/added until the SGD is run for that particular site That is why our clients didn't get their OU-path in SMS until the discovery was run for that particular site. Pretty logical in the end.
/M
"Mathias" <maha.nospam@xxxxxxxxx> wrote in message news:%2383dx%23MSHHA.4832@xxxxxxxxxxxxxxxxxxxxxxx
Can anyone duplicate my problem or is there something wrong with my AD System Group discovery cycle?
To sum it up:
1) Computer gets SMS client
2) System Group disc. cycle is run
3) It takes a long time for the OU-path to appear connected to the client in SMS.
Thanks,
Mathias
"Mathias" <maha.nospam@xxxxxxxxx> wrote in message news:OvBkDWIRHHA.4744@xxxxxxxxxxxxxxxxxxxxxxxRight now, we have installed the SMS-client to a computer named U004-0031. It appears in SMS as assigned to a site and with a client. At the moment I can find it in the table System_DISC with ItemKey 36300, but the ItemKey 36300 has no match in System_System_OU_Name_ARR yet. In other words, I can't filter in or out this computer based on SMS_R_System.SystemOUName.
My reason to do this is because we have different company branches in different OUs. We don't want to push out MS-patches to one specific branch, hence the filtering. The bad thing here is that the computer takes a number of hours to appear in the right collection because the filtering is done on SMS_R_System.SystemOUName and therefore we can't send programs to this computer until it appears in the collection.
What I need help with here is to identify how I can speed up the process of populating the table System_System_OU_Name_ARR.
/Mathias
"Mathias" <maha.nospam@xxxxxxxxx> wrote in message news:%23y%23wXhFRHHA.920@xxxxxxxxxxxxxxxxxxxxxxxWe were. :-) I was just wondering wheter or not the OU-path was inventoried for non-SMS clients.
Let me clarify. The computers have been in the AD for long but haven't had SMS-clients until now. They have been visible in SMS all the time as Unassigned and without Client. After the SMS-client installation they appeared in SMS as "Client = Yes" and "Assigned = Yes" within an hour. The OU-path wasn't added to the computer until four hours later even though we run the System/Group-discovery every hour.
Regards,
Mathias
"Kim Oppalfens <MVP>" <Kim dot Oppalfens@google mail.com> wrote in message news:OzWkuYFRHHA.5032@xxxxxxxxxxxxxxxxxxxxxxxAd system group discovery indeed only works for clients assigned to the site, sorry for not specifying but I thought we were talking sms clients.
If you need this for non-clients you might want to take a look at the enhanced system discovery plugin.
--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System SMS - MVP
"Mathias" <maha.nospam@xxxxxxxxx> wrote in message news:OtCop3ERHHA.4088@xxxxxxxxxxxxxxxxxxxxxxxHi Kim, thanks for helping out (again!).
We run the System Group Discovery once every five hours on five Primary Site Servers as well (should get into SMS every hour in other words...). The computers that got the sms-clients have been in AD for months so you'd think that the OU-path would be in SMS by now. Or does SMS only add this information to computers with SMS-clients?
Regards,
Mathias
"Kim Oppalfens <MVP>" <Kim dot Oppalfens@google mail.com> wrote in message news:F9F43F2C-DDA8-4851-91BC-B895DA7CE0DF@xxxxxxxxxxxxxxxxI should re-verify but I thought this info came from System group discovery.
--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System SMS - MVP
"Mathias" <maha.nospam@xxxxxxxxx> wrote in message news:ufYguH7QHHA.2172@xxxxxxxxxxxxxxxxxxxxxxxHi! My question is at the bottom, but here's the event that lead up to it:
I had 500 computers without SMS-clients already inventoried by SMS. I then installed the SMS-Client on these computers via a logon script. All computers appeared in SMS within an hour which they should since I run the 'Active Directory System Discovery' method every five hours on five Primary Site Servers so information should be collected into SMS every hour. All nice and well so far. Here's the part which I can't comprehend - I have a Collection that filters computers based on OU memership. My new computers didn't appear in this collection, not even after multiple update/refreshs, so I manually queried the SMS SQL-DB ( SYSTEM_SYSTEM_OU_NAME_ARR/SYSTEM_OU_NAME0. ) The information for which OU each computer wasn't in there which explained why my collection-query didn't work.
It took four hours for this information to eventually get into the DB eventually. I thought this information was also inventoried by the "Active Directory System Discovery" method that runs every hour?
How come this information didn't appear in SMS until four hours later? When and how does SMS collect this information as it doesn't seem to be a part of the ordinary Active Directory System Discovery method?
Regards,
Mathias.
.
- References:
- Prev by Date: Re: What part of SMS inventories the OU-path for computers?
- Next by Date: Re: ITMU Options
- Previous by thread: Re: What part of SMS inventories the OU-path for computers?
- Index(es):
Relevant Pages
|
Loading
