Hi,

you can always pipe a | get-member to get the properties and functions of an object, however this is not always a complete list.

So, if you run something like:
$MP = get-managementpack -name "My.MP"
$override = ($MP | get-override)[0]
$override | get-member
You get a bunch of properties and functions.

In your case, you want to find an Override's target, which differs from the different override types. If it's a monitor Override there's a Monitor property but the value is ManagementPackElementReference.
$override.Monitor

Won't show you much, but the Reference has a function called GetElement()
$override.Monitor.GetElement()
This outputs the monitor.

The target of an Override is configured in Context (Class like Windows Computer) and Context Instance (Class Instance like your.machine.in.your.domain.com). Context is also only a ManagementPackElementReference but with GetElement() you'll get it as well.

$override.Context.GetElement()

Contextinstance is a GUID I think, can't verify that now though.

But, it's not undocumented, you can either import the SDK assemblies and check them out with the Object Browser of Visual Studio or you can download the SDK docs from MIcrosoft: http://www.microsoft.com/downloads/details.aspx?FamilyID=a16bd9c0-55a4-4a65-ba7f-f876158be0c3&displaylang=en

Thank you both, this is very close to what I was attempting to craft on my own. However, I do wish the inventory script would output everything to one file instead of many. Any chance you can suggest how to append those csv files into a single spreadsheet?

Thanks for calling me "great", dude... I am embarassed now :-)

Tom, I agree that this script would be even better if the output were redirected to a single file and with a bit of additional formatting. Since I actually need this script tomorrow morning, and Daniele did all the hard work for us already (thanks Daniele!), what you and I need is a quick change. Here are the changes I made to his script.

• Added logic to store the output of all the packs in a single variable 
• Added the -notypeinfo flag to rid the output of the type info line on each pass, which is garbage for our purposes
• Added an extra column to include the name of the management pack the override is stored in
• Moved the override name to the far right column. The name string is so long and unruly it clutters the report

If you look at the code, you'll basically see I am simply passing the output of the inner foreach loop to a variable outside the loop so we can store it up for output to a single csv file.  

Not perfect, but should meet the need here. I have attached a copy of the updated script. Login to the site and download from my post. I'll put it to the Downloads section tomorrow.