WMI Object Identifiers and Keys

Microsoft news and tips » WMI Object Identifiers and Keys

Microsoft news and tips » WMI Object Identifiers and Keys — Tue, 15 Apr 2008 16:44:38 GMT

PingBack from http://microsoftnews.askpcdoc.com/?p=2530

re: WMI Object Identifiers and Keys

Will Irwin — Tue, 15 Apr 2008 23:25:55 GMT

Doesn't work for me (PS on 64-bit Vista, or on 32-bit XP).

$c=[wmiclass]"win32_logicaldisk"

gives me an object of type System.Management.ManagementClass#ROOT\cimv2\Win32_LogicalDisk (per get-member), but $c does not have a member called "Properties".

re: WMI Object Identifiers and Keys

PowerShellTeam — Wed, 16 Apr 2008 00:51:29 GMT

These demos are all using the V2 CTP syntax. If you want to do the same thing on V1, just put the term "psbase." in front of "properties" . e.g. instead of $c.Properties you'll type $c.psbase.Properties

Jeffrey Snover [MSFT]

Windows Management Partner Architect

Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell

Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

Windows PowerShell Automation Doubt?

kuttappanPro — Wed, 16 Apr 2008 09:30:57 GMT

Using IActiveScriptSite and CcmdTarget we can write our own script engine

for parsing VBscript code.

like wise How we can write powershell script parsing engine

using VC++ automation or other technology?

re: WMI Object Identifiers and Keys

RADagenais — Wed, 16 Apr 2008 22:11:57 GMT

Why are you posting V2 syntax when the current version is v1.

IMO this really diminishes your credibility.

I have clients coming to me with scripting problems that I know I could do great things in Powershell with, but this whole pushing version 2 before version 1 is even broadly adopted thing is keeping me from taking you guys seriously.

The v2 stuff should be on the sidelines for now, and the general public stuff should be focused on v1.

You guys are getting carried away and leaving the flock behind. Gazillions of us are just starting to bring PS1 into our production environments. SLOW DOWN

And while we're at it, can we fix the bugs in v1 (like missing -LiteralPath in set-acl, and -Path balks at brackets).

re: WMI Object Identifiers and Keys

Chris Federico — Thu, 17 Apr 2008 06:48:45 GMT

RADagenais (or whatever they call you )

This is a Blog and they can post whatever they feel like . Try going to the Powershell usergroup and posting this stuff over there . Maybe ask nicely and people will definitely help you .

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.powershell&cat=en_US_3750E87B-4971-4A5C-A537-45F5D7ABBECC&lang=en&cr=US

Chris

re: WMI Object Identifiers and Keys

RADagenais — Thu, 17 Apr 2008 22:10:26 GMT

I'm sorry if I was rude. I enjoy the blog.

But I think its a valid point. The whole parade to v2 seems a little ahead of things.

My comment is addressed to Microsoft in general, this being the main blog for PS by MS.

My remark about the set-acl bug is irrelevant tho.

-Rich

re: WMI Object Identifiers and Keys

BosReg — Fri, 18 Apr 2008 22:50:19 GMT

Will v1 scripts using psbase. still work correctly in v2?

re: WMI Object Identifiers and Keys

BosReg — Fri, 18 Apr 2008 23:35:43 GMT

If a class has more than one key property, you must specify all of them for this to work:

PS> Get-WMIKey Win32_Environment

Name

UserName

PS> $pp = '\root\cimv2:Win32_Environment.Name="Path",UserName="<SYSTEM>"'

PS> [wmi]$pp

VariableValue Name UserName

------------- ---- --------

F:\Oracle\product\10.1.... Path <SYSTEM>

re: WMI Object Identifiers and Keys

PowerShellTeam — Sat, 19 Apr 2008 05:40:01 GMT

> Will v1 scripts using psbase. still work correctly in v2?

Correct.

jps

re: WMI Object Identifiers and Keys

Matt Thompson — Fri, 23 May 2008 19:43:51 GMT

Hello Team!

Loving Powershell, findint what can be done with ADSI and WMI great but not without its problems. As such I'd like to ask a question. (Appreciate this is probably not the normal place to ask but I am finding it hard to get information on WMI)

I understand there maybe a bug in V2 where System.Management.ManagementBaseObject (or possibly an array of this object) is treated incorrectly in Powershell.

Can you confirm if this is correct?

(see here for info on this http://www.vistax64.com/powershell/79129-wmi-network-adapter-speed.html - I raised this here for further information to https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=345762)

Thanks,

Matt