A Proper OpsMgr 2007 Overrides Report (PowerShell)

Comments
Media
Social

jmacinc wrote: on Aug 29, 2010 11:30 PM

Pete -- thanks for the clean script posting. Maybe you were aware of the "clear-variable" cmdlet, but, as you said, were in a hurry. I found that lingering variables can cause confusion when I'm debugging a snippet after a script has run, so was glad to find that Powershell streamlines this chore if you prefix your var names by common purpose, such as "$override" in this case. Basically:

clear-variable override*

will leave the vars in memory but with null contents in one fell swoop. Gotta love PS.

Permalink | Report Abuse | Edit | Delete

Drew wrote: on Nov 07, 2010 12:26 PM

Write a comment...

Permalink | Report Abuse | Edit | Delete

Drew wrote: on Nov 07, 2010 12:32 PM

Thanks for this Pete, I was hoping to find a script to tweak for our environment versus writing from scratch. Something I added that may help others is conditional logic to make sure the Parameter property is collected so it's not left blank:

$overrideParameter = $override.Parameter

if ($overrideParameter -ne $null)

{

$overrideProperty = $override.Parameter

}

else

{

$overrideProperty = $override.Property

}

Permalink | Report Abuse | Edit | Delete

Add your Comment

Latest Media - View All Media (1)

Who Viewed

Who Reviewed