Page tree
Skip to end of metadata
Go to start of metadata

EZ Unified Device Manager Express
Provided by Event Zero 

The information contained in this document represents the current view of Event Zero on the software discussed as of the date of publication and is subject to change at any time without notice to you. This document and its contents are provided AS IS without warranty of any kind, and should not be interpreted as an offer or commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented. EVENT ZERO MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
The descriptions of other companies' products in this document, if any, are provided only as a convenience to you. Any such references should not be considered an endorsement or support by Event Zero. Event Zero cannot guarantee their accuracy, and the products may change over time. Also, the descriptions are intended as brief highlights to aid understanding, rather than as thorough coverage. For authoritative descriptions of these products, please consult their respective manufacturers.

All trademarks are the property of their respective companies.

©2017 Event Zero. All rights reserved.

Event Zero is either registered trademarks or trademarks of Event Zero Pty Ltd. in Australia and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Table of Contents

Overview of Hardware and Software

Installing EZ Unified Device Manager (UDM) Express is a simple process that allows you to get up and running quickly on a desktop computer a server-class computer or virtual machine. 
The installation is in six parts:

  • Review Hardware and Software requirements
  • Install the.Net Framework (minimum version 4.5.2)
  • Install and Configure Internet Information Server
  • Install SQL Server Express
  • Configure the DHCP Server
  • Install EZ UDM Express

If you encounter any complications or questions while installing EZ UDM Express, refer to the Appendix at the end of the document for tips and troubleshooting resources.

Hardware and Software Requirements

First, let's review the hardware and software requirements.
Note! We provide minimum and recommended hardware and software configurations. The minimum is known to work, but may not perform as well as the recommended. If you experience issues with slow performance or not able to service as many endpoints as you need, you will need to observe the recommended requirements.
Hardware Minimum:

  • CPU: 2 GHz 2 core AMD or Intel processor, 1 vCPUs for virtual machines
  • RAM: 2 GB RAM
  • Disk space: 20 GB available disk for SQL Express and application
  • Network Interface: 100 Mbps

Software Minimum:

  • Windows 8.1, current Service Pack, Windows Server 2012 R2, current Service Pack
  • Dynamic Host Configuration Server (Windows Server is assumed for this guide, but can be any applicable DHCP Server that will accept the required vendor options)
  • .Net Framework 4.5 or newer

Note! Some versions of SQL Server Express require .Net Framework 3.5

  • SQL Server Express 2012 (32-bit or 64-bit)
  • SQL Server Express Management Studio (for troubleshooting and tuning SQL Express)
  • Dynamic Host Configuration Protocol (DHCP) Server
  • Internet Information Services (IIS), exclusive use of Port TCP/80 and Port TCP/81 and optionally TCP/443 for HTTPS
  • Browsers: Google Chrome, Microsoft Edge, Windows Internet Explorer, Apple Safari, Mozilla Firefox, Opera Software Opera

Hardware Recommended:

  • CPU: 3.2 GHz or better AMD or Intel 4 core, 2 vCPUs for virtual machines
  • RAM: 4 GB or more
  • Disk space: 60 GB available for SQL Express and application
  • Network Interface: 1 Gbps

Software Recommended:

  • Windows 10, current Cumulative Updates, Windows Server 2012 R2, current Service Pack, or Windows Server 2016, current Cumulative Updates
  • .Net Framework 4.5.2 or newer
  • 32-bit or 64-bit SQL Server Express 2012 or newer (up to and including SQL Server Express 2016)
  • Dynamic Host Configuration Server (Windows Server is assumed for this guide, but can be any applicable DHCP Server that will accept the required vendor options)
  • Internet Information Services (IIS), exclusive use of Port TCP/80 and Port TCP/81 and optionally TCP/443 for HTTPS
  • SQL Server Express Management Studio (for troubleshooting and tuning SQL Express)
  • Browsers: Google Chrome 55.0 and newer, Microsoft Edge 25 and newer, Windows Internet Explorer 11, Apple Safari in macOS Sierra and iOS 9, Mozilla Firefox 51 and newer, Opera Software Opera 42.0 and newer

Note! EZ UDM Express supports most current browsers if they comply with the W3C standards, including ECMA JavaScript and JSON. If you are unsure if your browser supports these standards, use one of the listed browsers. Browser versions cited are the versions that were used to test the software during development and Quality Assurance. Other versions may work fine, but if there is a potential problem, use a version cited to eliminate a possible change in browser behavior.

Installation Step-by-Step

The Step-by-Step installation is provided for users who need the additional assistance or in the event you have problems with the default install.

Install the .Net Framework

If you need to install a newer version of the .Net Framework, refer to the links in Install the .Net Framework, download the .Net Framework installer package and install the package.

Important! Windows 10 and Windows Server 2016 come with .Net Framework 4.6 pre-installed. Windows 8.1 and Windows Server 2012 R2 come with .Net Framework 4.5 pre-installed. There is no easy method to accurately determine which version of the .Net Framework is installed without resorting to searching registry keys or searching and deciphering the Global Assembly Cache (GAC) in Windows. The most obvious method is to check "Installed Programs" but, the .Net Framework 5.4.2 is listed as .Net Framework 4.5 and the .Net Framework 4.6 is only listed as 4.6, not 4.6.1 or 4.6.2.

However, we created a PowerShell script (PowerShell file for .Net Framework) that does the work of looking through the registry and reporting back the installed versions of the .Net Framework. Run this script by copying it to the machine that you need to know what .Net Framework is installed.

  1. Click Start (or the Windows icon)
  2. Click "Windows PowerShell" (if Windows 10 or Windows 2016, click the Windows PowerShell folder, then click "Windows PowerShell")
  3. In the PowerShell prompt, type Path to the file\Get-DotNetFrameworkVersion.ps1
  4. The newest version of the .Net Framework installed is displayed, as in the example screenshot below 

On Windows Server 2012 R2 or Windows 8.1 we recommend installing .Net Framework 4.5.2, our minimum required version. By installing 4.5.2, you are assured of meeting the required software version.

If the .Net Framework 4.5.2 is already installed, instead of a dialog to begin the install, you are presented with an option to either Repair or Remove .Net Framework 4.5.2. If you see these options, click Cancel. The.Net Framework 4.5.2 is already installed.

Ensure that you have the correct version(s) of the .Net Framework installed.

If you need a newer version of the .Net Framework, refer to the following links:

Install and Configure Internet Information Server

Internet Information Server (IIS) is a required component for hosting and using EZ Unified Device Manage Express. IIS is installed and configured differently on Windows Server and Windows desktop. The following sections detail the installation process for Windows Server 2012 R2 and Windows 10 desktop.

Windows Server 2012 R2

Installation of IIS on Windows Server uses Server Manager. To install and configure IIS on Windows Server, do the following.

Using PowerShell

The installation of Internet Information Server (IIS) and the required features is very simple if you have even a passing knowledge of Microsoft's PowerShell scripting language. Open PowerShell (the PS command prompt or the PowrShell ISE Editor both work) and copy the following line (All on one line!)

Add-WindowsFeature -Name AS-NET-Framework,Web-Http-Logging,Web-Request-Monitor,Web-Stat-Compression,Web-Filtering,Web-Basic-Auth,Web-Windows-Auth,Web-Net-Ext45,Web-AppInit,Web-ASP,Web-Asp-Net45,Web-CGI,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,Web-WebSockets,NET-Framework-Core,NET-WCF-TCP-PortSharing45,Web-Mgmt-Tools -Source "Drive letter":\Sources\sxs

Where "Drive letter"  is the drive letter of the DVD drive or mapped location of the Windows source files.

Execute the Powershell command. After the install is complete, you should see a success message similar to the following screenshot:

We recommend you refer to the following screenshots for Server Manager to ensure all components are installed as expected. 

Using Server Manager

Note! The following screenshots are from Windows Server 2012 R2. Other Windows Server versions are similar.

  1. In Window Server, click the Windows button, then click Server Manager.

Figure   Server Manager in Windows Server

2. In Server Manager:

  • On the Dashboard, in the upper left click "Manage", then click "Add Roles and Features"
  • On the "Before you begin" page, click Next
  • On the "Select Installation Type" page, select "Role-based or feature-based installation," click Next

On "Select destination server," select "Select a server from the server pool," click the server you are installing to in "Server Pool," click Next

3. On "Select server roles," select "Web Server (IIS)." Click "Add Features" to accept the default options on "Add features that are required for Web Server (IIS)?" Click Next to continue.

Figure   Add Web Server (IIS) role and default features

4. Once you have confirmed the role service selections, click Next to continue.

5.  In "Features," check the .Net Framework 3.5 and 4.5 components. Add as appropriate.

Figure   .NET Framework 3.5 options

Figure   .NET Framework 4.5 options

6. On the "Select features" page, click Next.

7. On the Web Server Role (IIS) page, click Next.

8. On the "Select role services" page, under "Web Server," expand each section and select the Web Server components as depicted in the following figures:

If you are prompted to Add Features in the following Web Server IIS Features, review the defaults and click "Add Features."

Figure   Web Server Common HTTP Features

Figure   Health and Diagnostics features

Figure   Performance features

Figure   Security features

Figure   Application Development features

9. After completing the selections, click "Next."

10. On the "Confirm installation selections" page, review your selections, specify an alternate source files location, and click Install to continue.

Important! During the installation of the roles and features, the installer often needs access to the Windows Server media or source path for files for Roles and Features. You can specify an alternate path. If using a DVD drive or a network or local location where the source files are located, specify the location by clicking the "Specify an alternate source path" link. The location on the DVD (or the location of a copy of the source files to a local or mapped network hard drive) is the folder "[Drive letter]:\sources\sxs."

Click OK to accept the alternate path.

Figure   Specifying an alternate location for Windows source files

11. The installation will begin. Monitor the installation process. You can safely close the dialog while the installation proceeds by clicking Close. If you are monitoring the installation process, click Close to complete the installation when the installation progress reports that the installation succeeded.

Installation of IIS on Windows Server is complete. Proceed to the installation of SQL Server Express.

Windows 8.1, Windows 10 and Windows Server 2016

Using Deployment Image Servicing and Management (DISM)

Windows desktop operating systems are not serviced in the same way as the Windows Server platforms. Desktop systems use Deployment Image Servicing and Management (DISM). Installing Internet Information Server and the dependent components to support EZ UDM Express, do the following:

  1. Open a Windows command prompt using "Run as Administrator."
  2. Type or paste the DISM command at the command prompt

    DISM /Online /Enable-Feature /FeatureName:IIS-WebServerRole /FeatureName:IIS-WebServer /FeatureName:IIS-NetFxExtensibility45 /FeatureName:IIS-HttpTracing /FeatureName:IIS-WindowsAuthentication /FeatureName:IIS-ISAPIExtensions /FeatureName:IIS-ISAPIFilter /FeatureName:IIS-ASPNET45

  3. Reboot the computer following the completion of the DISM command

Using Control Panel's "Turn Windows features on or off" 

Installation of IIS on Windows Desktop also can use the Programs and Features in Control Panel. To install and configure IIS on Windows Desktop, do the following.
Note! The following screenshots are from Windows 10. Other Windows Desktop versions are similar.

  1. Log into Windows. You must log in as a user with Administrative capabilities.
  2. Open Control Panel, click Programs, then click Turn Windows features on and off.

Figure   In Control Panel, install IIS by turning on Windows features

3. In Windows features, locate the following components and select them.

Figure   .Net Framework 3.5 and 4.6 Advanced Services features

Figure   Locate and select Internet Information Services in Windows features

Figure   Enable features with check marks under Application Development

Figure   Enable features with check marks under Common HTTP Features, and  Health and Diagnostics

Figure   Enable features with check marks under Performance Features and Security

6. Click OK to continue. When prompted to restart, click Restart now.

7. After restarting Windows, the installation of IIS is complete. Login and proceed to the installation of SQL Server Express.

Install SQL Server Express

EZ Unified Device Manager (UDM) Express uses Microsoft ® SQL Server Express to store data and configuration information. You must install SQL Server Express before installing EZ UDM Express. To install SQL Server Express, you do the following.

  1. Download SQL Server Express.

Note! It is recommended to use 32-bit SQL Server Express for 32-bit Windows, or 64-bit SQL Server Express for 64-bit Windows. You can run 32-bit SQL Server Express on 64-bit Windows, but you cannot install or run 64-bit SQL Server Express on Windows 32-bit.
Links for versions of SQL Server Express 2012:

Links for versions of SQL Server Express 2014:

Links for versions of SQL Server Express 2016:

  1. Begin the install by double-clicking the package or right-click and select 'Run as Administrator.'

Note! The version of SQL Server Express used for this example is SQL Server 2012 Express with Tools and Service Pack 1

2. Initially, the installer will unpack files and launch the SQL Server Installation Center. In the left-hand menu, click Installation. Click "New SQL Server stand-alone installation or add features to an existing installation."

Figure   SQL: Server Installation Center menu

3. Review the license terms. You must select and accept the license terms to continue. Select the Send feature usage data to Microsoft if you desire. Click Next to continue.

Figure   Accept license terms and optionally send feature data to Microsoft

4. Installation Center checks for and offers updates for SQL Server. If the update check finds updates, select "Include SQL Server product updates" and click Next to continue.

5. Setup will install the Setup files and prepare for installing SQL Server. Wait until the task status for all items is Completed. Click Next to continue.

6. On the Feature Selection page, the default features and directories are sufficient for most users. We recommend not changing the defaults. Click Next to continue.

Figure   Feature Selection and directory locations for program files

7. On the Instance Configuration page, the default should be:

  • Named Instance – SQLExpress
  • Instance ID – SQLEXPRESS
  • Instance root directory: C:\Program Files\Microsoft SQL Server\

8. Retain these defaults and click Next to continue.

Figure   Instance Configuration and directories

9. On the Server Configuration page, set the identity of the Service Accounts. The defaults will work for most installations, and you should not need to make changes. Passwords for system service accounts are managed by the services and cannot be set. Click Next to continue.

Figure   Server and service identity configuration

10. On the Database Engine Configuration page, select Windows Authentication mode.

By default, the user account that you are installing SQL Server as will be made a SQL Server Administrator. If you need to add other SQL Server administrators, you do that by clicking Add… and locating the user object or group object to add to the list of administrators.
Note that there are three other tabs – Data Directories, User Instances, and FILESTREAM. You should not have to make changes to any of these, and these options can be changed later using SQL Server Management Studio.

Figure   Database Engine Configuration, data directories, and SQL administrators

11. Error Reporting allows you to select a checkbox that will send Windows and SQL Server Error Reports to Microsoft. Click Next to continue. Installation of your selections will commence.

12. When the Setup completes, a summary of operations is displayed. You can scroll through to determine if there were any warning or errors encountered. Typically, the setup will complete successfully. Product documentation on SQL Server Express is available and highlighted in the Details pane. Finally, a link to the setup log files is available for review.

13. Click Close to exit the SQL Server Setup. Click the red 'X' in the upper-right to quit the SQL Server Installation Center.

Figure   Completion of Setup and summary, documentation, and setup logs

14. Confirm that the SQL Server server and the instance are running by opening the Services console. Open a 'cmd' prompt and type 'services.msc.' In the Services console, locate SQL Server (SQLEXPRESS). The SQL Server instance service will be in the Running state. Close the Services console.

Figure   Services console with the SQL Server instance in a running state

15. The setup of SQL Server to host the database for EZ UDM Express is complete.

Install DHCP

A Dynamic Host Configuration Protocol (DHCP) server is used to assign IP, default gateway, and Domain Name System (DNS) addresses to computers and devices. Additionally, DHCP configures devices and computers with vendor-specific settings. These settings, such as HTTP and HTTPS Bridge Server.

Before installing a new DHCP server, determine if you already have one. Most networks, even the smallest, use DHCP on a server or a network device (router, wireless bridge) to provide DHCP services.
Important! If you are using a network device like a router or other device for DHCP that does not support customer options, you must install software or a device that does support the configuration of new options. Your IP phones will not connect to UDM Express if you cannot configure the required Option 160 and 161.

Refer to the vendor documentation for your network device.

To install a DHCP Server, see the following guidance on Microsoft's Windows Server page.
For Windows Server 2012 R2: Dynamic Host Configuration Protocol (DHCP) Overview
For Windows Server 2016: Dynamic Host Configuration Protocol (DHCP)

Configuring DHCP For EZ UDM Express

Devices require specific configuration options. Setting these options are either manual of automatic. The solution is to use DHCP to set the option on the device. 

Note! Windows Server provides a DHCP server for install, but Windows desktop does not. Third-party software vendors provide DHCP servers for Windows desktop. See the installation and configuration information from the third-party vendor.
When a device is connected to a network and boots, it looks for a DHCP server. If it locates a DHCP server, it requests DHCP Option 66 (Trivial File Transfer Protocol or Boot Server Host Name), and then Option 160, or Option 161 (Vendor-specific string to a host that can provide the boot image for the device.) Option 160 or Option 161 are used to direct the device to the EZ UDM Express provisioning bridge – an integral part of the server.

Important! If your DHCP server uses Option 66 for BOOTP or TFTP, you MUST resolve a workaround not to use Option 66. Most devices use Option 66 first and then will try Option 160, then Option 161. If the device finds an option for BOOTP or TFTP, it will always use it and will not find the EZ UDM Express server. Because Option 66 is a valid option for some devices and a completely different method to boot a device, it is incompatible with the software image process that newer provisioning systems like EZ UDM Express use.

The Option 160 and 161 setting is a string-based setting that is in Uniform Resource Locator (URL) format. For example, the following are both valid:

In some cases, the setting might seem a bit ambiguous. TCP/IP needs a port along with a URL. The default assumption would be TCP Port 80. However, the default TCP port that a device needs to connect to is TCP Port 81. The same example using ports:

To configure DHCP Options for EZ UDM Express, do the following:

  1. On the Windows Server acting as your DHCP server, launch Server Manager. Click Tools, then click DHCP.

Figure   Open the DHCP Management tool

2. In the DHCP Management console, expand the server name of your DHCP server

Figure   Expand your server in the DHCP console

3. Right-click the node IPv4 node and select Set Predefined Options…

Figure   Click 'Set Predefined Options' to create new options

4. In the Predefined Options and Values dialog, Click "Add.."

Figure   Creating a new DHCP custom Option

5. Fill in the following option values to create Option 160:

Name: Option 160 for Devices (Required name for the option)
Data type: String (Select from drop-down)
Code: 160 (Option value that is assigned)
Description: EZ UDM Express Option 160 (Optional value for identification purposes)
Click "OK" to save the settings.

Figure   Values for creation Option 160

6. In the Predefined Options and Values dialog, Click "Add.."

Figure   Creating a new DHCP custom Option

7. Fill in the following option values to create Option 161:

Name: Option 161 for Devices (Required name for the option)
Data type: String (Select from drop-down)
Code: 161 (Option value that is assigned)
Description: EZ UDM Express Option 161 (Optional value for identification purposes)
Click "OK" to save the settings.

Figure   Values for creation Option 161

8. Select the newly created Option 160. In the "string" field, fill in the URL of the EZ UDM Express server and port. For example,

Figure   Adding the string value to the EZ UDM Provisioning Bridge

9. Select the newly created Option 161. In the "string" field, fill in the URL of the EZ UDM Express server and port. For example,

Install EZ UDM

Installing EZ UDM Express is straightforward if the installation of pre-requisites is already installed per the guidance in this guide. To install EZ UDM Express, do the following.

  1. Locate the EZ UDM Express files that you downloaded. Right-click EZUDMExpress_Installer.exe and select "Run as administrator" to begin the installation.Click Next.
  2. If you want to use the default and recommended installation location, click Next to continue. If you prefer to install the application in another directory, click Browse. Select the location where to install the application files. Click Next.

Figure   Choose the default or select a new install directory

3. To proceed with the installation, click Install.

Figure   Dialog to begin the installation

4. Installation of EZ Device Manager Express will begin and display progress as it proceeds.

Figure   Progress dialog during the installation

5. When the installation completes, close the installation dialog by clicking Finish.

Figure   Completing the installation

Login to EZ UDM for the First Time

You log into EZ UDM for the first time from the computer that EZ UDM Express is installed on or another computer on your network.
To log in, do the following:

  1. Open a browser on the computer that EZ UDM Express is installed on or on another computer on your network. We suggest Google's Chrome browser, but we have tested Microsoft Edge, and Internet Explorer 11.
  2. In the space for the URL address, type http://localhost (if this is the computer that EZ UDM Express is installed on) or http://"name of the computer that EZ UDM Express is installed on"

Important! The above URL assumes the default TCP Port 80 is configured and was not in use on the computer that EZ UDM Express is installed on. EZ UDM Express requires the use of TCP Port 80 and Port 81

Figure   Logging in locally

Figure   Logging in from another computer to a computer named 'ezudm' on

3. Apply your license. You can either:

  • On the General activation tab, type or paste your supplied (via the license process) the EDP ID and License Code. Click Activate

     Figure   Activation using EPD ID and License Code   

  • On the Upload a License tab, click in the field Choose a license file (*.lic). In the file explorer, locate your license file. Select the file, and click Open. Click Upload & Activate.

Figure   Activation using a license file

4. Successful activation returns your license information containing the expiry date and number of devices allowed

Figure   Successful activation and license information

5. Click Login now to proceed

6. EZ UDM Express processes the initial login and creates the database. Wait while initialization completes. 

7. EZ UDM Express' Login page will load. Enter Admin as the username and Admin as the password.

Important! The username is NOT case sensitive, but the password is case sensitive. This is true for all password entries you use for EZ UDM Express.

Figure   Enter the default username and password

8. On the first login, you are required to change the password. Enter a new password (case sensitive) and re-enter the same password to verify.

Figure   Fields to change the Admin password

Figure   Fields change from red to green for matching new password entries

9. Click Change Password

10. Initialization of the new passwords and system are complete. The End User License Agreement (EULA) is shown.

11. Review the EULA and click Accept to continue, or if you decide that you cannot accept the terms of the EULA, click Declined and you are returned to the login screen.

Important! You MUST accept the terms of the EULA before you can use the software.

12. You are now ready to start configuring and using EZ PWD Express


Lost Password

It happens. We all forget our password, the person who normally manages the system is out for the day or has left the company. If you ever need to recover the EZ UDM Express from a lost password do the following:

  1. Log on to the computer where EZ UDM Express is installed as an administrator on the computer. You do not need to be an EZ UDM Express Admin to do this.
  2. Open Explorer or the CMD Prompt and go to the directory C:\ProgramData\Event Zero\UDM Express
  3. Delete the file 'ezpwd.txt'

Figure   Location of the file 'ezpwd.txt'

4. In your browser, type http://localhost (if this is the computer that EZ UDM Express is installed on) or http://"name of the computer that EZ UDM Express is installed on" The file 'ezpwd.txt' is recreated with the default username Admin and password Admin. You will be prompted to change the password on the first login.

Testing if Devices Can Connect to EZ UDM Express

If you need to do initial testing to confirm that the port for devices is available and responding, you can do this with a browser if you don't have a device immediately available. Do the following:

  1. From another computer (devices need to connect to the network, and a computer other than the EZ UDM Express is best to confirm this works), open a browser and use the URL http://"name of the computer that EZ UDM Express is installed on":81

For example, +

Figure   Test the ability to connect to T CP Port 81
Note: Message displayed varies from browser to browser. The important point is that a line of text was returned, not an error that the browser was unable to find the web page or an HTTP 404 error.

2. Congratulation! Everything seems to be working normally. Proceed to the User's Guide to setup and configure the environment to manage your devices.

PowerShell Script to Determine the .Net Framework Version Installed on A Windows System

  • No labels


  1. I have no idea why the Import function split some sections into other table-like splits. It's not that way int he regular doc that I imported. I'll have to play with this to get it right for Confluence. Regardless, this is just a draft.

  2. Just reviewed this document, it is very accurate and is exactly what we need for the installation document. The best 'draft' I've ever seen.  Will need this in PDF format at some point, something we can ship to customers after a demo is complete (or a valid public URL).  Rick, maybe add a note on step 4 above that this step is processing a very large schema file and updating the SQL database, thus, this step can take 10 minutes or longer.  Please be patient. 

    1. Thank you. PDF will not be an issue.

      10 minutes? You must be seeing some really, really fast times. Using Google Dev Tools and SQL Profiler, I've been doing tests. The SQL Updates are massive.  Lots of commits. Currently, my record FAST time is 36.7 minutes.

      1. Takes me about 10 minutes...but I'm on a SD disk.  Good point there though, maybe don't put a time limit, just note that it can take a LONG time.  I can already see people getting frustrated.  Seems we should make this step as part of when the app is first run, but maybe no need to make a big deal about it?

        1. I'm doing the installs and testing in my Hyper-V server. This is the reason that we need a comprehensive test matrix of different OS, SQL, disk types, configurations - much like I suggested last week. The main problem is: Depending on what we're deploying on - if it's not very similar to what the customer will use (and we can't KNOW, we can only set recommended configurations), we can't set expectations or tune if there is an overt problem that might be overcome.

  3. Jason Weaver Chris Clark Mike Kraut Ken Lasko Version of the Install docs with some update and addition of the installation and configuration guidance for DHCP and scope options is now ready for review. Jason - I've not missed your asks. They will be in the next version.

  4. Jason Weaver Chris Clark Mike Kraut Ken Lasko An ask to help facilitate getting the docs wrapped up: If there are specific things that need to be added to the docs, please put them here. Some of the comments sections for the software is getting so big and hard to track down items, I'm afraid that if you ask for something to be included in the docs - I'm going to miss them if they aren't here. I'm trying to track all requests, but if they're here - it's one stop shopping and a guarantee that they will be reviewed for inclusion. If on another page that has 60 or so comments - yeah, that's a bit harder.

    (And, before someone happens to mention it, I'm familiar with 'Search' on a web page!  (smile))

  5. Hi is there a 'using and configuring UDM' doc? thanks

    1. no not yet and if you are curious the default username and password is Admin/Admin case sensitive (wink) 

    2. Right, Rick is working on this did the install go using the info he wrote above?  Also, note the phone needs to be setup to run on http:\\localhost:81 (port 81) by default.

  6. Install guide was more than adequate for me, with only one complaint/suggestion. We need to specificy that the default user name and password is case sensitive Admin/Admin. A guide covering basic use of the app would also be nice, however, I found it fairly straight forward. Used Windows 10 and SQL Express 2016, modified the DHCP options on my Meraki instead of spinning up a Windows DHCP server. Application works as expected. My VVX 410 was picked up instantly and firmware was uploaded and pushed to the phone successfully. Great job all! My only concern is that the firmware takes too long to upload especially considering this is a local installation. While the firmware was being processed SQL was barely utilizing any resources, however, the IIS worker process was under significant utilization for the 14 minutes it took to process the firmware. I can confidently say in my lab SQL was not the bottleneck. Great job all! 

    1. The password is case sensitive and username is NOT (smile)

  7. Yes install guide was great for me but I installed on 2016 server and had some beefs installing the components via server manager. I was thinking we should add the powershell cmdlets to install the components or maybe a simple script to do it to the instructions?

    1. What issues did you run into using Server Manager on 2016? Can you give me some specifics? I've installed on 2016 and didn't seem to have any issues. I'd like to try and repro so I can adjust the docs as needed.

  8. I have it up and running and it looks like my device hit the server. One question, you can upload resources like background imagers but how do you assign them to the device set? maybe I'm just slow (smile)

    1. There is not a wizard to do that, so you have to figure it out. I use P1 to do this, but to make it even easier for Sir Johnny Cookie you can andd these XML's to a set (or globals):





      1. hooters.jpg needs to be in the resources list

        1. thanks. So you can upload the resource but currently no way to assign it in the gui. Ok as long as that's documented. (smile)

          1. You can assign it, there just is not a wizard around it. You can assign ANY standard XML using the system.  The 3 commands above tell teh endpoint to show Alex's favoriate Hooters Model, even though it is a dude (smile)

          2. John Cook Please try the steps:

            • Go to "Resources" tab
            • Upload the image
            • Go "Device Sets" tab
            • Edit for "Global"
            • Confirm you have the device Mac address in Device list
            • Click "Manual Entry" down to the Assign XML attribute to device set part
            • enter the 3 attributes name and value then Save
            • Restart the device
            • You should see the image background

  9. And so I'm clear, its port 81 that the devices need to be sent to in order to connect?



    1. yes, I am using this (on port 91) http://localhost:91

  10. Hi I am seeing this, and I may be doing it wrong, but when I upload a split firmware file, I see it in software but I don't see anything in the gui. And i cant assign it?

    1. Mike, can you confirm this?  sounds like an issue with the UI?  Mine works fine, not sure what is happening-

    2. John Cook Hit a similar issue. Which firmware - name of file exactly? And when you upload it, does it go through the whole process (you see the upload process, then the Processing spinner, and it takes > 10 minutes or so?) Or, does it show the upload percentage, you see the processing spinner for about 30 seconds, and then kicks you back to the Admin login?

      Part of a thread with Mike Poon:


      Thanks for looking at this. I’ll check into those potential issues. I’ll see if someone else will look at it as well. 

      In reference to the below:

      • The error only occurs only for that specific software?

       (RK) This is the only one that is currently failing for me. Of the five I’ve tested, so it’s far from comprehensive, but it’s a good cross of all software for our currently supported devices.

      • Do you have a copy in C:\Program Data\Event Zero\Software? If yes, please manual delete it.

      (RK) I do not. This was after rolling back to a checkpoint (VM) and re-installing with 1.11.

      • Are there any software 5_4_5 in database table “firmwareVersions”?

      (RK) I don’t believe so. If that’s the case, then we have our answer. I’ll need to be sure and doc in the User’s Guide that you should not use multiple ‘versions’ of the same software release, e.g. 5_4_5 Combined and 5_4_5 Split. They are, as we know, essentially the same – only different formats and hence – redundant.

      (RK) Unless someone else can duplicate my issue, we should consider this a ‘one off’ and not worry about it.

  11. I tried this on safari mac and edge on win10.

  12. Just wonder you guys using Admin installer or Normal installer? Are there any issue with Admin installer? If not, I'll create Admin installer only for next release

    1. I used it today w/o issue. That'll require the user to run it in admin mode, so we will need to document or will it run normally as well?  I have never had an issue with either to date-

      1. Good suggestion, Jason. I believe that I've already documented to Run as Administrator, but I also think that Mike is going to tick the box (so to speak) in the Installer to force it to run as admin. Doing this bypasses other issues during the install process and is the best way to install the software, especially if we're going to spawn child installers (e.g. .Net, SQL Express).