O R G A N I C / F E R T I L I Z E R: 08.10

Aug 25, 2010

sccm: dcm (desired configuration management) logs

just something to capture dcm logs and their purpose.




  functions of discovery (wql select statements, registry lookup, etc)


  overall dcm agent activity


  activity for managing ci baselines (downloading, accessing, etc)


  activity for managing configuration items (downloading, accessing, etc)


  overall discovery activity (not helpful)


  references loading the sdmdiscagent.xml (not helpful)


  activity regarding non-compliant items that are flagged to log an event (for monitoring use)

i marked the one in red that has the most value.  the others, while useful for showing activity in case you want to know if dcm is even working or not, has very little use outside of that.  i found that discovery.log has most of the magic.  for example, this is a snippet of log entry which indicates the exact query issued to the system:

DiscoveryProvider:Discovery Function query('select Version from cim_datafile where name = "c:\\windows\\vmmreg32.dll"','root\cimv2'): Object count final: 1. 

as you can see, now it's easy to use wbemtest, powershell, wmic, etc to run the query against the system directly to see how it works.  the dcm model verification tool, while cool, doesn't show you this level of detail.

Aug 17, 2010

powershell: generating a range of test users

this was a request for creating 500 user accounts, sequentially numbered.

1..500 | % { new-qaduser -parentcontainer 'OU=myOU,DC=myDomain,DC=COM' -name "MyTestUser$_" -samaccountname "MyTestUser$_" -UserPassword 'MyTestPassword' -email "MyTestUser$_@myDomain.com" }

Aug 4, 2010

opalis: (the real) integration pack help files

some of the best help files are the .chm (compiled html help) files that accompany the IPs.  the release notes are good for cursory information but don't provide a lot of value above that.  if you're looking for them, most are under the client location.

files folder description
oisip*.chm <opalis software>\opalis integration server\client these are the general names of the integration pack help files.
database_configuration.chm <opalis software>\opalis integration server\management service this is not very useful after the initial configuration of the opalis database
oisdeploymentmanager.chm <opalis software>\opalis integration server\management service\console help file for deployment manager

most of your time spent will most likely be in the oisip*.chm files.  they contain the help information and samples respective to each integration pack.  start automating something.

Aug 3, 2010

opalis: how to purge logs

curious how to purge logs from your opalis server?  it's so simple, i'll illustrate it using pictures.




if you're a t-sql person, according to the opalis forums, it's just a stored procedure (sp_CustomLogCleanup).  here's a snippet of how to use it:

Log Purge functionality has three options:

  1. Keep last x number of records
  2. Keep last y number of days.
  3. If records are older than y number of days, keep last x number of records.

These three options dictate how the stored procedure “sp_CustomLogCleanup” is called.  To call the stored procedure in a manner that mimics the Log Purge functionality (but without the hardcoded timeout) you can execute one of the following three scripts in SQL Management Studio where @XEntries is the number of entries to keep and @YDays is the number of days to either keep entries or the number of days to determine when entries should be processed:

Option #1

DECLARE @Completed bit
SET @Completed = 0
WHILE @Completed = 0 EXEC sp_CustomLogCleanup @Completed OUTPUT, @FilterType=1,@XEntries=1000

Option #2

DECLARE @Completed bit
SET @Completed = 0
WHILE @Completed = 0 EXEC sp_CustomLogCleanup @Completed OUTPUT, @FilterType=2,@YDays=7

Option #3

DECLARE @Completed bit
SET @Completed = 0
WHILE @Completed = 0 EXEC sp_CustomLogCleanup @Completed OUTPUT, @FilterType=3,@XEntries=1000,@YDays=7

here's the original thread if you want to read more.