Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Discovery\New Collection Issue?

Status
Not open for further replies.

NetAdminII

IS-IT--Management
Aug 9, 2004
3
US
My SMS 2003 Setup:
-SMS installed on Windows 2000SP4 with SQL2000 on same box
-Advanced Security
-One primary site created (i.e. SMS-Companyname)
-configured primary site boundaries to use site created in AD

I executed an AD system discovery based on the root domain of AD. Under all systems in collections, I see all of my computers in the company. If I select any of the additional collections, the computers are listed in the correct collection. (i.e., XP machines and Servers)

Here are my problems:
1. Computers were discovered even though they do not belong to the AD site configured in the boundary. Why would this be?

2. Not all the the settings were detected. For instance, I would like for it to discover the OU, Operating System, and other information if possible.

3. When I try to create a new collection, (called Test), I go to membership rules and try to configure a query statement based on an OU that the computers belong to. However, when I add the criteria as follows:
criteria type: Simple Value, Where: System Resource -System Group Name, Operator: is in, and nothing appears when I select the Values Tab.

Your help would be appreciated.
 
Well I am a complete idiot and after playing around with the program a little longer, I figured out most of my problems.

For anyone who is interested,

ISSUE #2-3 - To resolve, all I had to do was the AD System Group Discovery in order for the OU settings to be detected and registered in the DDR. Once they were registed, it resolved issue number 3. The OU values appeared and the collection worked.

Issue #1 - The reason all computers were found despite the boundary was because I did the AD system discovery which lists all servers in my company regardless of site.

If anyone has or had the same problem and needs help, please reply and I will assist.
 
Join v_RA_System_SystemOUName, via ResourceID, and use
System_OU_Name0.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top