Run Device Manager From Cmd
Honorato Overmyer
I connect remotely and the user enters their password. I open the device manager from the right-click on the start menu. Windows warns me that it's logged in as a standard user, but I can still open up the properties pop-up for any device. On that properties window it's mostly read-only but there's the security access button for Change Settings. When I click that it reloads the properties window editable - to click the Update Driver button, for example - but at that point my remote session does not have any control over the reloaded window. I can see the new window just fine, and I can still control other items on the remote system.
Is this a familiar problem to anyone? Do I need to back up and open the device manager itself in some way with elevated permissions? Do I need to prompt for the user to enter something within the remote desktop session so I can have control of that properties window?
What I am looking for is a command that I can use which will show the device manager inside of the prompt. Or is there a command which will show me what is in the device manager? I cant think of a intelligent way to ask that last sentence. What I mean is if I want to see what type of video card is on a computer I could use a command that will show just the display adaptors part of the device manager. Or a command which will show just the Network adaptors.
Or does anybody think I am going about obtaining this information the wrong way? Does anybody know of a better way to get the device manager information on a remote computer without taking control away from the user?
I have wondered if I could simply put a script of some sort onto the remote computer (lets say in the program files folder) and using the powershell browse to that location and run the script. Would this work?
The place where I work the users are a little touchy about me using their computers. Even when there is an issue for me to fix that they asked me to fix. The more I can do remotely with Powershell the easier my life will become. Every time I read an article about advice for young/new/noob IT people such as myself there is always the mention of the power of Powershell. I am trying to figure out exactly how powerful Powershell is by using it as much as possible.
I would suggest maybe not trying to delve into a huge thing like this unless the rewards show enough benefit that it makes sense to spend that kind of time sifting through the various hardware classes.
I have a serial to USB device and more than one of those can be connected to the computer. I need to query and retrieve a list of COM ports that the devices are connected to. In Windows Device Manager you can get the COM port + friendly name of devices that are connected at the present time. This list is dynamic.
I had to solve a similar issue just some weeks ago. I came accross the Jawin-Project that provided everything you need to use WMI-Queries. It is already quite old but works like a charm if you follow the documentation. A nice German walkthrough can be found codegods blog.
For me, it did not solve all problems (I had some very specific things to find out about the target device), I finally created an own JNI (Java Native Interface) Class and DLL in C incorporating the windows API.
I am looking at Java Native Access as it provides access to the windows API from pure Java code - no JNI to deal with. I was concerned about the LGPL license; whether it can be included in a commercial product but from what a few posts in the newsgroup say, it can be. After I try it out in the next few weeks, I shall post back here.
To start Device Manager, you can launch the Start Menu search functionality and search for "Device Manager". Alternatively, in File explorer, select and hold (or right-click) This PC, select Manage, and then select Device Manager from the System Tools that are listed in the resulting dialog.
If your device is required to start the computer, a problem with your device installation can prevent the computer from starting. In these cases, you have to use the kernel debugger to troubleshoot your device installation. For more info, see Getting Started with WinDbg (Kernel-Mode).
If your device isn't required to start the computer, if there's a problem with your device, Device Manager places a yellow exclamation point next that device's name in the Device Manager dialog. Device Manager also provides an error message describing the problem. For more information about the error messages, see Device Manager Error Messages.
Device Manager provides detailed information in the Properties dialog for each device. Select and hold (or right-click) the name of the device, and then select Properties. The General, Driver, Details, and Events tabs contain information that can be useful when you debug errors. For more information, see Device Manager Details Tab.
I've seen similar errors posted but I think mine is a little different. I'm new to Cisco, and was given an ASA 5505 to configure. I intended to do a factory reset, but ended up running an erase, which of course wiped everything out.
If you don't have the files you expect in place, look at what is there. If there are corresponding versions of ASA and ASDM on there, update the config to use them - this will allow you to access ASDM and you can upgrade via that if necessary. If there are multiple versions, start with the oldest ones first.
Another useful troubleshooting step is to connect a console cable to the ASA, get a console session up, and watch the output when booting - the ASA will report errors during the boot process, but you won't see them if you ssh in. Many errors will result in an ASA that functions, just not as expected.
If you formatted your device you need to upload the ASDM image as well as the ASA825 image. You can probably get it from your hardware dealer. Make sure you have the correct ADSM version as well, designed for your ASA release.
Recent versions of Java seem to break the connection to older versions of the firmware. The recommended "fix" from Cisco is to upgrade to a newer version - which is really convenient for them since this requires an active support contract for the device in question (ie it costs money).
1.) Open your Java Control Panel (for example by launching "Configure Java" in your start menu)2.) Go to the Advanced tab3.) Scroll down to Advanced Security Settings4.) Locate option "Use SSL 2.0 compatible ClientHello format5.) Enable this option by setting the checkbox6.) Restart your Java environment. Make sure you have ASDM closed. If in doubt, or if you have instances of ASDM hung in your Taskmanager, reboot your PC.
In my case the support contract for an older ASA 5505 is actually more expensive than throwing it in the trash and buying a new device from scratch. Go figure. So I'll be using a downgraded Java version instead.
I understand that supporting products costs money, but making it so expensive that it completely breaks common sense and becomes more expensive than a new device is just - frankly - plain stupid. I will be limping along with my current device using an old Java version, and stay well clear of Cisco devices in the future.
Since no one else seems to have offered the following, I will even though it is an old post it seems to be still helpful and active:You have enabled http/https access but you need to finish that setup by adding the IP address for your workstation to the "Management Access" list. I have found this to be the corrective action on multiple ASA5505 units for clients as well as my own.
Its not the ASA or ASDM. If you do not have proper certificate, it will not work. Open Control Panel, Java and add the site certificate as Trusted. If you are using temp Cert, you will need to do this every time ASA Reboots.
Regarding the behavior you described, we would like to provide you with the steps below; however, we recommend first confirming that the Wireless and Bluetooth devices are enabled in the BIOS. (Please contact the computer manufacturer for instructions on how to check this on the BIOS).
On your keyboard, press the Windows logo key and type and then select Identify and repair network problems in the list of search results to run the network troubleshooter. The network troubleshooter will automatically detect the network problems on your PC. You just need to follow the steps in the network troubleshooter and see if this issue can get fixed.
If the issue persists after trying the steps above, we recommend contacting your computer manufacturer directly for further support. For instance, It may be needed to perform a restore from a system restore point or to physically inspect the wireless network card (it may need to be reset or check if there are hardware issues).
*Links to third-party sites and references to third-party trademarks are provided for convenience and illustrative purposes only. Unless explicitly stated, Intel is not responsible for the contents of such links, and no third-party endorsement of Intel or any of its products is implied.
64591212e2