Guidelines for installing Multi-tenant 2014 R2 or above

[#1]

Summary

This article provides some additional guidelines for installing 2014 R2 or above in a multitenant (MT) environment and should be used in conjunction with the single tenant (ST) installation guide.

Synopsis

The process for installing a Multitenant (MT) version of 2014 R2 or above differs in some ways from a single tenant installation, this article covers the areas where this differs.

Discussion

?Here are a bullet point list of key points when installing an MSP system, highlighting where it differs compared to a regular FNMS install.

1. Flexera licences are different for an MSP system ? make sure that multi-tenant licences are requested at the point of ordering licence generation.
2. You must use SQL Server Enterprise ? Standard edition will not work for multi-tenant installations due to partitioning requirements.
3. Use the partitioned scripts to install the database. In 9.2 multi-tenancy needed to be configured on a database with a stored procedure. This is no longer supported: the partitioned scripts install with multi-tenancy enabled. You cannot use a database created with the scripts from the ?Normal? script directory for multi-tenancy.
4. When installing the system, the user running the installation is added as the first operator in the system. They will automatically be the only operator in any new tenant that is installed with the activation Wizard.
5. After you create a tenant, you need to login as the installation user to that tenant and use the UI to add the accounts of any users that require access to the tenant. It is possible to change the default administrators that are created when a tenant is installed, but this can only be done directly on the database. Contact support if this is necessary.
6. At least one domain user is required per tenant for their beacons to authenticate.?
   • You should be able to create these users from the UI.
   • They don?t need admin permissions, adding them to the readonly role is sufficient.
   • This domain user must only be added to tenant they are used for.
7. Adding an account used for beacon authentication in one tenant to another tenant will cause authentication to fail in both tenants. There is no warning for this, so be careful. If this does happen, run the stored procedure: EXEC dbo.ComplianceOperatorConvertGlobalOperatorToTenant @OperatorLogin = 'DOMAIN\username', @TenantUID ='TenantUID'.
8. This will ensure that the operator will be associated with one and only one tenant.
9. We do not support installing a beacon on a multi-tenant application server, instead the beacon needs to be installed on each customer premises or at the very least on a separate server as the Beacons are specific to each tenant.

Additional Information

Sizing guidelines are no different for a MT installation, as the number of devices under management increases for each tenant so does the sizing as per the guidelines in the release notes.

Multiple server installations from the start is recommended to allow for growth i.e. separate the following:

• Inventory Database
• FNMP Database
• Presentation Server
• Batch / Reconciliation Server
• Inventory Resolver Server

The Inventory and FNMP databases can be on the same server but should definitely be on separate databases.

There is currently no method for migrating from Single Tenant to Multi-Tenant however this is being planned for a future release.