Microsoft Windows (English and Japanese):

• 11

• 10

  Note	See Windows 10 in ASDM Compatibility Notes if you have problems with the ASDM shortcut.

• 8

• 7

• Server 2016 and Server 2019

• Server 2012 R2

• Server 2012

• Server 2008

Yes

No support

Yes

8.0 version 8u261 or later

1.8

Apple OS X 10.4 and later

Yes

Yes

Yes (64-bit version only)

8.0 version 8u261 or later

1.8

ASDM Launcher compatibility with ASDM version

"Unable to Launch Device Manager" error message.

If you upgrade to a new ASDM version and then get this error, you may need to re-install the latest Launcher.

1. Open the ASDM web page on the ASA: https://<asa_ip_address>.

2. Click Install ASDM Launcher.

   

3. Leave the username and password fields empty (for a new installation), and click OK.

   With no HTTPS authentication configured, you can gain access to ASDM with no username and the enable password, which is blank by default. When you enter the enable command at the CLI for the first time, you are prompted to change the password; this behavior is not enforced when you log into ASDM. We suggest that you change the enable password as soon as possible so that it does not remain blank. Note: If you enabled HTTPS authentication, enter your username and associated password. Even without authentication, if you enter a username and password at the login screen (instead of leaving the username blank), ASDM checks the local database for a match.

Self-signed certificate not valid due to a time and date mismatch with ASA

ASDM validates the self-signed SSL certificate, and if the ASA's date is not within the certificate's Issued On and Expires On date, ASDM will not launch. If there is a time and date mismatch, you will see the following error:

To fix the issue: Set the correct time on the ASA and reload.

To check the certificate dates, (example shown is Chrome):

1. Go to https://device_ip.

2. Click the Not secure text in the menu bar.

3. Click Certificate is not valid to open the Certificate Viewer.

4. Check the Validity Period.

Windows Active Directory directory access

In some cases, Active Directory settings for Windows users may restrict access to program file locations needed to successfully launch ASDM on Windows. Access is needed to the following directories:

• Desktop folder

• C:\Windows\System32C:\Users\<username>\.asdm

• C:\Program Files (x86)\Cisco Systems

If your Active Directory is restricting directory access, you need to request access from your Active Directory administrator.

Windows 10

"This app can't run on your PC" error message.

When you install the ASDM Launcher, Windows 10 might replace the ASDM shortcut target with the Windows Scripting Host path, which causes this error. To fix the shortcut target:

1. Choose Start > Cisco ASDM-IDM Launcher, and right-click the Cisco ASDM-IDM Launcher application.

2. Choose More > Open file location.

   Windows opens the directory with the shortcut icon.

3. Right click the shortcut icon, and choose Properties.

4. Change the Target to:

   C:\Windows\System32\wscript.exe invisible.vbs run.bat

5. Click OK.

OS X

On OS X, you may be prompted to install Java the first time you run ASDM; follow the prompts as necessary. ASDM will launch after the installation completes.

OS X 10.8 and later

You need to allow ASDM to run because it is not signed with an Apple Developer ID. If you do not change your security preferences, you see an error screen.

1. To allow ASDM to run, right-click (or Ctrl-Click) the Cisco ASDM-IDM Launcher icon, and choose Open.

   

2. You see a similar error screen; however, you can open ASDM from this screen. Click Open. The ASDM-IDM Launcher opens.

   

Requires Strong Encryption license (3DES/AES) on ASA

ASDM requires an SSL connection to the ASA. You can request a 3DES license from Cisco:

1. Go to www.cisco.com/go/license.

2. Click Continue to Product License Registration.

3. In the Licensing Portal, click Get Other Licenses next to the text field.

4. Choose IPS, Crypto, Other... from the drop-down list.

5. Type ASA in to the Search by Keyword field.

6. Select Cisco ASA 3DES/AES License in the Product list, and click Next.

7. Enter the serial number of the ASA, and follow the prompts to request a 3DES/AES license for the ASA.

• Self-signed certificate or an untrusted certificate

• IPv6

• Firefox and Safari

When the ASA uses a self-signed certificate or an untrusted certificate, Firefox and Safari are unable to add security exceptions when browsing using HTTPS over IPv6. See https://bugzilla.mozilla.org/show_bug.cgi?id=633001. This caveat affects all SSL connections originating from Firefox or Safari to the ASA (including ASDM connections). To avoid this caveat, configure a proper certificate for the ASA that is issued by a trusted certificate authority.

• SSL encryption on the ASA must include both RC4-MD5 and RC4-SHA1 or disable SSL false start in Chrome.

• Chrome

If you change the SSL encryption on the ASA to exclude both RC4-MD5 and RC4-SHA1 algorithms (these algorithms are enabled by default), then Chrome cannot launch ASDM due to the Chrome “SSL false start” feature. We suggest re-enabling one of these algorithms (see the Configuration > Device Management > Advanced > SSL Settings pane); or you can disable SSL false start in Chrome using the --disable-ssl-false-start flag according to Run Chromium with flags.