Skip to main content
Version: On prem: 15.0.3

Omada Identity Enterprise Server

Here you can find information on how to:

  • Install Omada Identity Enterprise Server
  • Configure the Windows and SQL Server platforms
  • Initial configurations needed for the Enterprise Server.

In addition to installation and configuration information, you can also find information on the SQL Server configurations and settings for different setup scenarios. Information about security and licensing are also provided as well as general tips and troubleshooting.

Upgrade a previous version to 14.0

If you are upgrading the software to a new major version, there are two rules:

  • You cannot skip a major version. For example, if you want to upgrade from Omada Identity v11.1 to Omada Identity v14, you must first upgrade to Omada Identity v12.3.
  • You must always be on the latest patch version before upgrading to a new major version, for example the latest patch for v12.3.xxx.

Enterprise Server Installation​

note

Here is a single-tier installation of Enterprise Server described.

If you upgrade to a new patch release, you are not prompted for any details. To add new features, run the installer a second time after the upgrade.

Install Enterprise Server​

Before you begin the installation process, make sure that you have installed Microsoft.NET Framework 4.8.

  1. Double-click the OIS Enterprise Server.exe file to launch the installation wizard. Once the Preparing to install screen is replaced by the Welcome page of the installation wizard, click Next.

  2. Click Next to install the software to the default destination folder, which is C:\Program Files\Omada Identity Suite\Enterprise Server 14. Alternatively, click Change to specify a different folder.

  3. Specify the user for which the application pool and services are going to run (for Service Account only), then click Next.

    note

    Refer to the CIAM Installation and Configuration guide to learn more about creating a CIAM Service Account.

  4. Select the software you would like to install, then click Next.

  5. Click Install. The program features that you selected are now installed. Click Next when the process completes. Click Finish to complete the installation.

Command line installation​

You can run a silent installation from the command prompt. The following example installs all features to the default installation path, using a named user as the account that is going to run the Omada Services.

OIS Enterprise Server.exe /v\"INSTALLDIR=\"C:\Program Files\Omada Identity Suite\Enterprise Server 14\" SERVICETYPE=\"2\" SERVICEDOMAIN=\"test\"SERVICEUSER=\"testservice\"SERVICEPASSWORD=\"xxxx\" /qn\" /s

Use SERVICETYPE="1" to use the Local System Account as the account that is going to run the Omada Services. You can change to another user at a later time you need to.

You can specify which features to install by adding an ADDLOCAL parameter with a comma-separated list of the features to install. The following features are available:

  • Omada_Enterprise
  • PasswordReset
Example

The following example shows how to install Omada_Enterprise and Tools.

OIS Enterprise Server.exe /v\"INSTALLDIR=\"C:\\Program Files\Omada Identity Suite\Enterprise Server 14\" ADDLOCAL="Omada_Enterprise,Tools" SERVICETYPE=\"2\" SERVICEDOMAIN=\"test\" SERVICEUSER=\"testservice\" SERVICEPASSWORD=\"xxxx\" /qn\" /s

You can test the parameters by running the command without /qn and /s. This opens the install wizard with the specified parameters inserted, enabling you to confirm the settings.

Installing different versions of the Enterprise Server​

If you need to run different versions of Enterprise Server, you should manually install the software in a distinct folder by typing:

Start > Run > **msiexec /a OIS Enterprise Server.exe**

This command is necessary because you can only have one Timer Service running. It should work for all databases.

note

This is only necessary for installations within the same minor versions of Enterprise Server. For this release, that means 14.0.x-versions.

When you configure each website with different ports (or different IP addresses), each website can then run 'independently'. The IISRESET command affects all websites.

Create a database​

Because Enterprise Server requires an empty database, you must create a database in SQL Server. For detailed instructions on how to create a database, see Install IIS and create a database.

  1. In SQL Server Management Studio, create a new database and give it a name, for example, Omada Identity.
  2. Make sure that the service account running the Enterprise Server is assigned the db_owner role for the database.
  3. If the user who is accessing the Enterprise Server database is not allowed to have the db_owner role because of company or SQL Server policy:
    • Install the db_omada role on the SQL server using the script db_omada.sql.
    • Grant the user who is accessing the Enterprise Server database the following roles: db_omada, db_datareader, and db_datawriter.
note

While creating the ES database, you must make sure that you have turner ON both read_commited_snapshot and allow_snapshot_isolation settings in the ES database before you use the Omada Identity software. This setting is required for proper operation of the ES.

Create a connection to the database​

After you have installed Enterprise Server, you must use the Omada Enterprise Configuration utility to connect your installation to the database.

  1. In Windows, click the Windows button, then select Configuration to open the utility.

  2. Click OK in the welcome dialog box. The program prompts you for the connection string to connect to the Omada Identity database. This is the one that you created earlier.

  3. Enter the connection string, and then click OK.

  4. Click OK to confirm that the latest database version is to be installed. The program now creates tables, views, and stored procedures for the Omada Enterprise database.

  5. Enter the name of your company, and then click OK. Note that you must type in the same name as the Company Name in your license key. Click OK to finish the configuration.

Database back-ups and restoration

Omada recommends that you make backups of the Enterprise Server database on at least a daily basis, preferably more often. This is both common and best practice. Database backups can be performed automatically by configuring a SQL Agent job.

Specify a connection string for the source system's data database​

To specify a connection string for the source system database, go to Tools -> Source System Data database connection.

Important

You must create the source system data's database before yoy specify the connection string, otherwise you will receive an error.

Set-up the Web Application in IIS​

Now that you have installed Enterprise Server, you must create and configure the Omada Identity web application.

Edit IIS Settings​

  1. In Windows, click Start -> Administrative Tools to open Internet Information Services (IIS) Manager, then expand the menu in the navigation pane on the left.

  2. Right-click Sites and select Add Website.

  3. In the Add Website dialog, type OIS as the Site name and C:\Program Files\Omada Identity Suite\Enterprise Server\website as Physical path, then click OK.

  4. An associated application pool is automatically created. Click Application Pools. OIS now appears on the list.

  5. Right-click the OIS application pool and select Advanced Settings.

  6. In the Advanced Settings dialog, specify the settings as shown in the image below.

  7. In the Set Credentials dialog, enter the service username and password. After confirming the password, click OK.

  8. The service user name is now displayed in the Identity field. Click OK.

Edit Default Document settings​

  1. Next, you must edit the Default Document settings and the Authentication settings for the OIS site. Start by double-clicking Default Document in the IIS section.

  2. On the Default Document page, right-click and select Add, and add main.aspx as a default document. Remove the other entries.

  3. Return to the OIS Homepage and double-click Authentication in the IIS section.

  4. Right-click Anonymous Authentication and select Disable.

  5. Right-click Windows Authentication and select Enable. The Authentication page should look like this:

  6. In the IIS section, right-click and select Basic Setting, then in the Edit Site dialog, click Select to use OIS as the application pool and click Test Settings.

  7. Click OK to save your settings.

Authenticate Users​

If you want the Portal to authenticate users with user name and password, you can disable Integrated Windows Authentication. The following steps describe how to do this.

  1. Open the Internet Information Services (IIS) Manager, go to Home, and double-click Authentication.

  2. Enable Anonymous Authentication and disable Windows Authentication.

Log on to the application​

By default, only one user named Administrator, with an empty password, is available for you to log in with.

note

The user table in Omada Identity also contains of three other artificial users that are used by the system only.

  • ACTUSER is used in filter expressions to express a variable being replaced with the active user during the evaluation.
  • SYSTEM is the user who executes the code when it is not running in the context of an interactive user in a web browser. For example, the timer service and RoPE are running in the context of the system user. Also, CodeMethods can be configured to run as the system user.
  • NONE is used as assignee on activities that do not have any other assignee yet.

There are two different approaches to how you can log on as an administrator to the application. They are described in the following sections.

Use anonymous authentication​

If you have enabled anonymous authentication, perform the following steps to log on with a user name and password:

  1. Open your web browser, and connect to the web server, for example, http://localhost/OmadaEnterprise/main.aspx.

  2. Enter Administrator as the user name. Do not enter a password.

Use integrated Windows authentication​

To log on with Integrated Windows authentication, log on to the web server (console or Remote Desktop) with the Administrator user.

  • Open your web browser on the web tier and connect to the local web server.
note

To avoid using the Administrator user, you can log into the application using anonymous authentication and manually create accounts in Enterprise Server for a few relevant users, before enabling Windows Authentication.

License keys​

You must install a license key for each installation. The key is stored in the database, and you normally just need to install it once for each database. However, if the license conditions change, new license key installations might be necessary.

Request a license key​

To request a license key, contact your account manager or the Omada sales department at sales@omada.net. You must submit the following information to obtain a key:

  • Company Name
  • Address (multiple if applicable)
  • Contact person
  • License key type (normal, demo, or trial)
  • Number of Users
  • Number of Process Templates
  • Number of Identities

License key types​

There are three different types of license keys that you can request for Omada Identity.

SettingDescription
NormalA normal license key enables you to use the system without any time limits.
You must upgrade this license key each time you install a new version of Omada Identity.
DemoA demo license key is meant for Omada partners so that partners can demonstrate Omada Identity for a third-party company or individual.
Demo license keys have a time limit, so you must update this type of license key after the license has expired.
TrialA trial license key is meant for potential customers and partners who request a demonstration of how the system works.
The trial license key has a time limit and will expire.

Install or update a license key​

  1. Log in to the Omada Identity Portal.

  2. Follow the step in the top of the screen to enter a license key.

  3. Paste your new license key into the field and click OK. Your license is now updated.

note

Only Platform administrators can update the Omada Identity license keys.

Omada Identity API Documentation

The Omada Identity API documentation is where you can find documentation of the built-in collection of code methods, public JavaScript and other information written by Omada developers.

This documentation is available in compiled HTML format (.chm file). You must run this file locally on your computer. If you do not run the file from your local machine, Windows does not allow you to open the file.

You can find the compiled HTML format (.chm file) of the Omada API Documentation Site at the following default location: C:\Program Files\Omada Identity Suite\Enterprise Server\documentation\OIS-X 12 documentation.chm.

Service User Rights​

Logging on as a Service​

You must give the service account(s) used for the Omada Identity Services the right to Log on as a service in Local Policies.

Database owner​

The service account(s) used for the Omada Identity Services must have the db_owner role in the Enterprise Server database.

If the user who is accessing the Omada Identity Enterprise Server database is not allowed to have the db_owner role because of company or SQL Server policy, do the following:

  • Install the db_omada role on the SQL server using the script db_omada.sql.
  • Grant the user who is accessing the Enterprise Server database the following roles: db_omada, db_datareader, and db_datawriter.

Access to the MSDB database​

The service account(s) used for the Omada Identity Services must have the following role memberships for the MSDB database:

  • db_datareader
  • db_ssisadmin

If SQL Agent is used, also the following role is required:

  • SQLAgentOperatorRole

Set read Access to Perflib Registry Key​

The service account(s) used for running the Omada Identity Services the IIS Application Pool must have Read Access to the following registry key:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib

This is for the Key Performance counters to run. This is set in the permissions for the registry key in the Registry Editor.

  1. Right-click the registry key, and select Permissions...

  2. Click Add... and search for the service account.

  3. Select Read in the Permissions section and click Apply.

Full-text indexing​

A full-text index is by default enabled in the Enterprise Server if the SQL Server full-text service is installed on the database tier. The full-text index improves the scalability and performance of the search function. If it is not enabled, there might be performance issues when the data set reaches a certain point.

tip

Omada recommends that full-text index is enabled in the production environment. It can be disabled for the development and test environments.

  1. To configure the full-text indexing, start the Omada Enterprise Configuration utility by clicking Start -> Configuration.

  2. In the Tools menu, click Create full text index.

  3. Then click Add Columns to full text, followed by Full text change tracking auto.

  4. Go to Services and make sure that the MSSQLSERVER service is set to Automatic startup in case the server requires a restart.

  5. In Enterprise Server, go to Setup -> Administration -> Other -> Customer Settings, then set the Disable Searching in the FTI setting to False and click OK.

Initial configuration​

The Enterprise Server installation installs two services:

  • Omada Identity Timer Service

The default startup type of these services is Manual. For this reason, you may want to change this property for the Timer Service and the Role Engine Service. See the image below:

note

The services are set to manual startup by default. After an installation, upgrade, or patch has been applied, you must start the Timer Service and any other services that you require.

If you are using Microsoft Security Support Provider Interface (SSPI), you must assign a specific user to two of these services.

The service account(s) used for the Omada Services must be given the right to Log on as a service in Local Policies and the db_owner role in the Enterprise Server database.

Those services requires configuring the following settings to ensure that the software reflects local preferences.

To configure the customer settings, go to Setup ->Administration -> More... -> Customer Settings.

The most relevant customer settings to configure are listed in the table below.

SettingDescription
Mail senderThe email address that you provide here is used as the From address for any emails that are sent from the system.
Support emailType the email address used for reporting errors.
Support email (auto)Type the email address to which automatic, system-generated error reports should be sent.
Website URLType the full URL to the site. Example: http://OIS.somecompany.com/
Disable full text index searchingIf you set this setting to False, you enable the full-text search.
 
Important

When enabling OpenID or SAML, you must perform additional mandatory changes to tblCustomer and tblCustomerAuth. These tables must be edited using SQL Management Studio.

Any changes to authentication settings take immediate effect, and precipitate changes may lock out the user changing the Master Settings out of the Omada Identity system.

Maintain the Omada platform​

To ensure that Omada Identity runs well, it is important that there is a continuous maintenance of the SQL server. Because schedules vary from customer to customer, the requirements listed here are only basic requirements.

A more advanced setup of maintenance plans should be discussed between the customer's IT department and Omada Consultants.

Set up SQL server maintenance plans​

From the SQL Server Management Console, you can set the database maintenance plans to match the local requirements and service windows. You can do this in Management -> Maintenance Plans.

  1. Set up a plan to update the statistics on a regular basis, preferably every night.

  2. Set up another plan to reorganize data and index pages at least once a week.

Using SSPI​

Using the Security Support Provider Interface (SSPI) requires configuring following settings.

Configure Active Directory settings​

  1. Create an Active Directory service account to be used for the integrated authentication between the web or application server and the SQL Server.

  2. Log on to the Domain Controller with Domain Admin rights and execute the following command:

    Setspn --s HTTP/<webserver fqdn> <DOMAIN>\<service account>

Configure Web/Application server settings​

  1. Add the newly created AD account to the local user group IIS_IUSRS on the web server.

  2. Set up an application pool in the IIS to use the newly created AD service account. Setting up an application pool in IIS is described at the end of this section.

  3. Change the Enterprise Server web application to use the newly created application pool.

  4. Change the connection string to:

    Initial Catalog=<db name>;Data Source=<db server name>\<DB INSTANCE>;Integrated Security=SSPI;

    Example

    Initial Catalog=OISTST;Data Source=DBSRV01\TST;Integrated Security=SSPI;

  5. Run the following command in the folder C:\inetpub\AdminScripts:

    cscript adsutil.vbs set w3svc/NNTAuthenticationProviders "Negotiate"

Authentication with Kerberos on Windows 2016 or newer​

When you use Windows Integrated Authentication with Kerberos on Windows 2016 or newer, you may need to change the ASP.NET authentication function to use the AppPool credentials.

  • Open a command prompt and enter:

    cd %windir%\system32\inetsrv

    appcmd.exe set config -
    section:system.webServer/security/authentication/windowsAuthentication - 
    useAppPoolCredentials:ture

    Alternatively, you can disable the IIS authentication kernel mode authentication.

  1. In Internet Information Services (IIS) Manager, expand the local computer's node, expand Sites, and click the website.
  2. In the center pane, under IIS, double-click Authentication.
  3. Click Windows Authentication.
  4. In the right-side pane, under Actions, click Advanced Settings.
  5. Clear the check box Enable Kernel-mode authentication. Click OK.

SQL Server Settings​

  1. On the SQL Server instance, you must create a new login equal to the newly created AD service account.
  2. Go the Enterprise Server database and create a new user with the newly created login.
  3. Assign the database role membership db_owner to the newly created user.

Omada Identity Windows Services​

After configuring all the settings listed here, you must change the Timer Service to use the newly created Active Directory service account.

Remember to set the Windows services as described here, each time you apply a patch to Enterprise Server.

Configuring SSL​

  1. Start Internet Information Services Manager, then select the relevant server and double-click Server Certificates in the main pane.

  2. In the right-side menu, click one of the available options to launch a wizard that helps you create a request for a server certificate. The request is delivered to a certificate authority that can grant a certificate. The response is brought back to the wizard, and the certificate is then installed.

    note

    The certificate's common name must match the DNS common name on the Web server, typically using certificate authorities, such as VeriSign or Thawte. However, internal solutions often choose an internal certificate authority, which requires that all internal PCs must have the appropriate root certificate installed. This is Omada's best practice advice.

    It is critical that you select the correct setup to match your security and usability needs. Therefore, contact your own IT support to ensure that the best solution is chosen for your enterprise.

  3. After the certificate is installed, select the website, and open the Site Bindings dialog. Click Add and create an https site binding using the installed certificate.

  4. Select SSL Settings in the main pane and select Require secure channel (SSL). If you enable this setting, all network traffic is encrypted with the server certificate.

note

The described solution does not cover client certificates.

Check the system security​

When your Enterprise Server installation is complete, you can apply security to the installation.

  1. Change any blank passwords that were used during installation into secure passwords. Your company should already have a password policy in place. Omada recommends following password best practices such as:

    • Periodic password changes and no recycling of passwords
    • No dictionary words or names
    • Minimum 6 characters
    • No passwords that contain user names, real names, or company names
    • The inclusion of English uppercase and lowercase characters (A-Z and a-z), Base 10 digits (0-9), and symbols found on the keyboard such as ! $, #, or %.

  2. Contact your auditors to include your Enterprise Server installation in future routine audits that include security checks.

Right after the Omada Identity is installed, the PswEncryptionKey has the default value DefaultEncryptionKey. You need to change this value as soon as possible after the installation, preferably before performing any other actions within Omada Identity.

The PswEncryptionKey change must be performed manually in all the places where it is used.

For more information of PswEncryptionKey, please refer to Password encryption key

The following table shows a sample checklist for ensuring the security of your implementation:

ActionNotesResult
Change the PswEncryptionKey from the default one.Refer to Password encryption key
Change administrator password from <blank>.See the password best practices described in step 1 above.
Use SSPI connection instead of username/password.To avoid having the username and password stored in clear text in the registry.
Activate SSL.Optimize security.
note

This is security for your environment and is therefore unrelated to the security settings within the installation. For information about security in Omada Identity, go to Security settings

Omada Identity audit database​

Omada Identity Audit Database is designed specifically for reporting purposes. This chapter explains how to configure the database.

Configure the audit database​

  1. Create an empty SQL Server database and name it, for example, OmadaEnt_Archive.

  2. Enable SNAPSHOT_ISOLATION in the archive database:

    ALTER DATABASE OmadaEnt_Archive SET ALLOW_SNAPSHOT_ISOLATION ON

    ALTER DATABASE OmadaEnt_Archive SET READ_COMMITTED_SNAPSHOT ON

  3. Grant the db_owner role permissions to access the archive database for the Enterprise Server service account user (when you use integrated security) or for a SQL user.

  4. Go to Setup -> Connectivity -> Data Connections.

  5. Open the connection ESARC and edit the ADO connection string accordingly.

Configure object types for auditing​

  • In the Data Object Type dialog box, configure the object types that should be replicated to the audit database by ticking the Enable archiving checkbox.
  • When an object type is configured to be replicated to the audit database then a table named "tbl[system name of object type]", for example "tblIdentity", is created in the audit database.

Database schema​

The database schema in the Omada Identity Auditing Database goes through maintenance automatically. If you make any changes to the Enterprise Server's object model, for example, when you add a property binding to a data object type, you must restart the Omada Identity Timer Service to refresh the target schema.

  1. DataObjects

    DataObject versions are stored in a table that is named according to the configuration, for example, tblIdentity for identity objects. Columns in these tables are named according to their System Name property.

    There is a _DELETETIME column in each table. In this column, NULL indicates the current value.

  2. Multivalued properties

    Multivalue reference properties and multivalue set properties have their own reference table in the auditing database. For example, the Manager property on the tblIdentity is stored in a tblIdentity_MANAGER table.

  3. Set and multilingual property values

    Set property values and multilingual text property values get a column for each configured language. For the type Identity, there is an Identity Status property that is transported into the columns IDENTITYSTATUS_ENGLISH and IDENTITYSTATUS_DANISH, when the English and Danish languages are requested.

  4. Data object types with built-in properties

    When special built-in data object types, namely Users, Processes, and Activities, are included in the configuration, their properties are handled as indicated in the following table.

    Data Object TypeProperties Archived
    Users_USERNAME
    Processes_State, _Target, _AbsDuration and _Duration
    Activities_State, _Process, _FirstActiveTime, _ActiveTime, _AbsDuration, _AbsDuration2, _Duration2

  5. UserGroup memberships

    Enterprise Server internal UserGroup memberships are stored in the table tblUser_MemberOf, where the _DELETETIME column indicates whether the row has a current value.

Limitations​

File attachments are not stored in the Omada Identity Audit Database.

Reference property attribute values are not covered by the archive feature. Most notoriously, resource assignment attribute values are not represented in the archive database.

Install IIS and create a database​

Omada Identity Enterprise Server requires an empty database, so you must create one in SQL Server.

note

While creating the ES database, you must make sure that you have turned ON both read_committed_snapshot and allow_snapshot_isolation settings in the ES database before you use the Omada Identity software. This setting is required for proper operation of the ES.

  1. Click Start -> All Programs -> Microsoft SQL Server -> SQL Server Management Studio.

  2. Click Connect. The server type must be Database Engine, Server name is (local), and Authentication must be set to Windows Authentication.

  3. Right-click Databases and then click New Database.

  4. Enter OmadaEnt as the database name and, if necessary, change the default location of the database files. Click OK to create the database.

  5. Make sure that the service account running Enterprise Server is assigned the db_owner role for the database.

If the user who is accessing the Enterprise Server database is not allowed to have the db_owner role because of company or SQL Server policy, do the following:

  1. Install the db_omada role on the SQL server using the script db_omada.sql.
  2. Grant the user who is accessing the Enterprise Server database the following roles: db_omada, db_datareader, and db_datawriter.

Install IIS on Windows Server​

This section describes how to install IIS on Windows Server and how to configure IIS on installations with remote users.

For information about configuring application pools in IIS, see the Set-up the Web Application in IIS.

note

For security reasons, you may need to add the installation URL to your web browser local intranet zone.

Install IIS on Windows Server 2016 and later​

  1. Click Start -> Administrative Tools -> Server Manager to start the Server Manager.
  2. Click Manage -> Add Roles & Features to open the Add Roles & Features Wizard.
  3. In the Installation type page, select either Role-based or Feature-based installation.
  4. Select the correct server in the Select destination server page.
  5. On the Server Roles page, select Application Server and Web Server (IIS). The pop-up window Add features required for Web Server (IIS) may appear when you select Web Server (IIS). In this case, click Add Features in the pop-up, and then click Next on the Select Server Roles page.
  6. On the Select features page, make sure that .NET Framework 4.8 (including ASP.NET 4.8) is installed. If it is not, you must install it. Click Next.
  7. Read the informational message for Application Server and click Next.
  8. Select Web Server (IIS) Support in the Select role services page. Click Next.
  9. Read the informational message for Web Server Role (IIS) and click Next.
  10. In the Select role page, review the Role services that you have selected to be installed. Click Next.
  11. In the Confirm installation selections page, select Restart the destination server automatically if required, and click Install.
  12. When the installation is complete, the Installation Results page opens. Check that the Web Server role services were installed successfully and click Close.

Install IIS on Windows Server 2008​

  1. Start the Server Manager by clicking Start -> Administrative Tools -> Server Manager.
  2. In the tree view select Roles.
  3. In the Roles Summary pane click Add Roles to start the Add Roles wizard.
  4. On the Before You Begin page click Next.
  5. On the Select Server Roles page select Application Server and click Next.
  6. On the Application Server page click Next.
  7. On the Select Role Services page select Web Server (IIS) Support and then click Next.
  8. On the Web Server (IIS) page click Next.
  9. On the Select Role Services page, leave the default configuration as it is, and click Next.
  10. On the Confirm Installation Selections page read the informational messages and click Install to start the installation.
  11. The Installation Progress page now shows you the features that are being installed and the progress of the installation.
  12. When the installation is complete the Installation Results page opens. Check that the Web Server role services were installed successfully and click Close.

Configure IIS on Installations with Remote Users​

Omada recommends that you enable content expiration on the IIS instance for installations with remote users because this improves performance.

  1. Open the HTTP Response Headers in the main pane for the website in question and click the tab Set Common Headers....

  2. Select Expire Web content and set the number of days that can elapse before expiry.

note

For slow networks Omada recommends setting the Web content expiration time to 7 days. In such cases, 7 days before planned upgrade, the cache need to be set to 3 hours and increased right after the finished upgrade.

Tips and troubleshooting​

If you experience frequent restarts, set the following to True:

Aspnet.config = <legacyUnhandledExceptionPolicy enabled="false" />

If you have problems uninstalling an Omada service, use the following:

.netv2.0\\installUtil -i OmadaOeservice.exe

If the user who is accessing the Enterprise Server database is not allowed to have the db_owner role because of company or SQL Server policy, do the following:

  • Install the db_omada role on the SQL server using the script db_omada.sql. Grant the user who is accessing the Enterprise Server database the following roles: db_omada, db_datareader, and db_datawriter.

Security software blocking network traffic between web browser and web server​

Under some circumstances, if the Omada Identity was not deployed with the use of HTTPS protocol (as recommended), anti-virus software or other security components can block the HTTP network traffic. Consequently, such a block causes issues between the end user's web browser and the ES web server. For example, it may cause problems during the import of changesets, which simply stops without further progress.

This issue has been identified, for instance, when using F-Secure's browser plugin in combination with it's Advanced Network Protection feature. In such a situation, the issue can be resolved by adding the HTTP site to the exclude list of the F-Secure client or turning off the Advanced Network Protection completely.

However, Omada recommended solution is to deploy Omada Identity utilizing HTTPS.

Installing updates​

The following tip simplifies your update installation procedure.

  • Store a backup of the connection string under a key called ConnStr_ in the registry editor: HKEY_LOCAL_MACHINE -> SOFTWARE -> Omada -> Omada Enterprise.

If a backup connection string exists, it is recovered during the installation and the Omada Timer service also starts.

note

Remember to update your backup copy when changing the real connection string. Be careful when you manually change anything in the registry.

Later uninstalls of Enterprise Server does not clear the registry of Enterprise Server content. The program works with the Omada Windows Server Component certification.

Web farms​

When you deploy to an installation where Enterprise Server is load-balanced between several web servers with, for example, WNLB, you must add a machineKey to the Web.config file.

The machineKey section should be added to the bottom of the system.web section:

    <system.web>

    ....

    <machineKey ....>

    </system.web>

The change to the Web.config file must be made after each Enterprise Server patch release because when you apply a new patch, manual edits are overwritten.

For more information about configuring machineKey, see Web Farm Deployment Considerations at How To: Configure MachineKey in ASP.NET 2.0.

Batch jobs​

With batch jobs, consider the web.config setting <httpRuntime executionTimeout="90">

You should set the value to the time it takes for batch jobs to run. Otherwise, the jobs may not finish. The value of 300 is a good starting point.