However, I will use both Windows PowerShell 3.0 and Windows PowerShell 2.0 code so you can test this out for yourself. I do not have the resources to test this out right now, so I cannot report when exactly WMI began reporting wireless keyboards and mice. Bummer.Īt some point, WMI started reporting wireless devices. It only reported the “primary devices” physically connected to the computers. Anyway, at the time, it was not possible to obtain this information because the two WMI classes ( Win32_Keyboard and Win32_PointingDevice) could not detect a wireless device back then. This was for inventory purposes, audit purposes, or maybe general information. One of the things I remember from when I was a consultant is that my customers wanted to be able to know who was using a wireless keyboard or a wireless mouse.
Use WMI to detect wireless keyboard and mouse It does not matter where we meet him because both towns are absolutely lovely. We are in our hotel room right now waiting for his email to detail the plans, and I am sipping an excellent cup of Earl Grey tea-Germany has awesome tea because so much comes through the port of Hamburg. We’ll see him in either Munich or in Regensburg-not sure which town yet. Today, we are supposed to meet with Windows PowerShell Guru Oliver Lipkau. The Scripting Wife and I got to see a lot of our old friends. It was great to be back-as it had been five years since I was in the building. Yesterday, we had a great time at the Windows PowerShell user group meeting at the Microsoft Office in Munich (actually just outside of Munich). Microsoft Scripting Guy, Ed Wilson, is here. Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell and WMI to find a wireless keyboard or mouse attached to a system.
0 kommentar(er)
