{"id":67463,"date":"2006-04-25T16:49:00","date_gmt":"2006-04-25T16:49:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2006\/04\/25\/how-can-i-determine-the-name-of-the-local-computer-using-wmi\/"},"modified":"2006-04-25T16:49:00","modified_gmt":"2006-04-25T16:49:00","slug":"how-can-i-determine-the-name-of-the-local-computer-using-wmi","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/how-can-i-determine-the-name-of-the-local-computer-using-wmi\/","title":{"rendered":"How Can I Determine the Name of the Local Computer Using WMI?"},"content":{"rendered":"

\"Hey, \n

Hey, Scripting Guy! How can I determine the name of the local computer using WMI?

— BM<\/P>\"Spacer\"\"Hey,\"Script<\/A> \n

Hey, BM. As you noted in your email we Scripting Guys always tell people that, in WMI, you can simply use a dot (.) to refer to the local computer. For example, the following mini-script connects you to the WMI service on the local computer:<\/P>

strComputer = “.”<\/p>\n
Set objWMIService = GetObject(“winmgmts:\\\\” & strComputer & “\\root\\cimv2”)\n<\/PRE>\n
Cool, huh? Of course, as you pointed out that\u2019s really only half the story: yes, we can use a dot to refer to the local computer, but what if we need to know the name<\/I> of that computer? When it comes to doing that, when it comes to helping you determine the name of the machine that the dot represents, well, in that case the Scripting Guys haven\u2019t been much help.<\/P>\n\n<\/THEAD>\n\n\n
\n
Note<\/B>. To be honest, it doesn\u2019t really sound like the Scripting Guys to do half a job and then just plain give up on it. Usually we don\u2019t make it even that<\/I> far before giving up on something!<\/P><\/TD><\/TR><\/TBODY><\/TABLE>\n
<\/DIV>\n
Before we go any further we should probably take a moment to address the skeptics in the audience. No doubt some of you are looking at this question and thinking, \u201cSo what\u2019s the big deal here? If the script is running on the local computer, well, then why would you even care about the name of the local computer? And if the script is running remotely, well, wouldn\u2019t you already know<\/I> the name of the computer where the script is running? Wouldn\u2019t you simply set the value of the variable strComputer to the name of that remote machine?\u201d<\/P>\n
The answer to all those questions is the same: maybe. But, then again, maybe not. For example, suppose our code is running as part of a logon script or a computer startup script, and suppose we need to log collected data to a database. In one of those scenarios we need to know the name of the computer. Yes, the script will run just fine by using a dot to represent the computer name, but we can\u2019t rely entirely on the dot; if we do, our database will end up looking something like this:<\/P>\n\n<\/THEAD>\n\n\n\n\n\n\n
\n
Computer<\/B><\/P><\/TD>\n
\n
Number of Processors<\/B><\/P><\/TD><\/TR>\n
\n
.<\/P><\/TD>\n
\n
1<\/P><\/TD><\/TR>\n
\n
.<\/P><\/TD>\n
\n
2<\/P><\/TD><\/TR>\n
\n
.<\/P><\/TD>\n
\n
4<\/P><\/TD><\/TR>\n
\n
.<\/P><\/TD>\n
\n
1<\/P><\/TD><\/TR><\/TBODY><\/TABLE>\n
<\/DIV>\n
Cute, but not too terribly informative. Needless to say, a table like this would be a bit more useful:<\/P>\n\n<\/THEAD>\n\n\n\n\n\n\n
\n
Computer<\/B><\/P><\/TD>\n
\n
Number of Processors<\/B><\/P><\/TD><\/TR>\n
\n
atl-ws-01<\/P><\/TD>\n
\n
1<\/P><\/TD><\/TR>\n
\n
atl-fs-02<\/P><\/TD>\n
\n
2<\/P><\/TD><\/TR>\n
\n
atl-dc-03<\/P><\/TD>\n
\n
4<\/P><\/TD><\/TR>\n
\n
atl-ws-04<\/P><\/TD>\n
\n
1<\/P><\/TD><\/TR><\/TBODY><\/TABLE>\n
<\/DIV>\n
Likewise there might be times when we do<\/I> need get the computer name when dealing with remote machines. With WMI you can connect to a remote computer by specifying the computer name; however, you can also connect to a remote computer by specifying an IP address:<\/P>
strComputer = “192.168.1.1”<\/p>\n
Set objWMIService = GetObject(“winmgmts:\\\\” & strComputer & “\\root\\cimv2”)\n<\/PRE>\n
Because very few of us have memorized the IP addresses of all our computers (and because, thanks to DHCP, many of these IP addresses are wont to change anyway) a table like is also only marginally useful:<\/P>\n\n<\/THEAD>\n\n\n\n\n\n\n
\n
Computer<\/B><\/P><\/TD>\n
\n
Number of Processors<\/B><\/P><\/TD><\/TR>\n
\n
192.168.1.1<\/P><\/TD>\n
\n
1<\/P><\/TD><\/TR>\n
\n
192.168.1.2<\/P><\/TD>\n
\n
2<\/P><\/TD><\/TR>\n
\n
192.168.1.3<\/P><\/TD>\n
\n
4<\/P><\/TD><\/TR>\n
\n
192.168.1.4<\/P><\/TD>\n
\n
1<\/P><\/TD><\/TR><\/TBODY><\/TABLE>\n
<\/DIV>\n
In other words, even in this high-tech day and age of ours something as old-fashioned as a name can still come in handy. (Which sounds funny coming from a group that hides behind the collective moniker \u201cThe Scripting Guys,\u201d doesn\u2019t it?)<\/P>\n
So can we use WMI to determine the name of the local computer (or, say, a remote machine where all we know is the IP address)? You bet we can. And when we tell you that there are hundreds and hundreds of different ways to do that, well, we aren\u2019t kidding. For example, suppose you have a burning desire to use the Win32_BIOS<\/B> class to determine the computer name. Hey, why not:<\/P>
strComputer = “.”<\/p>\n
Set objWMIService = GetObject(“winmgmts:\\\\” & strComputer & “\\root\\cimv2”)<\/p>\n
Set colItems = objWMIService.ExecQuery(“Select * From Win32_BIOS”)<\/p>\n
For Each objItem in colItems\n    Wscript.Echo objItem.Path_.Server\nNext\n<\/PRE>\n
As you can see, this is a standard WMI script, one that binds to the WMI service on the local computer. We then use this line of code to retrieve BIOS information for that machine:<\/P>
Set colItems = objWMIService.ExecQuery(“Select * From Win32_BIOS”)\n<\/PRE>\n
Why did we pick the Win32_BIOS class? No reason; we could have picked any<\/I> WMI class. That\u2019s because each and every WMI class returns an SWbemObjectPath object; the Path_<\/B> property for that object serves as the unique address for the item in question. For example, the Path_ to the BIOS on a computer might look something like this:<\/P>
\\\\ATL-WS-01\\root\\cimv2:Win32_BIOS.Name=”EPP runtime BIOS – Version 1.1 “, \nSoftwareElementID=”EPP runtime BIOS – Version 1.1 “,SoftwareElementState=3,\nTargetOperatingSystem=0,Version=”HP     – 22110520”\n<\/PRE>\n
That path is unique: no other object on the computer atl-ws-01 will have that same path. <\/P>\n
As you can see, the name of the computer (ATL-WS-01) is embedded in the beginning portion of that path. (Which makes sense: not including the name of the computer in the path would be about as useful as having an address of 111 Main Street that didn\u2019t include the name of the city.) Admittedly, we could do some fancy string manipulation in order to try and tease out the computer name from the path. Or, we could simply ask for the value of the Server<\/B> property, like we do here:<\/P>
For Each objItem in colItems\n    Wscript.Echo objItem.Path_.Server\nNext\n<\/PRE>\n
It\u2019s that easy. And, best of all, any WMI object you get back from a script will include an SWbemObjectPath object and the Server property. Are you already using the Win32_ParallelPort class to connect to a machine? That\u2019s fine; while you\u2019re there you can get the value of the Server property using Win32_ParallelPort:<\/P>
strComputer = “.”<\/p>\n
Set objWMIService = GetObject(“winmgmts:\\\\” & strComputer & “\\root\\cimv2”)<\/p>\n
Set colItems = objWMIService.ExecQuery(“Select * From Win32_ParallelPort”)<\/p>\n
For Each objItem in colItems\n    Wscript.Echo objItem.Path_.Server\nNext\n<\/PRE>\n
Connecting to a machine using the Win32_PrinterConfiguration class? Then you can get at the value of the Server property using Win32_PrinterConfiguration. Connecting to a machine using the Win32_LogicalDisk class? Then you can get at – well, you get the idea.<\/P>\n
But what if you don\u2019t like all this talk of SWbemObjectPaths? Well, in that case you can always rely on the Win32_ComputerSystem class to get the computer name:<\/P>
strComputer = “.”<\/p>\n
Set objWMIService = GetObject(“winmgmts:\\\\” & strComputer & “\\root\\cimv2”)\nSet colItems = objWMIService.ExecQuery(“Select * From Win32_ComputerSystem”)<\/p>\n
For Each objItem in colItems\n    Wscript.Echo objItem.Name\nNext\n<\/PRE>\n
That works just fine; it\u2019s just nowhere near as cool as using the Win32_TimeZone class to determine the computer name. And just think of how many bar bets you\u2019re likely to win now; after all, from here on you\u2019ll be able to walk into a crowded bar and tell people, \u201cGive me the name of a WMI class – any WMI class – and I\u2019ll use just that class<\/I> to determine the name of a computer.\u201d If people aren\u2019t impressed by that then maybe they aren\u2019t worth impressing.<\/P>\n
We hope that answers your question, BM. After all, we Scripting Guys take pride in our motto: Leave no job undone. We don\u2019t necessarily live up to that motto, mind you. But we do take pride in it.<\/P>
\n
\n\n\n\n
\"Top<\/A>Top of page<\/A><\/TD><\/TR><\/TBODY><\/TABLE><\/DIV><\/p>\n","protected":false},"excerpt":{"rendered":"
Hey, Scripting Guy! How can I determine the name of the local computer using WMI?— BM Hey, BM. As you noted in your email we Scripting Guys always tell people that, in WMI, you can simply use a dot (.) to refer to the local computer. For example, the following mini-script connects you to the […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[3,4,5,6],"class_list":["post-67463","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-scripting-guy","tag-scripting-techniques","tag-vbscript","tag-wmi"],"acf":[],"blog_post_summary":"
Hey, Scripting Guy! How can I determine the name of the local computer using WMI?— BM Hey, BM. As you noted in your email we Scripting Guys always tell people that, in WMI, you can simply use a dot (.) to refer to the local computer. For example, the following mini-script connects you to the […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/67463","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=67463"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/67463\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=67463"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=67463"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=67463"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}