Axon Commander Installation Guide

Transcription

1 Axon Commander Installation Guide Axon Commander Version 4.14 Release Date: July, 2018 Document Revision: A

2 Apple, ios, and Safari are trademarks of Apple, Inc. registered in the US and other countries. Firefox is a trademark of The Mozilla Foundation registered in the US and other countries. Google, Google Play, Android, and Chrome are trademarks of Google, Inc. Microsoft, Azure, Windows, Internet Explorer, and Excel are trademarks of Microsoft Corporation registered in the US and other countries. Javascript is a trademark of Oracle America, Inc. registered in the US and other countries., Axon, Axon Body, Axon Body 2, Axon Capture, Axon Commander, Axon Dock, Axon Flex, Axon Flex 2, Axon View, Evidence.com, Evidence.com Lite, Evidence Sync, and TASER are trademarks of Axon Enterprise, Inc., some of which are registered in the US and other countries. For more information, visit All rights reserved Axon Enterprise, Inc. Axon Enterprise, Inc. Page 2 of 77

3 Table of Contents System Requirements and Firewall Permissions... 5 Server Hardware Requirements... 5 Client Hardware Requirements... 5 Firewall Ports... 6 Create Local Users... 8 Permit the Application on Windows Firewall (Optional) Add Inbound Rules Add Outbound Rules Install.NET 3.5 Framework (Windows10 and Server 2016 Only) Install and Configure Axon Commander Install Microsoft SQL Server Automatic Install of SQL Server (Recommended) Manual Install of SQL Server (Advanced) Install and Configure Axon Commander Install Axon Commander Configure Axon Commander Database Activate the Axon Commander Software License Configure Axon Commander Server Access Configure Client Access for Axon Commander Configure Windows Firewall (Optional) Domain Settings (Optional) Axon Commander Language Settings (Optional) Verify the Axon Commander Installation Install and Configure Axon Camera Extractor (Optional) Add Certificate Snap-in Import SSL Certificate Install Axon Camera Extractor Configure Axon Camera Extractor DNS Settings Axon Enterprise, Inc. Page 3 of 77

4 Installing DNS Server on Microsoft Windows Server Configuring DNS Zone with Windows Server Configuring DNS Zone with Simple DNS (For Test Installations Only) Axon Dock Configuration Axon Commander Advanced Settings Axon Device Firmware Updates Axon Commander Software Updates Third-Party Player Storage Add a Third-Party Player Edit Third-Party Player Information Delete a Third-Party Player Configuring Axon Commander and Milestone XProtect Update to Latest Milestone Device Pack Installing Axon Commander, Axon Camera Extractor, and Wowza Configuring Wowza Configuring Axon Commander Cameras Configuring Windows Firewall Configuring Milestone XProtect Axon Commander Troubleshooting Terminology Issues Dock communication error Server login issue or general malfunctions: Revision History Axon Enterprise, Inc. Page 4 of 77

5 System Requirements and Firewall Permissions Axon Commander is the World's leading on premise digital evidence management system. This guide provides information on how to install the application on the server of your choice. Server Hardware Requirements The following table outlines the hardware and software requirements for the server portion of an Axon Commander installation. This is the system that will store and manage a department s evidence. Minimum Recommended Processor 1x Quad-Core Intel Xeon E3 (1.7 GHz) 2x Quad-Core Intel Xeon E5 (2.66 GHz) Memory 1 8 GB RAM ECC 16 GB RAM ECC Internal Drive GB HDD 256 GB SSD Network 10/100 Ethernet Gigabit Ethernet Video Integrated Graphics Monitor SVGA (800 x 600) WXGA (1024 x 768) Operating System Windows Server 2008 R2 Windows Server 2012 R2 SQL Database SQL Express 2008 SQL Express Error Code Correction (ECC) memory is encouraged to maximize system reliability. 2 Relates to storage for Axon Commander Server and Operating System. It does not include recommended drive for evidence storage. Client Hardware Requirements The following table outlines the hardware and software requirements for Axon Commander Client. This is the system that is used to access and view the evidence, that is stored on a department s central server. Axon Enterprise, Inc. Page 5 of 77

6 Minimum Recommended Processor Intel Core i3-530 (2.93GHz) Intel Core i (3.4 GHz) Memory 4 GB RAM 8 GB RAM Internal Drive 1 80 GB HDD 120 GB SSD Network 10/100 Ethernet Gigabit Ethernet Video Integrated Graphics 256MB Dedicated Graphics (x16 PCI-Express Card) Monitor WXGA (1024 x 768) UXGA (1600 x 1200) Operating System Windows 7 Optical Media 16x DVD+/-RW Drive 1 Relates to storage for Axon Commander Server and Operating System. It does not include recommended drive for evidence storage. Firewall Ports The following ports are required to be open on Axon Commander installations. Please take note of the ports required for the Server and for the Clients. Axon Commander Server Type Name Protocol Port Outbound Axon Commander - Beacons UDP 8881 Inbound Axon Commander Transporter (v1) Protocol TCP 8896 Axon Enterprise, Inc. Page 6 of 77

7 Inbound Axon Commander Transporter (v2) Protocol TCP Inbound Axon Commander Web Server TCP Axon Commander Client Type Name Protocol Port Outbound Axon Commander Transporter (v1) Protocol TCP 8896 Outbound Axon Commander Transporter (v2) Protocol TCP Outbound Axon Commander Web Server TCP File Sharing (if Applicable) In some instances, the client, server, and network attached storage systems may connect through a firewall. In these instances, it is important to ensure ports are open for file access. The network storage configuration can vary depending on configuration. However, for most systems using Windows File Sharing (via SMB) the following settings might be required. Type Name Protocol Port Inbound Direct Hosted SMB TCP 445 Outbound Direct Hosted SMB TCP 445 SQL Server (if Applicable) Depending on the configuration and location of the SQL server and your agency s firewall, some special configuration might be required to ensure communication with the Microsoft SQL server. If the SQL Server is installed on the same machine as the Axon Commander server, firewall configuration is not typically required. If your server configuration results in the Axon Commander server and SQL server being on separate machines that pass through a firewall, then refer to the Configure the Windows Firewall to Allow SQL Server Access article from Microsoft to understand how to best determine and manage your port requirements. Axon Enterprise, Inc. Page 7 of 77

8 Axon Dock (if Applicable) Type Name Protocol Port Outbound Axon Dock HTTPS TCP 443 Outbound Axon Dock Time Synchronization TCP 80 Create Local Users Local users are required to install and configure Axon Commander. Axon recommends creating two local users, one with administrator access and one that has read-only access. The local administrative user account needs to be able to access folders and assign permissions within Windows during installation. While the user that configures client access only requires the read-only access. 1. Open the Computer Management console. a. From the Start menu, click Control Panel, click System and Security, and then click Administrative Tools. b. Double-click Computer Management. 2. From the left navigation pane, under System Tools, select Local Users and Groups. 3. Right-click User and then select New User. The New User dialog box appears. Axon Enterprise, Inc. Page 8 of 77

9 4. Enter a user name and password that conforms to your agencies policies. Note: If you want the user to change their password when they log in, click the User must change password at next logon checkbox to select it. 5. Click Create and then click Close. 6. From the navigation pane, click Users. 7. Double-click the user you created. The properties dialog box for the user appears 8. Click the Member Of tab and then click Add. The Select Groups dialog box appears. 9. In the Enter the objects name to select text field, enter the local administrator group and then click Check Names. Axon Enterprise, Inc. Page 9 of 77

10 Note: Verify that the user is added to admin group of local domain. 10. Click OK. 11. Repeat steps 3 5 to create the local user with read-only access. Note: Ensure the administrative user has read-write access to the network (UNC) paths for all storage locations and ingestion directories, and that the launcher user only has read-access to all the network (UNC) paths. Permit the Application on Windows Firewall (Optional) For Axon Commander to communicate with and through its various dependencies, certain ports need to be opened. You can manually add rules to open the ports for Axon Commander or, optionally, you can let Axon Commander Server Setup automatically configure your Windows firewall. Before starting, determine the ports you need to open for inbound and outbound rules, see Firewall Ports on page 6 for more information. Note: Optionally, if Axon Commander is installed in a closed system, the firewall can be disabled completely. Add Inbound Rules 1. From the Start menu, click Control Panel, click System and Security, and then click Windows Firewall. 2. In the left navigation pane, click Advanced settings. The Windows Firewall with Advanced Security window appears. 3. In the left navigation pane, click Inbound Rules, and then in the Actions pane, click New Rule. The New Inbound Rule Wizard dialog box appears. Axon Enterprise, Inc. Page 10 of 77

11 4. On the Rule Type page, click Port and then click Next. 5. On the Protocol and Ports page, select TCP and Specific local ports. Enter the port numbers into the Specific local ports field. Protocol Port Port Use TCP 8896 Transporter (v1) communication TCP Transporter (v2) communication TCP Web server communication 6. Click Next. 7. On the Action page, select Allow the connection and then click Next. 8. On the Profile page, select the Domain, Private, and Public checkboxes, and then click Next. 9. Enter a name and, optionally, a description for the Inbound rule, and then click Finish. 10. Repeat steps 3-9 for all other Inbound rules. Add Outbound Rules 1. In the Windows Firewall and Advanced Security navigation pane, choose Outbound Rules, and then in the Actions pane, choose New Rule. The New Outbound Rule Wizard dialog box appears. Axon Enterprise, Inc. Page 11 of 77

12 2. On the Rule Type page, click Port and then click Next. 3. On the Protocol and Ports page, for each Outbound rule, select the appropriate protocol and select Specific remote ports. Enter the port number into the Specific local ports field. Protocol Port Port Use UDP 8881 Sending beacons TCP 8896 Transporter (v1) communication TCP Transporter (v2) communication TCP Web server communication (required to download the Axon Commander executable for initial installation) 4. Click Next. 5. On the Action page, select Allow the connection and click Next. 6. On the Profile page, select the Domain, Private, and Public checkboxes and click Next. 7. Enter a name and, optionally, a description for the Outbound rule, and then click Finish. 8. Repeat steps 1-7 for all other Outbound rules and any special requirements identified in the Firewall Ports section. 9. Close the Windows Firewall with Advanced Security window. Axon Enterprise, Inc. Page 12 of 77

13 Install.NET 3.5 Framework (Windows10 and Server 2016 Only) Axon Commander and SQL Server have a dependency on the existence of the Microsoft.NET 3.5 Framework. Typically, this framework is included with all Microsoft operating systems. However, starting with Windows 10 and Server 2016, the.net 3.5 Framework is not installed by default. If you are installing the Axon Commander Server or SQL Server 2014 on a system that uses either of these operating systems, you must perform one of the following options: Option 1 (Recommended): Enable the functionality using the Windows Control Panel by taking the following actions: o Press the Windows key ( ) on your keyboard, type Windows Features, and press Enter. The Turn Windows features on or off dialog box appears. o Select the.net Framework 3.5 (includes.net 2.0 and 3.0) check box, click OK, and then reboot your computer if prompted. If you are unable to install.net Framework 3.5 using Option 1, try to use one of the following options: Option 2: If running Server 2016 and your agency is not using Windows Server Update Services (WSUS), then.net 3.5 Framework can be obtained using the standard Windows Update as follows: o Open a command prompt with administrator user rights (Run as Administrator). o Install.NET Framework 3.5 feature files from Windows Update using the command: dism.exe /online /enable-feature /featurename:netfx3 /all Axon Enterprise, Inc. Page 13 of 77

14 o Option 3: If running Windows 10 or Server 2016 with WSUS configured, you will need access to a Windows 10 or Server 2016 installation DVD/ISO. If you do not have access to a DVD/ISO, it can be downloaded once from Microsoft at: Install.NET 3.5 Framework as follows: o o o If you downloaded the Windows 10 ISO, use Windows File Explorer to find the file, right-click on the file, and then select Mount. Note the drive letter Windows assigned to the ISO (example D:/). Open a command prompt with administrator user rights (Run as Administrator). Run the following DISM command to install.net 3.5 Framework. When typing the command, replace /Source:d with the drive letter on which the ISO or DVD is mounted. For example, if it was mounted as E drive, then the field should be /Source:e DISM /Online /Enable-Feature /FeatureName:NetFx3 /Source:d:\sources\sxs /All /LimitAccess Install and Configure Axon Commander The following section will walk the user through the installation procedure to install and configure Axon Commander, along with its required dependencies. 1. Extract the Axon Commander setup file. 2. Right-click on the Launcher.exe file and select Run as Administrator. Axon Enterprise, Inc. Page 14 of 77

15 3. Once the Axon Installation Launcher appears, select the software you want to install by selecting or clearing the appropriate checkboxes. Note that.net Framework is a dependency for Axon Commander as well as a SQL Server instance. If the launcher detects a dependency as being already installed, the Launcher will automatically deselect it from the installation procedure. 4. Once the required selections are made, click Install to begin the installation process. Install Microsoft SQL Server Axon Commander uses SQL for data management, such as indexing files, and retrieving data, but not storing videos. Note: The Axon Installation Launcher includes Microsoft SQL Server 2014 Express. However, users may opt to install a later version of SQL Server Express, or their own instance of Microsoft SQL Server Standard. SQL Server is only required for Commander installations and SQL is not required for Axon Camera Extractor. Automatic Install of SQL Server (Recommended) 5. If the Microsoft SQL Server 2014 Express checkbox was enabled, the installer will automatically configure and install the SQL Server in the background. The user will be presented with the following interface. Once the installation of SQL server is complete, the installer will proceed to the next required software package. Axon Enterprise, Inc. Page 15 of 77

16 Manual Install of SQL Server (Advanced) Should it be required to manually install SQL server, the following steps are provided to guide the installer through the installation procedure. The steps below were created using Microsoft SQL Server 2014 Express. However, these instructions will scale to any supported version. 1. Run the SQL Server 2014 setup file by right clicking the SQL Server 2014 executable file and selecting Run as Administrator. 2. In the SQL Server Installation Center, click New SQL Server stand-alone installation or add features to an existing installation. Axon Enterprise, Inc. Page 16 of 77

17 3. On the SQL Server 2014 Setup License Terms page, accept the license agreement and click Next. 4. On the Microsoft Update page, optionally, select Use Microsoft Update to check for updates and click Next. 5. On the Feature Selection page, accept the default settings and click Next. Axon Enterprise, Inc. Page 17 of 77

18 6. On the Instance Configuration page, select Named instance and change the name from SQLExpress to Commander. The Instance ID automatically changes. 7. Click Next. 8. On the Server Configuration page, click the Collation tab. Axon Enterprise, Inc. Page 18 of 77

19 9. In the Collation tab, click Customize. The Customize SQL Server Database Engine Collation dialog box opens. 10. On the Customize SQL Server Database Engine Collation dialog box, select Windows collation designator and sort order, then set the Collation designation to Latin1_General, and then select Accent-sensitive. Axon Enterprise, Inc. Page 19 of 77

20 11. Click OK to save the settings and close the Customize SQL Server Database Engine Collation dialog box. You are returned to the Server Configuration page. 12. On the Server Configuration page, click Next to continue with the installation. 13. On the Database Engine Configuration page, select Mixed Mode and enter your password in both the Enter password and Confirm password fields. 14. Click Next 15. On the Feature Configuration Rules page, click Next. The installation begins and progress is shown. The installation takes a few minutes to complete. Axon Enterprise, Inc. Page 20 of 77

21 16. When the installation is complete, click Close. Install and Configure Axon Commander Axon Commander Checkup is where you configure the inner workings of the Axon Commander application. Install Axon Commander 1. In the Axon Installation Launcher window, click Next to start the Setup Wizard. The license agreement dialog box appears. 2. In the License Agreement dialog box, accept the license agreement and click Next. 3. In the Choose Setup Type dialog box, select Typical and click Install. 4. After the installation process finishes, click Finish. The Commander Server Checkup window appears. Axon Enterprise, Inc. Page 21 of 77

22 Configure Axon Commander Database 1. In the Commander Server Checkup window left navigation pane, click Server Setup. 2. In the Set up your Commander Server pane, click Run Database Wizard to locate the SQL Server instance and configure the database. The Commander Database Deployer window appears. 3. If are using the default database source, go to step 4. If you are not using the default database source, in the Commander Database Deployer window, click the browse button to locate the database source. Axon Enterprise, Inc. Page 22 of 77

23 In the Choose a Data Source dialog box, select the SQL server created in the SQL Server installation procedure and click OK. 4. In the Commander Database Deployer window, click Next. 5. In the Commander Database Deployer window, click Create a new Commander Database, and click Next. 6. The Asset directories dialog box is used to set the directories for your Axon Commander databases. You can choose to use the default database settings or configure the information yourself. To use the default settings, click Create default configuration to have Commander Database Deployer automatically create the specified base directory (default is C:\Videos) and a few subdirectories. Axon Enterprise, Inc. Page 23 of 77

24 Note: Axon Commander requires a few paths for storing files. You can use another drive for the base directory. However, when changing the path to the base directory, only change the letter do NOT change anything else. To configure the directories yourself, click the Advanced tab, enter the New directory paths, and then click Save. 7. Click Finish. The Commander Database Deployer window closes. Axon Enterprise, Inc. Page 24 of 77

25 Activate the Axon Commander Software License 1. In the Set up your Commander Server pane, click Run License Wizard. The Commander Licenser window appears. 2. In the Commander Licenser window, click Save license request to file. The License Request dialog box appears. 3. In the License Request dialog box Agency/site name field, enter your organization name. Axon Enterprise, Inc. Page 25 of 77

26 Note: The Agency/site name can be the same name as the server. 4. In the License Request dialog box Integrator/installer field, enter the name of the person installing Axon Commander. 5. Optionally, add any notes for the license request. 6. Click OK. The Browser for Folder dialog box appears so you can select where the license request file is saved. 7. Select Desktop and click OK. 8. the license request file that was just saved to your desktop to your Axon representative. Alternately, you can contact Axon Customer Service through the Axon Support website, by at: or by phone at: Axon Enterprise, Inc. Page 26 of 77

27 Your Axon representative activates your license and then sends an Axon Commander license file to you. Note: If needed, you can close the Commander Licenser window and Commander Server Checkup window. Return to this procedure when you receive the license file from your Axon Representative, open Commander Checkup, click Server Setup, and then click Run License Wizard. 9. After receiving the activated license file from your Axon representative, save the file to your desktop. 10. In the Commander Licenser window, click the Submit license tab. Axon Enterprise, Inc. Page 27 of 77

28 11. Click the browse button to the right of the Filename field. 12. Navigate to your desktop, select the Commander license file, and then click Open. 13. In the Commander Licenser window, click Submit License and then click Yes when the displayed message asks to restart once finished. 14. In the Commander Licenser window, click the View License tab and then close the Commander Licenser window. Axon Enterprise, Inc. Page 28 of 77

29 Configure Axon Commander Server Access 1. In the Set up your Commander Server pane, click Run Commander Permission Wizard. The Commander Permissions Updater dialog box appears. 2. In the Commander Permissions Updater dialog box New Configuration section, enter the Username and Password for the local administrator. Axon Enterprise, Inc. Page 29 of 77

30 Note: The Username is the local administrator username; not the domain administrator. This is the administrative user created in the Create Local Users section. 3. Click Update selected services. A message appears. 4. Click OK. 5. Close the Commander Permissions Updater dialog box. Configure Client Access for Axon Commander 1. In the Set up your Commander Server pane, click Run Client Access Wizard. The Commander client/plugin access window appears. Axon Enterprise, Inc. Page 30 of 77

31 2. In the Commander client/plugin access window, click Repair. The Modify Launcher user dialog box appears. 3. In the Modify Launcher user window, enter the local user username and password. This is the read-only access user created in the Create Local Users section. 4. Click Save and then click OK. 5. Close the Modify Launcher user dialog box. 6. Close the Axon Commander client/plugin access window. Configure Windows Firewall (Optional) If you manually configured your Windows firewall rules, you can skip this section. 1. In the Set up your Commander Server pane, click Run Firewall Configuration. Axon Enterprise, Inc. Page 31 of 77

32 2. The system configures the Windows firewall ports for Axon Commander. For more information about the firewall port requirements, see Firewall Ports. Domain Settings (Optional) Axon Commander automatically connects to the local domain. This procedure is used to connect your installation of Axon Commander to other domains. This procedure can be skipped if your installation will not connect to any other domains. 3. In the Set up your Commander Server pane, click Run Domain Configuration. The Domains dialog box appears. Axon Enterprise, Inc. Page 32 of 77

33 4. The Domains dialog box, click Add. The Domain dialog box appears. 5. In the Domain dialog box, enter the path for the domain you want to add, enter the username and password for the account being used to synchronize with the domain, and then click Test to check the connection. 6. If you receive a Success message, continue to the next step. Otherwise, repeat step Click Save. 8. Close the Domain dialog box. 9. Close the Domains dialog box. Axon Commander Language Settings (Optional) This procedure sets the default language for Axon Commander Client. Axon Commander Client supports multiple languages. This procedure can be skipped if your installation will use English as the default language. 1. In the Set up your Commander Server pane, click Select Default Language. The Language selection dialog box appears. Axon Enterprise, Inc. Page 33 of 77

34 2. The Language selection dialog box, select the default language for the Axon Commander Client and then click Select. A message dialog box appears saying the language setting has been applied and that the AppServer must be restarted for the change to take effect. 3. Click OK. 4. Close the Language selection dialog box. Verify the Axon Commander Installation 1. In the Commander Server Manager window, click Services and verify all the services are running. Note: The Commander Beacon Service will only be running if Axon Interview is also installed. Axon Enterprise, Inc. Page 34 of 77

35 If a service is not running, select it and click Start. 2. Open a web browser. Axon Commander supports Internet Explorer 11, Chrome, and Firefox browsers. 3. Enter the server name, IP or if you are accessing on the server itself localhost and the port To access the Axon Commander Client download page in French, German, or Italian, add a / and the language code fr, de, or it. 4. Press Enter. The Axon Commander launch screen is shown in the browser window. 5. Click Launch Commander. Axon Enterprise, Inc. Page 35 of 77

36 An icon appears at the bottom of the browser window asking you to KEEP or DISCARD the file for Commander. 6. Click KEEP. The browser downloads the Commander-launcher.exe application. Note: In some cases, you might see a Windows Unknown Publisher message during installation. You can safely ignore this message and continue with the installation. 7. Run the Commander-launcher.exe application to install Axon Commander Client and creates a desktop shortcut. After a brief splash screen, the client connects with the Axon Commander server and the Axon Commander Client Login screen is shown. 8. Enter the following default administrator account credentials and then click Login. Username: admin Password: pass Note: After an administrator logs in to Axon Commander Client and creates their own user account, the default administrator account password should be changed. The Axon Commander Client main window opens. You can close the Axon Commander Client window. This completes the installation. Install and Configure Axon Camera Extractor (Optional) Note: Axon Camera Extractor (ACE) links the Axon Docks to Axon Commander and ingests assets from devices placed in the Axon Docks into Axon Commander. To allow Axon Docks and the Axon Device Manager mobile application to communicate with Axon Axon Enterprise, Inc. Page 36 of 77

37 Commander, an SSL certificate that authenticates the AES connection must be installed. Contact your Axon representative for additional information and assistance with this SSL certificate. Alternately, you can contact Axon Customer Service through the Axon Support website, by at: or by phone at: If you are not using Axon Docks to ingest assets or using Axon Device Manager mobile application to assign devices, you do not need to add the Certificate Snap-in or import the SSL certificate. You can skip those procedures and go to the Install Axon Camera Extractor procedure. Add Certificate Snap-in 1. Unpack the ACE zip file and extract the files to an appropriate location. 2. Open the Microsoft Management Console (MMC). In the Search Windows field type mmc. Select MMC from the list. The MMC console window appears. 3. In the console window, click File and select Add/Remove Snap-in. The Add or Remove Snap-ins dialog box appears. Axon Enterprise, Inc. Page 37 of 77

38 4. In the Available snap-ins pane, select Certificates and click Add. The Certificates snap-in dialog box appears. 5. In the Certificates snap-in dialog box, select Computer account, and then click Next. The Select Computer dialog box appears. Axon Enterprise, Inc. Page 38 of 77

39 6. In the Select Computer dialog box, click Local computer: (the computer this console is running on) and then click Finish. 7. In the Add/Remove Snap-in window, click OK. Import SSL Certificate 1. In the left pane of the console window, click Certificates (Local Computer). 2. In the center pane of the console window, right-click Personal, select All Tasks, and then select Import. The Certificate Import Wizard appears. Axon Enterprise, Inc. Page 39 of 77

40 3. On Certificate Import Wizard, click Next. 4. On the File to Import page, click Browse, locate your certificate file, and then click Next. The certificate file is provided as a.pfx file. Note: If certificate cannot be found in the designated folder, try searching for all files. 5. Enter the password and click Next. The password for the certificate is provided separately by your Axon representative. 6. On the Certificate Store page, click Automatically select the certificate store based on the type of certificate, and then click Next. 7. Click Finish, and then click OK to confirm that the import was successful. 8. Open the Certificate properties dialog box to verify that the correct certification path exists. In the left pane of the console window, click Certificates (Local Computer). Double-click Personal and then double-click Certificates. Right-click the certificate and select Open. Axon Enterprise, Inc. Page 40 of 77

41 Click the Certification Path tab. 9. Save the console settings, but keep the console window and certificate dialog box open. Install Axon Camera Extractor 1. Locate the extracted ACE files and double-click the.exe file to start the installation process. The Axon Camera Extractor Setup wizard appears. 2. Click Next. Axon Enterprise, Inc. Page 41 of 77

42 The End-User License Agreement page appears. 3. Accept the license agreement and click Next. The Select Installation Folder page appears. 4. In the Select Installation Folder page, click Browse, select the directory where you want to install the application, and then click Next. The Ready to Install window appears. 5. Click Install and when the installation is complete click Finish. The Axon Camera Extractor Configuration window appears. Axon Enterprise, Inc. Page 42 of 77

43 Configure Axon Camera Extractor Axon Camera Extractor can be configured to connect to an Axon Dock through an Ethernet or using a USB interface to connect to a single Axon camera or Axon Dock without the Axon Core attached. 1. In the Axon Camera Extractor Configuration window under Connectivity, select USB or Ethernet, as applicable for your installation. If USB is selected, enter the Max. Simultaneous Offloads allowed. This number can be anything from 1, if your agency will only use an Evidence Sync cable to offload information one camera at a time, up to 6, if your agency is using a six-bay Axon Dock without the Axon Core attached. Axon Enterprise, Inc. Page 43 of 77

44 If Ethernet is selected: In the previously opened Certificate dialog box, click the Details tab. In the Field/Value list, select Thumbprint and copy the entire thumbprint string including the spaces. In the Axon Camera Extractor Configuration window, paste the thumbprint into the Thumbprint field and click Submit. The Windows command prompt window appears. Press Enter. The Windows command prompt window closes. Axon Enterprise, Inc. Page 44 of 77

45 2. In the Axon Camera Extractor Configuration window under Settings, enter the Axon Commander server address, and then enter the directories information as needed. Note: If you are upgrading from a version of Axon Camera Extractor (ACE) earlier than v1.5, it is important to note that there is no longer an Asset folder. Instead, newer versions have a Staging folder. In earlier versions of ACE, once a video was offloaded it would remain in a shared folder until the Commander Parser service saw the video and ingested it. To improve the overall security of the software, ACE was updated to automatically push the video into the Commander ingestion folder once the video is fully offloaded. The Staging folder is not a shared folder, unlike the Assets folder, and is only used as a temporary storage location until the camera video is fully offloaded. 3. In the Axon Camera Extractor Configuration window, click Save. 4. In the Question dialog box, click Yes to restart the service. The service restarts and changes to the Status Running. Axon Enterprise, Inc. Page 45 of 77

46 5. Close the Axon Camera Extractor Configuration window and close the console window. The Axon Camera Extractor continues to run in the background as a service. DNS Settings The Axon Docks must be able to find the ACE certificate URL (ace1axontest.commander.evidence.com) to reach the Axon Camera Extractor server and authenticate and encrypt the cameras' offload. You can do one of the following: Create the zone and entry below on your own DNS server and set this DNS server when configuring the docks. DNS Setting DNS forwarding Zone Type A record IP Address Value commander.evidence.com ace1axontest.commander.evidence.com ACE Server IP Axon can provide you with a DNS server software that can be installed on the same Axon Commander/ACE server. If you need this software, please contact your Axon representative. Specialized instructions will be provided as well. Installing DNS Server on Microsoft Windows Server Prior to executing these steps, ensure that the DNS Server Role is installed on the Windows Server instance that the Axon Commander Server is installed on. To install the DNS Server Role, perform the following steps: Axon Enterprise, Inc. Page 46 of 77

47 Configuring DNS Zone with Windows Server 1. If running Windows Server 2012, Server 2012 R2, or Server 2016, start by opening the DNS Server Manager. This can be done from the Windows Run command. Enter dnsmgmt.msc and click OK. The DNS Manager window appears. 2. In the DNS Manager window, right-click on the Forward Lookup Zones folder and select New Zone. The New Zone Wizard starts. Axon Enterprise, Inc. Page 47 of 77

48 3. Click Next to continue. 4. On the Zone Type page, click Primary Zone and click Next. Axon Enterprise, Inc. Page 48 of 77

49 5. On the Active Directory Zone Replication Scope page, use the default selection (To all DNS servers running in this domain), and then click Next. 6. On the Zone Name page, in the Zone Name field enter commander.evidence.com and click Next. Axon Enterprise, Inc. Page 49 of 77

50 7. On the Zone File page, leave the Zone name as is and click Next. 8. On the Dynamic Update page, click Do not allow dynamic updates and click Next. Axon Enterprise, Inc. Page 50 of 77

51 9. Click Finish. The system creates the new zone. 10. Create a new A Record entry under the newly created zone. In the DNS Manager window, right click on the commander.evidence.com zone and select New Host (A or AAAA). The New Host dialog box appears. 11. In the New Host dialog box, enter the name and IP address for the new host and click Add Host. Axon Enterprise, Inc. Page 51 of 77

52 The entry must have the Fully Qualified Domain Name (FQDN) be the same as the SSL Certificate name (for example, ace1axonseattle.commander.evidence.com). The IP must be the IP address of computer on which you installed the Axon Camera Extractor software. See the image below as an example. 12. When complete, your entry in the DNS Manager window should be similar to the following image. You can register your Axon Docks to the FQDN (ace1axontest.commander.evidence.com) using any credentials listed within Axon Commander. Go to the Axon Dock Configuration section to complete the process. Axon Enterprise, Inc. Page 52 of 77

53 Configuring DNS Zone with Simple DNS (For Test Installations Only) In the event a local DNS server is not available on the network in which Axon Commander is being deployed, third-party DNS software is required. This software can be installed on a Workstation running a Windows 7 or Windows 10, since consumer-based versions of Windows do not include DNS server software. An example of such third-party software if SimpleDNS by JH Software. The following steps will walk through the configuration steps for using SimpleDNS. 1. With SimpleDNS having previously been installed, from the main screen of Simple DNS Plus, click Records on the tool bar. The DNS Records dialog box appears. 2. Click Quick on the tool bar to start the Quick Zone Wizard. Axon Enterprise, Inc. Page 53 of 77

54 3. Enter your domain name, in this case we recommend commander.evidence.com. The IP addresses are optional and not required at this moment. Click OK. 4. Right-click on the new zone (commander.evidence.com) and select New A-record (Host Address). Axon Enterprise, Inc. Page 54 of 77

55 5. Enter the A-Record information: Record name (host) should match the name of the certificate used for the ACE configuration. Host IP address must match the IP address of the VM running the ACE software. Click OK to complete the configuration. You can now configure your Axon Docks. Axon Enterprise, Inc. Page 55 of 77

56 Axon Dock Configuration This section provides information on how to configure the Axon Dock to operate with Axon Camera Extractor (ACE). This information is in addition to the basic configuration information found in the Axon Dock Installation Manual. Follow the initial steps in the Axon Dock Installation Manual for firewall configuration, installing and connecting the dock, and accessing the dock s configuration web portal. After connecting to the web portal for the Axon Dock (see Axon Dock Installation Manual for details), ensure the following items are configured correctly. 1. Click on the Networking tab. Review the information to ensure that basic IP information has been configured. By default, the dock uses standard DHCP to obtain an IP address from your network. 2. Click on the Operations tab to register the dock to your Axon Commander Server. For the Evidence.com Agency, enter Axon Commander [Site ID]. Your Site ID can be found in Commander Licenser. For the Domain name, enter the digital certificate FQDN that was used when configuring the DNS Zone (such as ace1axontest.commander.evidence.com). Your FQDN may vary based on the server configuration and certificate used. Enter the Admin Username and Admin Password for any existing Axon Commander administrator. Axon Enterprise, Inc. Page 56 of 77

57 3. Click Save Changes. The Axon Dock will save the information, register the dock, and restart. 4. Lastly, we need to make an adjustment to the Axon Dock time synchronization to ensure ACE is used to set the time. Click the Administration tab, scroll down to the SSL Configuration section. Select the Require SSL for Initial Time Check check box. Click Save Changes and then Reboot Dock. 5. After the configurations are complete, click the Status tab. The System Status should show the first six line have a green check mark, as shown in the image below. This completes the Axon Dock configuration. Axon Enterprise, Inc. Page 57 of 77

58 Axon Commander Advanced Settings The Advanced Settings section has three items: Wowza Configuration is used to configure the Wowza Streaming Engine for use with Milestone XProtect. See Configuring Axon Commander and Milestone XProtect for more information. Beacon Configuration is used to configure the Beacon service for installations that integrate with Axon Interview. This information is typically configured when Axon Interview is installed. File Placement Restorer is used, with assistance from Axon Support, to detect and repair issues with Axon Commander assets. This tool should not be used without guidance from Axon. It also has, at the bottom of the page, a listing of the Windows information for the server, which may be used for remote purposes. Axon Device Firmware Updates Axon periodically issues firmware updates for Axon devices. When these updates are issued, your Axon representative will contact you and provide copies of the firmware update files. Axon Enterprise, Inc. Page 58 of 77

59 Once you receive a firmware update, use the following procedure to add the update to your system and your devices. 1. Save the firmware update file to the Axon Commander Server. 2. Open Commander Server Manager. 3. In the Commander Server Manager left pane, click Firmware. 4. In the Firmware pane, click Browse. 5. Navigate to the location where the firmware update file was downloaded, select the file, and then click Open. Axon Enterprise, Inc. Page 59 of 77

60 6. In the Dock Firmware pane, click Update Devices. The system extracts the firmware update and displays the updated firmware version for the appropriate devices. Close the Commander Server Manager window. When devices are placed in the Axon Dock, the device firmware is updated to the most recent version after the device downloads the files on the device. If you have any questions about firmware updates, contact your Axon representative. Axon Commander Software Updates Axon periodically issues software updates for Axon Commander. When these updates become available, your Axon representative will contact you and provide copies of the updates. Once you receive a software update, use the following procedure to add the update to your system. 1. Save the software update file to the Axon Commander Server. 2. Open Commander Server Manager. Axon Enterprise, Inc. Page 60 of 77

61 3. In the Commander Server Manager left pane, click Software. 4. In the Software Upgrades pane, click Add. 5. Navigate to the location where the software update file was downloaded, select the file, and then click Open. The software update is added to the list. 6. In the Dock Firmware pane, select the update and click Enable. The system installs and updates your Axon Commander software. Axon Enterprise, Inc. Page 61 of 77

62 If there are issues with using an update, you can select the update and click Disable to deactivate the changes. Close the Commander Server Manager window. If you have any questions about software updates, contact your Axon representative. Third-Party Player Storage When working with third-party video, such as those from a CCTV or VMS system, a standalone software is often required to play proprietary video formats. The Players tab in the Commander Server Manager can be used to associate certain players with one or more video extensions. When a video is exported from Axon Commander to a DVD or a local workstation, the associated player is exported with the video. This ensures users always have the required tools to play the video and helps with the management of those players. Add a Third-Party Player 1. Open Commander Server Manager. 2. In the Commander Server Manager left pane, click Players. 3. Click Add. 4. In the Standalone Media Player dialog: Axon Enterprise, Inc. Page 62 of 77

63 Enter the Player name. Enter or browse to the location of the third-party player file. Select all the file Extensions associated with the player. This is used by the system to determine when the player is included with file exports. Optionally, select if the standard Commander player should be included with any exports. Including the standard Commander player allows users to view metadata and audit information associated with the exported file. 5. Click Save. Edit Third-Party Player Information 6. Open Commander Server Manager. 7. In the Commander Server Manager left pane, click Players. Axon Enterprise, Inc. Page 63 of 77

64 8. Click on the third-party player you want to edit and click Edit. 9. In the Standalone Media Player dialog, change the appropriate settings for the player. 10. Click Save. Delete a Third-Party Player 11. Open Commander Server Manager. 12. In the Commander Server Manager left pane, click Players. 13. Click on the third-party player you want to delete and click Delete. 14. The system asks you to confirm the deletion. Click Yes to delete the player information. Axon Enterprise, Inc. Page 64 of 77

65 Configuring Axon Commander and Milestone XProtect Update to Latest Milestone Device Pack To add support for edge-storage with audio, the latest Milestone device pack must be installed. Prior to configuration, ensure you have the latest from the Milestone website. At a minimum, Device Pack 9.8a is required for proper functionality: Installing Axon Commander, Axon Camera Extractor, and Wowza Follow the standard instructions for installing Axon Commander, but ensure that the Wowza Streaming Engine is selected for installation in the Axon Installation Launcher (this option is normally unselected). Configuring Wowza After Axon Commander is installed and setup, follow the steps below to configure the Wowza Streaming Engine. 1. In the Commander Server Manager, click Advanced Settings and then click Run Wowza Configuration. Axon Enterprise, Inc. Page 65 of 77

66 2. In the Wowza Configuration dialog box, enter the IP address for the server Wowza was installed on, and the location of the Wowza root folder. If Wowza was installed using the automated Axon Installation Launcher, the information in these fields was automatically added and does not need to be changed. The default root folder is: C:\Program File (x86)\wowza Media Systems\Wowza Streaming Engine If Wowza was installed manually and the default installation location was changed, verify that the correct information is entered in the fields. 3. Enter in Wowza License information 4. Click Save. Axon Enterprise, Inc. Page 66 of 77

67 Configuring Axon Commander Cameras 5. Log in to Axon Commander Client and click Administration in the upper right corner of the client window. The Axon Commander Administration window is displayed. 6. Click Devices in the Administration navigation pane. 7. In the All Devices tab, search for all the Axon body cameras that needs to stream to Wowza. 8. In the Port column, enter an unused port number for each Axon body camera that will stream to Wowza. Each camera must have a unique port number. If you do not see a Port column, there may be a licensing issue with your Axon Commander installation and you should contact your Axon representative. Configuring Windows Firewall In order for camera streaming to work, the appropriate ports need to be opened in the Windows Firewall. Create an Outbound Rule in Windows Firewall to allow Outbound TCP connections for ports 1088, 1935, Axon Enterprise, Inc. Page 67 of 77

68 Configuring Milestone XProtect Note: The Commander Application Server service must be running prior to configuring cameras in Milestone since it provides camera's description (device information, encoding details, etc.). Adding and configuring Axon body cameras as Hardware effectively adds them to the Milestone system. Follow the steps below to add an Axon body camera. 9. Open Milestone XProtect Management Client. 10. In the left navigation pane, expand Servers and click Recording Servers. 11. In the center pane, right-click the item under Recording Servers. 12. Click Add Hardware. Axon Enterprise, Inc. Page 68 of 77

69 Axon Commander Installation Guide 13. In the Add Hardware dialog box, select Manual and click Next. 14. On the Credentials page, click Next to continue. Credentials are not supported at this time, so no selection is required. Axon Enterprise, Inc. Page 69 of 77

70 15. In the Driver selection page, select ONVIF and click Next. 16. Point the Milestone Server to the Axon body cameras Axon Enterprise, Inc. Page 70 of 77

71 Click Add and enter the following information: Address: Enter the IP address of Axon Commander server Port: Enter the port number for an Axon body camera that will stream to Wowza. This is the port number entered when configuring Axon Commander Cameras. Hardware Model: Select ONVIF Conformant Device. 17. Click Next. The Milestone system tries to detect the cameras. 18. Click Next until the Add to Group page appears (there should be three pages before the Add to Group page). To add to a group, click on a folder, select a group, and click OK. Axon recommends the you create a new Camera and Microphone group to for the Axon body cameras. In the example below, the Axon Cameras and Axon Microphone groups were created. Axon Enterprise, Inc. Page 71 of 77

72 Axon Commander Installation Guide 19. Click Finish to complete adding the hardware. 20. In-order to maintain communication between Axon Commander and Milestone, Axon Commander will continuously stream a blank-black video. To prevent Milestone recording and saving this video, disable the recording of this stream as follows: In the left navigation pane, under Devices, click Camera. In the middle pane, click on the appropriate body camera In the right-hand Properties pane, click the Record tab. Clear the Recording check box, Click the Save icon on the XProtect Management Client toolbar. 21. Repeat this procedure for each Axon body camera. Axon Enterprise, Inc. Page 72 of 77

73 Axon Commander Troubleshooting This section provides general information for post-installation troubleshooting, as well as what information should be passed on to Axon in case of systems malfunction. Terminology Dock Docking station used to charge and upload evidence from Axon body worn cameras. Server Physical or virtual machine where the Axon Commander application is installed. ACE Axon Camera Extractor links the Axon Docks to Axon Commander and ingests assets from body worn cameras placed in the Axon Docks into Axon Commander. SSL certificate Secure Socket Layer, is the standard security technology for establishing an encrypted link, in this case between the Axon Commander server and the Axon Docks. DNS Server Domain Name System, A method that resolves IP addresses and hierarchical domains into easily readable names. In this case the URL linked to the SSL certificate. Ping - Is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. Issues Dock Communication Error Symptoms include the docked camera cycling through all colors (Red, Yellow,Green) Dock Check: Check to see if you can reach Axon Dock from the server by logging in to dock web interface from server (input IP address of dock in web browser). Note: If not able please check your IP addressing scheme. Navigate to Network tab and verify the DNS and Commander server IP s match the corresponding entities. Server Check: Make sure you can ping the dock from server Axon Enterprise, Inc. Page 73 of 77