in reply to WindowsRegistry{ServiceName} V.S. wmic{ServiceName} UPDATE: Solved

My first thought was that if it's not in the output of wmic nic list full then you won't get it from wmic, but combined with the info from pKai, it looks like you could piece it together.

When I wmic nic list full there's a suspicious "Index" that (on my computer) goes from 1 to 9. When I go into the registry at pKai's:
LMACHINE/SYSTEM/CurrentControlSet/Control/Class/{4D36E972-E325-11CE-BFC1-08002bE10318}
I see an index from 0 to 8, so I'm guessing that between wmic and the registry you could get at what you're after

I'm wondering, though if there isn't an XY problem here. You seem to be where I am when I get myself into the most trouble very focused, tunnel vision, stubbornly fighting with the computer. Is there a better way to solve the problem your working on? Is the permanent MAC / current MAC something you could let go of and solve a different way? If you gave a little more context, perhaps the Monks here could help with that more.

If this is the only way, then I hope our observations on wmic and the registry help.

I humbly seek wisdom.

Replies are listed 'Best First'.
Re^2: WindowsRegistry{ServiceName} V.S. wmic{ServiceName}
by cmv (Chaplain) on Sep 19, 2007 at 18:16 UTC
    Can I not hide anything from you perlmonk wizards? :-)

    You are correct goibhniu, this is an XY problem, which is why I didn't bother to attach this side issue to the original thread id:639048. I'm actually working on a solution to the original problem, and got stuck on this side issue, trying to understand how to get the hex servicename from the not-hex servicename.

    Given that this whole problem may become moot, I'm still interested in knowing if it is possible to find the hex servicename for something without "hardcoding" a probable path in for it. The vague mists of my memory nag at me that there is a way to do this I once explored, but I can't come up with what it is to save my life.

    Yes, yes, yes, everyones observations on wmic and the registry are helping very much. I apologize if I can't respond to everyone's thoughts, but I am dole-ing out my meager XP points as fast as I'm allowed.

    Thanks to everyone for holding my hand through this uncharted (and spooky) adventure!

    -Craig

[reply]

      I remembered Getting MAC Address(s) on Windows PCs. I wasn't so much thinking that service name was a distraction from finding the two MAC address problem. I was wondering if the two MAC address problem might be hiding another problem. Maybe that makes this an XYZ problem?

      You can hide all you want form perlmonks. We'll try to help anyway. :)

      (total side note here: the way to link to a node is [id://nodeid], not [id:nodeid]. Note the slashes.)

      I humbly seek wisdom.
[reply]
[d/l]
[select]
      this can be done easily if u have the HEX service name with you .... browse thru the registry to HKCR\CLSID\ you will find it there. another way is to go to DCOMCNFG.exe component services\computers\mycomputer\dcom config.
[reply]

In Section Seekers of Perl Wisdom