Skip to main content


Showing posts from September, 2008

dsmod bug when using the –c option?

UPDATE : thanks to some anonymous commenters, i have corrected my example in this post. it seems i left off the trailing %a in the for loop! oops. fixed now. i was visiting up in roanoke extolling about the boundless possibilities with command shells, scripting, etc to a near liability.  in other words, i bored them nearly to death.  :) to my surprise, it stuck.  i’ve been exchanging conversation with one of the site admins and ran across this bug while running through a sample scenario on listing members from one group and adding them to another.  typically, you could do this quite easily with the dsquery tool set. it looks something like this: dsquery group -name "myGroup" | dsget group -members | dsmod group "cn=myNewGroup,ou=etc,dc=etc,dc=etc" -addmbr –c   so what are we doing here? dsquery group –name “myGroup” – retrieves the dn of the group dsget group –members – retrieves the membership list (dn) of the group passed through the pipe dsmod group

verifying replication failure with admp and mom 2005

you’ve no doubt seen this error message if you’re monitoring active directory replication. The following DCs have not updated their MOMLatencyMonitor objects within the specified time period (8 hours). This is probably caused by either replication not occurring, or because the 'AD Replication Monitoring' script is not running on the DC. Format: DC, Naming Context, Hours since last update My-Site myDCserver, NDNC:DC=DomainDnsZones,DC=myDomain,DC=com, 16   typically, this error is generated when a DC is no longer replicating.  the ADMP script watches changes to an attribute called adminDescription.  under the container MOMLatencyMonitors off the root of the watched naming context, exist objects that represent all of the DCs for that naming context. for example: myDCserver, NDNC:DC=ForestDnsZones,DC=myDomain,DC=com, 9   this statement indicates that the domain controller myDCserver has not replicated the required value for 9 hours or more in the naming

restarting services and terminating processes with mom 2005

this particular example is for softgrid.  i thought it might be useful to generalize it for any purpose, though.  you probably already have services that may require a restart every now and then.  that’s pretty easy in mom.  you can do it by issuing a simple net stop && net start command as illustrated in this post . the general perception is that admins are lazy.  to help perpetuate this obvious lie, i tried to use the simple method above but failed.  it turns out that some services don’t terminate the processes upon stopping, as you would expect.  short of trying some ridiculously long for loop statements inside of the batch response, you have to go with a script. i really did consider going with batch script but ended up needing a bit more flexibility.  for instance, instead of blindly going through the cycle, i wanted to make sure we were still in the given condition before we went ahead with it.  to do that, we have to check the process utilization state.  any

troubleshooting device drivers with dpc problems

another little gem.  here’s what you need and some highlights: process explorer kernrate hklm\system\currentcontrolset\services run process explorer open the DPCs property check the performance graph - see if it’s high if it is, run kernrate for 30-60 seconds ctrl-c to escape and view the results the offending item should be at the top or close find the subkey associated with the offending item path is noted above modify the “start” value to 4 in order to disable it.  (at your own risk) thanks to steven daugherty … read the full article in windows it pro.