How do I know that SMS 2003 is working?

[mijohnst]

I've run a discovery on my AD domain and it's been going for about 30 minutes and I don't see anything being collected in the default collection groups. I've checked my event logs and I see no errors and also under "Site Satus" and everything looks peachy...

Does it just take that long to discover machines? I thought I could view some by now.

 

[Jpoandl]

- Right click Collections, and choose REFRESH

or

- Right click Collections --> ALL TASKS --> Update Collection Membership


(Maybe your MMC is just not refreshed)

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[mijohnst]

Thank you Joseph. I did the "update Collection Membership" and now I have small hourglasses on each collection group. So far though I only see the server that's running SMS... Shouldn't it be pickuping up everything on the domain as it comes in?

 

[Jpoandl]

What mode are you in? Advanced Security Mode? Did you update the AD schema for SMS 2003 during your install?



Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[Jpoandl]

Here's some information for you. I suspect your SMS site boundaries are not configured properly:

http://myitforum.techtarget.com/articles/8/view.asp?id=6697

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[mijohnst]

I'm in Advanced Security Mode. I've looked at the MMC for Schema and checked the box to allow changes. Did I skip something?

 

[Jpoandl]

You can check AD to see if the schema updates are in place. Here is some documentation on how to do this (it is very easy...don't worry)

BASIC VERIFICATION OF INFORMATION

If you want to ensure that the information published in AD contains the actual site specific information, here’s what you can do. Use a tool called ADSI edit. It allows viewing of the values associated with various Active Directory classes. This tool is available in the support folder for Windows 2000. More information on the tool is at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;246926

Once you load the MMC Snap-in, you’ll navigate to the CN=System Management container, expand it, then right click on your CN=SMS-MP-<sitecode>-<MPcomputerName> and choose Properties. Drop down the list of “Select a property to view” and scroll to the “msSMS…” items. Ensure that:



msSMSDefaultMP is TRUE

msSMSMPName is <MPcomputername> (Whatever that machine name is)

msSMSSiteCode is <sitecode>


Now, select the CN=SMS-Site-<sitecode> object in the System Management container. Open the properties, and drop down the property list. Ensure it has:



msSMSAssignmentSiteCode = <sitecode>

msSMSRoamingBoundaries = <ADsite or subnets>

msSMSSiteBoundaries = <ADsite or subnets>

msSMSSiteCode = <sitecode>


As a matter of reference, there are two separate processes on the SMS Site server that publish information into Active Directory. They are Hierarchy Manager (a thread of SMS_EXECUTIVE process) and Site Component Manager. If the publishing process appears to have failed, review hman.log or sitecomp.log file located in \sms\logs\ folder.

ADVANCED VERIFICATION OF PUBLISHED DATA

Assume that you have a primary site and a secondary site with an MP assigned for each and roaming boundaries as well as site boundaries of all three types define for each site. This would mean you have a total of 12 boundaries:



Three roaming boundaries for primary site

Three roaming boundaries for the secondary site

Three site boundaries for primary site

Three site boundaries for the secondary site


You will want to verify the following:



For the primary site's sms-site-sitecode object in AD:

- The msSMSAssignmentSiteCode and mSSMSSiteCode values should be the primary site code

- The msSMSRoamingBoundaries value should contain both the primary and secondary site's site boundaries and roaming boundaries.

- The msSMSSiteBoundaries value should contain the only the primary site's site boundarires.


For the secondary site's sms-site-sitecode object in AD:

a. The msSMSAssignmentSiteCode should be the parent site code

b. The msSMSSiteCode value should be the secondary site code

c. The msSMSSiteBoundaries value should be the secondary site's standard site boundaries.

d. The msSMSRoamingBoundaries value should be blank.


Verify there is a IP address range object sms-sitecode-LowIPAddress-HighIPAddress for the two ranges added.

Verify both range objects list the parent site code in the mSSMSSiteCode and mSSMSAssignmentSiteCode values.

Verify the secondary site AD object starts has the parent site code in the object name and not the secondary site code (Eg: if the parent is S01 and secondary is S02 then the object name will be SMS-S01-lowIP-highIP

Verify the mSSMSAssignmentSiteCode and mSSMSSiteCode values for both objects are the parent's sitecode.

Verify the mSSMSRangeIPHigh and mSSMSRangeIPLow values are correct.

http://myitforum.techtarget.com/articles/8/view.asp?id=6324

http://myitforum.techtarget.com/articles/8/view.asp?id=6715

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[mijohnst]

I must have done something wrong because msSMSDEFAULtmp and msSMSMPName is not listed. I bet that's my whole problem. I wonder why is wasn't added and how I'd go about getting them in there.

I see that it's already pulled in my users and groups to the collection so at least that's something positive...