I’m a huge fan of remotely diagnosing computer issues. If I tell a remote VPN user to bring in their equipment that means there is something terribly wrong with their system.<\/p>\n
I was attempting to use systeminfo \/s IPOFCOMPUTER to check the hotfixes that had been applied and verify the network wasn’t causing issues.<\/p>\n
Loading Network Card Information …ERROR: Provider failure<\/p><\/blockquote>\n
Awesome.
\nAnother site told me to delete the wbem\/repository files as they were probably corrupt. WMI requires these files.
\nIn order to delete them, you must turn off the WMI Service (Windows Management Instrumentation), but I was having difficulty stopping the service remotely via my services.msc connected to their system.<\/p>\nSo I fired up psexec and ran the command lines:
\npsexec -s \\\\computerIP cmd.exe<\/code>
\nnet stop \"windows management instrumentation\"<\/code><\/p>\nI then deleted the files located in:
\nC:\\windows\\system32\\wbem\\Repository<\/code><\/p>\nThen start up the WMI:
\nnet start \"windows management instrumentation\"<\/code><\/p>\nNow I could re-run the systeminfo \/s systemnameorip and it worked like magic.<\/p>\n","protected":false},"excerpt":{"rendered":"
I’m a huge fan of remotely diagnosing computer issues. If I tell a remote VPN user to bring in their equipment that means there is something terribly wrong with their system. I was attempting to use systeminfo \/s IPOFCOMPUTER to check the hotfixes that had been applied and verify the network wasn’t causing issues. Loading … Continue reading Systeminfo Error Provider Failure<\/span>