



bat files setting JAVA_HOME then execute ASDM-IDM Launcher - etc. I thought I would have to play games with finding old JRE6 32bit ( load it in addition to the latest JAVA ( 8 )) and create. That seems to let the "session" have the correct cached software - (actually you can pop to different devices if they are running same versions) I just created different "IE Favorties" and start over for each device of different version software. If you have different versions of ASDM sent from the devices you may get errors popping back and forth in the upper left device list. Then just use the links ( I used I.E 11 ( not Microsoft "edge" ) just because)Įven with the java exception defined you have to tell java "Security Warning" pop up "Continue" every time - no "always trust"Īllow caching of software from each device->Ģ devices = "Cisco ASDM-IDM Launcher v1.5(46)" - ASDM 6.2F for FWSMġ device = "Cisco ASDM-IDM Launcher v1.5(49)" - ASDM 6.3 for FWSM New Windows 10 Java 8u72 both 32 and 64 ( no jre 6 involved )Ĭontrol Panel -> Java ( yes 8 ) -> add above link to security tab exception
