i've marked the relevant lines you need to look for in your schema log. you can check this manually too with the active directory schema snap in (schmmgmt.msc). under classes, locate mSSMSManagementPoint. take a look at the optional attributes. you should see dNSHostName now.<03-30-2006> Modifying Active Directory Schema - with SMS extensions.
<03-30-2006> DS Root:CN=Schema,CN=Configuration,DC=bladerunner,DC=int
<03-30-2006> Attribute cn=MS-SMS-Site-Code already exists.
<03-30-2006> Attribute cn=mS-SMS-Assignment-Site-Code already exists.
<03-30-2006> Attribute cn=MS-SMS-Site-Boundaries already exists.
<03-30-2006> Attribute cn=MS-SMS-Roaming-Boundaries already exists.
<03-30-2006> Attribute cn=MS-SMS-Default-MP already exists.
<03-30-2006> Attribute cn=mS-SMS-Device-Management-Point already exists.
<03-30-2006> Attribute cn=MS-SMS-MP-Name already exists.
<03-30-2006> Attribute cn=MS-SMS-MP-Address already exists.
<03-30-2006> Attribute cn=MS-SMS-Ranged-IP-Low already exists.
<03-30-2006> Attribute cn=MS-SMS-Ranged-IP-High already exists.
<03-30-2006> Class cn=MS-SMS-Management-Point already exists.
<03-30-2006> Located LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=bladerunner,DC=int.
<03-30-2006> Successfully updated class LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=bladerunner,DC=int.
<03-30-2006> Class cn=MS-SMS-Server-Locator-Point already exists.
<03-30-2006> Class cn=MS-SMS-Site already exists.
<03-30-2006> Class cn=MS-SMS-Roaming-Boundary-Range already exists.
<03-30-2006> Successfully extended the Active Directory schema.
[load "*",8,1] : notes, ramblings, contemplations, transmutations, and otherwise ... on management and directory miscellanea.
Mar 30, 2006
sms: sms 2003 sp2 schema extension
Mar 28, 2006
mom: graphing performance in the operator console
- on free megabytes (left pane), right-click and choose properties.
- the first tab of this window is "criteria". click the measured in specified time period.
- click the link in the lower window and specify the time frame for the graph you want.
- click ok.
- choose the items you want to include.
- select draw graph.
mom: heartbeat management
Mar 27, 2006
mom: useless exchange rule
- 4 days = 500,000 events; therefore, the production database is storing 125,000 of these a day.
- 125,000 * 60 = 7,500,000 since the mom warehouse stores 60 days (61 actually... but who's counting?)
Mar 24, 2006
mom: manual agent installations and command-line switches...
Mar 23, 2006
mom: monitoring organizationalUnit changes...
- source: security
- event id: 566
- type: success audit
- description: contains substring organizationalUnit
- parameters: 3,4,9,12
- parameter 3: object type
- parameter 4: object name
- parameter 9: user name
- parameter 12: access
- source: security
- event id: 566
- type: success audit
- description: contains substring organizationalUnit
Directory Service change occurred for: Object: $Parameter 3$ User : $Parameter 9$ Action: $Parameter 12$ Change: $Parameter 4$why? if you let the description field come in to the alert, it's just ugly. no one wants to read it like that. by the way, the parameters won't mean much to you without making this modification to configure the mom agent to resolve the guids it collects in events to friendly names. obviously, you're picking up these events on your domain controllers. yes...
Mar 17, 2006
ds: dsacls is driving me crazy!
No GUID Found for Computer The parameter is incorrect. The command failed to complete successfully.apparently case does matter in some cases (intended). capitalizing Computer causes the output to fail. why? i guess dsacls is case sensitive. it's looking for an object called Computer. switching it to lowercase computer works just fine.
Mar 8, 2006
mom: upgrading to sql 2005
mom: availability reporting doesn't generate reports
os: wmidiag tool finally posted!
Mar 2, 2006
sms: addressing wmi corruption...
i picked up this tidbit from jeff gilbert on the sms mailing list. anyway, there are a few ways to address this if the os of the affect client is windows xp or windows 2003 or greater. here's what he had to say on the matter:
There is help for XP SP1-SP2 and Server 2003, SP1 systems to diagnose and repair WMI corruption: To check the WMI repository for errors on a Server 2003 SP1 system, run the following command from command prompt:
Once you've run that command, check the setup.log file located at: %windir%\System32\Wbem\Logs\Setup.log. Check for entries from today's date. If you find none, then WMI is probably OK and you should continue troubleshooting somewhere else. If however, you see an error message from today saying that it can't find a namespace then yes, your WMI repository does have issues and you should do the below:
- rundll32 wbemupgd, CheckWMISetup
This will re-create your WMI repository minus any custom .mof additions that were implemented without the -autorecover switch. For Windows XP SP2, use the following command to check for corruption, and repair if necessary:
- rundll32 wbemupgd, RepairWMISetup
For Windows XP SP1, the check and repair commands are below and function just like the Windows Server 2003, SP1 commands:
- rundll32 wbemgupgd, UpgradeRepository
- rundll32 wbemupgd, CheckWMISetup
- rundll32 wbemupgd, RepairWMISetup
These are the commands I personally use to try to troubleshoot WMI corruptions. Hopefully they can help you too. Remember to always check that setup.log (%windir%\System32\Wbem\Logs\Setup.log) to see what is going on, and remember that any mof additions compiled without the -autorecover switch will be lost whenever you rebuild your WMI repository!
just keep in mind... the commands above do have a space after the comma. it IS required.