Tip: Windows internals using wmi

[Tim Golden]

"Colin Brown" <cbrown at metservice.com> wrote in message news:<3f831c27 at news.iconz.co.nz>...
> Thanks for your comments Tim. Sadly I find myself in the same position
> as yourself with regard to need and time to investigate this further.
> 
> I note that there is a third article in WMI Scripting Primer's:
> 
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnclinic/ht
> ml/scripting06112002.asp
> 
> which states:
> "Modifying the Properties of a Managed Resource
> In Windows 2000, WMI is primarily a read-only technology. Of the 4,395
> properties defined in the Windows 2000 root\cimv2 namespace, only 39
> properties are writeable. Those numbers improve in Microsoft® Windows® XP,
> where 145 of approximately 6560 properties are writeable. And the numbers
> get even better in Windows Server 2003."
> 
> It appears to be evolving technology, currently targetted more at inspection
> than management!
> 
> Colin Brown
> PyNZ

Interesting indeed. Further investigation 
(which I *really* didn't have the time to do!) 
threw up several articles by Microsoft which 
talked about having to compile / set something 
up / register COM services / other arcane stuff 
in order to use the Registry provider. 

I can't lay my hands on the URL (and it would 
have changed by the time you read this) but it
put me off somewhat -- also, I can't understand
why they didn't just build it in from the start:
it's not as though the Registry is some little-used
backwater of the Operating System!

If you come across anything useful, or find the
energy to get something working with this, let me 
know.

Thanks. TJG