Our article focuses on resolving the Device Descriptor Request Failed (Unknown USB device) issue in a timely manner, no matter what caused it. The issue at hand can be caused by either hardware or system-specific problems. This is a problem when you’re trying to use things such as a USB flash drive, memory card, Android device, game controller, or anything that plugs into your USB port. When you encounter this error message, you’re essentially told that the computer is unable to use the specific USB device connected. One of these common issues is the “ Unknown USB Device (Device Descriptor Request Failed) ” error that shows up in the Device Manager. TblNetworkAdapter.Windows 10 Home users have been reporting issues when connecting and using a USB device on their computer. When tblNetworkAdapter.Name Like 'DisplayLink%' Or When tblNetworkAdapter.Name Like 'Lenovo%' Then 'Lenovo' When tblNetworkAdapter.MACAddress Like '6C:0B:84%' Then 'Lenovo USB-C Gen 2' When tblNetworkAdapter.MACAddress Like '48:2A:E3:85%' Then When tblNetworkAdapter.MACAddress Like '48:2A:E3:7D:5C%' Then When tblNetworkAdapter.MACAddress Like 'E0:4F:43%' Then 'Lenovo USB-C Gen 1' TblNetworkAdapter.Name Like '%TBT%' Then 'Lenovo Thunderbolt 3 Gen 1' When tblNetworkAdapter.MACAddress Like '00:50:B6%' And When tblNetworkAdapter.MACAddress Like '3C:E1:A1%' Then When tblNetworkAdapter.MACAddress Like '08:3A:88%' Then It's not bulletproof, but it's better than nothing. We use a network interface report and try to infer the dock based on the client machine's network adapter MAC or adapter name. We use Lenovo and Alogic now, they pass-through the connections. I believe we had some docks at some point that could be configured to report their IP/MAC as well as the machine that they were connected to (Microsoft Surface maybe?). I think this depends a lot on the dock itself, most docks pass through the network connection. Not sure how this could hook into lansweeper as custom reporting, but it should technically be possible as it scans WMI objects. If someone could get this working properly as an array that combines this output with the computer name as a custom PSObject, then at least I could run this on demand to get the asset serial numbers. The hideous results of that is the best i've gotten so far for scanning all notebooks, and if I remove the -ExpandProperty Name to try to get the invoke-command to display which computer its listing, it breaks the scirpts ability to run through each computer. Invoke-Command -ScriptBlock -ComputerName $notebooks $notebooks = Get-ADComputer -SearchBase 'ou=Notebooks,dc=your,dc=domain,dc=com' -Filter * -Properties Name | Select -ExpandProperty Name It seems like the dell command demands the list of computer objects to act on at the end of the command. I am stuck between whether I need to learn how to use arrays better in powershell and whether the dell command objects can even work properly with the syntax i'm attempting. I have tried and failed at multiple powershell attempts to return a nice bulk export csv when scanning the entire network. The Dell docking stations cannot be detected by the chassis in Lansweeper and I have found that Dell Inventory Agent is a required install for the WMI objects to be detected as a "dock" and return an identifier and serial number. Adding my journey in trying to scan dell docking stations to this most recent post.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |