Skip to main content


Showing posts from June, 2006

ds: add conditional forwarders by command line

sometimes i think it's relevant to follow your own advice. of course, some lessons aren't learned by sedulous effort. often times, it requires moments of sheer languor. rtfm, rtfm, rtfm i tell myself! if you want to add conditional forwarders through command line, use this: dnscmd [servername] /zoneadd [] /forwarder [primary ip address] [secondary ip address] the /forwarder statement is actually expressing what zone type you want (e.g. primary, secondary, etc). using /forwarder tells dnscmd that you're interested in adding conditional forwarders. this stuff rocks. by the way, this is only available on 2003 or later. here's the tfm if you're looking for all the details.

mom: sp_helpdb - cannot insert the value null into column

been getting any of these errors? the system stored procedure sp_helpdb, which is used to gather information about the databases, has returned an error that may indicate that it cannot determine the db owner for the database [databasename]. here are the details: sp_helpdb @dbname='databasename' on sql server instance: [instancename]. error number: 515, error information: [microsoft][odbc sql server driver][sql server]cannot insert the value null into column '', table ''; column does not allow nulls. insert fails. this generally occurs when there's no owner specified for the database. executing this query will tell you if that's the case: select name, suser_sname(sid) from master.dbo.sysdatabases where suser_sname(sid) is null if indeed it does show up in this query, using sp_changedbowner will fix it. this will assign sa as the owner (make sure to change the database to the one you need to correct): exec sp_changedbowner 'SA'

mom: dell openmanage mp has been updated

it's been about a year since their last release so i'm sure there must be some improvements. i'm profiling the management pack in mpstudio now to see how it looks. by the way, you won't find it yet on the mom catalog, but you can get it here: . by the way, germany scored in the ecu v ger game in the first 5 minutes. wow!

ds: machine account password interval

you're probably familiar with default machine account password reset intervals: nt 4: 7 days 2000 & above: 30 days some additional details on this came through on the list. it's pretty cool so i thought i'd share for those that aren't subscribed. unfortunately the author of this information doesn't a blog (yet). does, however, maintain archives of the list. :) i'd link you... but that section seems unresponsive right now. at any rate, here's a snippet of the post. these are the logs generated during success, failure and offset. success: 05/25 14:48:22 [SESSION] NORTHAMERICA: NlChangePassword: Doing it. 05/25 14:48:22 [SESSION] NORTHAMERICA: NlChangePassword: Flag password changed in LsaSecret 05/25 14:48:23 [SESSION] NORTHAMERICA: NlChangePassword: Flag password updated on PDC 05/25 14:48:23 [MISC] NlWksScavenger: Can be called again in 30 days (0x9a7ec800) failure: 05/16 01:13:24 [SESSION] NORTHAMERICA: NlChangePasswor

mom: looking for a training class?

i have a hard time recommending a training class for mom. this is because, historically, microsoft official curriculum sucks. the information is too vague, not very timely, and doesn't discuss real-world issues. there's a new offering that looks very promising and has had some excellent reviews. i've looked over the syllabus. it looks very complete. it's a 4-day crash course on everything you need to know about mom and will bring your level of understanding much higher than what the MOC class could ever do. it's also taught by mom consultants and know their ... stuff. anyway, there's a class coming up in Atlanta! maybe i'll see you there. here's the details .

mom: tracking down duplicate notifications

while i was out at teched, a reader sent me an email on how to track down duplicate notifications. this was pretty fresh in memory since i had just gone through the same ordeal explaining to another group here why they received duplicated emails. now that i have the exact details at my disposal, i can relay them here with some manner of lucidity. (i hope anyway. still trying to get back into work mode ... and for some reason, someone brewed the old, nasty corporate coffee instead of the new, aromatic seattle's best. ah well...) the first thing to do is find the alert in the mom console. once you've isolated it, check the history tab of the alert. you might see something similar to this: Alert is created in management group myMgmtGroup. === 6/01/2006 08:20:03 === The server side response 'notify group: Network Administrators' triggered by rule 'Send notification for any Alerts with a severity of "Error" or Higher' ( DF7DA784-D7D8-4FC5-8109-04AB0

os: i can't see the interactive cmd shell

i think i tried 5 times in a row to get cmd.exe to show up as an interactive window. just for reference, if you're trying this, the command would looking something like this: at HH:MM /interactive cmd.exe right? looks right. this will spawn a cmd shell alright. you'll see it in the processes. you won't be able to access it. why is this? it turns out that the interactive switch is indeed true. you have to be logged on at the console. rdp, terminal services, etc... they won't show it. good news is, if it's 2003, you can connect to the console session using this command: mstsc /v:[servername] /console :)

mom: all notifications for a server

pretty quick and easy. didn't even believe that it would work since it seems to defy logic (at least mine). apparently it does. once i set it up, i realized why. here's the steps: create a new rule group. create a computer group (or use an existing one). populate the computer group with the computers you want alerts for. associate the computer group to the rule group. create an alert rule. only match alerts generated by rules... should be unchecked. add a severity criteria if you want. setup a notification response. i've no doubt you're smarter than me, but entertain me for a bit and let me explain. the alert rule in this case, is not bound to work for rules of any given rule group. therefore, the alert rule is generic and applies to anything that matches its criteria.

mom: some details about mom 2005 summary reporting

get this… since the day summary reporting was rolled out, the dts package has never successfully completed. i’m talking 6 months. so, for 6 months, mom has been force fed data from the systemcenterreporting database. for those of you that may not know, summary reporting is an add-on that aggregates data points in the reporting warehouse database. by using this system, you can effectively reduce the size of your warehouse. this is by no means a comprehensive guide. just some things discovered along the way. more information is in the accompanying guide that comes with the download . to get started, here are the stored procedures that can be executed to change the behavior of summary reporting pack: exec p_setweekstartday [value] [value] is 1-7 (sunday through saturday, respectively) exec p_setcutoffdate [yyyy-mm-dd] exec p_setsamplegroomdays [value] [value] must be greater than 7 exec p_setalertgroomdays [value]