Installer

This guide explains the installer screens, fields, options, and installation paths for clients and consultants installing or updating Any2Info on Windows 11 or later, or Windows Server 2019 or later. Field names match the installer. Defaults below apply when starting a new installation; selecting an existing instance can load different saved settings.

Hover over a field, checkbox, button or its label for a short explanation. Disabled settings also have hover help, so you can understand why an option is relevant without enabling it.

Downloads

Placeholder: download links per version will be added here.

Before starting

Run the installer as a Windows administrator on the Windows computer where the selected applications will run. The installer manages local IIS configuration, files, Windows services, certificates, and installation settings in the Windows registry. The SQL Server may be on another machine. The Connected server fields identify this local computer; they do not select a remote deployment target.

Have the following information ready:

• A permanent instance name, the target version, and the installation folders.
• The SQL Server address, suitable SQL credentials, and names for all four Any2Info databases.
• The IIS website name, public HTTPS URL, port, and website certificate.
• The required Datahub installation mode and its settings.
• An initial Any2Info administrator account for a clean installation.
• Microsoft Graph application credentials if the Outlook add-in is required.

Install IIS and the application prerequisites specified for your Any2Info release before running the wizard. Enable IIS through Windows features on Windows 11, or install the Web Server role on Windows Server. The wizard deploys the supplied applications; selecting Install IIS packages does not enable IIS or automatically provision the other prerequisites.

Before an upgrade, back up the four SQL databases and existing application configuration. Schedule downtime because selected websites, application pools, or services are stopped and restarted. The installer creates application-folder ZIP backups, but these do not replace database backups or provide automatic rollback. Backup locations are shown in the installation log.

An IIS upgrade replaces the application package folders and regenerates configuration. Record any customer-specific file or configuration changes before starting so that you can review and reapply necessary customizations afterward. Reusing an IIS site or application does not automatically move its existing physical path or change its application-pool assignment when you change folder or prefix fields.

Prepare DNS, firewall access, and a certificate covering the intended HTTPS hostname. A new main website uses the HTTPS certificate (new website) selector. Existing sites retain their bindings and certificates; configure a missing or incorrect binding in IIS before proceeding.

Guided installation walkthrough

1. Prepare and launch

Extract the complete release to a folder separate from the installation destinations. Keep Prerequisites.json, Check-InstallerPrerequisites.ps1, the launcher and all selected payloads together. Run Install-Any2Info.cmd. It uses Windows PowerShell 5.1 to check the installer runtime and requests administrator elevation for the wizard. If the runtime is missing, install the matching .NET 10 Desktop Runtime and start again. The launcher does not bypass execution policy; ask your administrator to arrange script signing if required. Direct EXE launch relies on the standard .NET host message when its runtime is absent.

The release policy accepts Windows 11 or later (Client build 22000 minimum), or Windows Server 2019 or later (Server build 17763 minimum), on x64. It requires stable .NET 10.0.0 or a later compatible stable 10.0 patch. The installer needs the .NET and Windows Desktop runtimes for its own architecture. Web/Datahub deployments additionally need x64 .NET and ASP.NET Core runtimes and any higher minimum declared by their published applications. An SDK or another major version alone does not satisfy this. Datahub drivers also need .NET Framework 4.8 or later (release value at least 528040).

For IIS hosting, install IIS before the .NET 10 Hosting Bundle, or repair the bundle afterward. Ensure WAS and W3SVC run, the x64 ASP.NET Core Module V2 is registered with its binary present, and required restarts are complete. WebSocket Protocol is recommended; missing support warns. Application Initialization is recommended for preload/always-running applications. The installer does not provision these prerequisites.

For database work, arrange four separate Any2Info databases and SQL access. Existing databases need compatibility level 130 or higher and effective CONTROL permission for migrations, for example db_owner; server sysadmin is not mandatory. Missing databases require effective creation permission and a compatible creation package. A SQL engine version alone does not establish each database’s compatibility level. Have the DBA resolve permission or compatibility failures; readiness does not change them.

2. Follow a clean installation

1. On component selection, enter the permanent Instance name, choose Install IIS packages, Update or create database, and, when needed, Install datahub with its hosting mode. Click Next.
2. The Installation prerequisites checklist opens. Select any failed/warning row and read Required, Detected and remediation. Correct machine or package problems, then Check again. Use Continue when acceptable; Back to settings returns without starting installation.
3. On application settings, confirm Version to install, select a dedicated absolute Install folder, and enter Apps service name. Click Next.
4. On database settings, enter the customer connection string, click Test connection, then Load databases. Select the matching four existing databases or enter four new names. Confirm Update scripts points to this release’s ZIP. Click Next and resolve the database readiness checklist before continuing. A new name is a request to create a database, so review spelling carefully.
5. On application pools, decide whether this instance needs a distinct prefix and inspect the pool preview. On website settings, select/create the website, enter the public root URL and matching port, and select the certificate for a new HTTPS site. Preserve any intended suffix and advanced settings. For an existing site, arrange its matching binding in IIS first. Click Next.
6. On Outlook add-in settings, enter all three Graph values if used, or leave all empty. On Datahub settings, choose its folder and the mode-specific fields described below. On Create users, add an initial application administrator and confirm Admin rights is selected.
7. Click Next to enter the summary. The full Installation readiness check runs before the summary is built. Resolve blockers and review warnings. If readiness returns you to a settings page, correct the indicated issue and proceed again.
8. Review the summary’s instance, paths, databases, IIS/service actions and backups. Click Install. A fresh complete readiness check appears before registry settings are saved or actions start. Accept its results, then monitor progress and the log. If settings changed since the summary, review the refreshed summary and click Install again.
9. After completion, perform the checks at the end of this guide. Reaching the end of the progress bar does not prove application login, public reachability or external integrations work.

3. Follow an upgrade

Back up all four databases, customer configuration and required Data Protection certificates first. Arrange downtime and record customizations. On component selection, select the existing instance and wait for Loading data… to finish. Confirm the package version and every loaded value, especially folders, database roles, website, suffix, pool prefix and Datahub service name. Select only components intended for this run; IIS deployment still requires database updating.

Follow the same Next/checklist/summary/Install sequence as the clean walkthrough. Reuse matching applications and pools. If CFG-02 reports another path, pool or binding, check the intended existing deployment before changing names to evade a collision. Existing websites retain their bindings. Restore missing original Data Protection certificates with private keys before proceeding. Add only new users; existing users do not need to be queued again. Review and reapply required customer customizations after deployment and test with an existing administrator.

4. Follow a database-only run

Select/load the instance, clear Install IIS packages and Install datahub, and select Update or create database. Next runs machine readiness, then opens databases. Test the connection, load/select all four database roles and choose the update ZIP. Next runs database readiness, followed by full configuration readiness when entering the summary. Review the summary and click Install for the final gate. No web/Datahub payload, IIS or storage checks are required when those components are unselected. The installer runtime, database package, SQL and applicable input/operational checks still apply.

If Update DB only is visible on the database page, it is an implemented shortcut that selects this component combination and opens the summary through full readiness; it does not execute database work immediately. Always finish with Install. Keep backups: database migrations are real changes and do not have an automatic rollback.

5. Follow a Datahub-only run

Select/load an existing instance when its saved parent site or integration settings are needed. Clear IIS packages, select Datahub and choose its hosting mode. Clear database updating if this run needs no migrations. After machine readiness, complete databases if selected, then the Datahub screen. Virtual application mode needs an existing parent IIS site when web applications are unselected; its settings come from the loaded instance because the main website screens are skipped. IIS website mode requires its own site, folder and port; select HTTPS, hostname and certificate when required. Legacy service mode requires a safe instance name, folder, available port and an application-service start mode. Service HTTPS blocks readiness.

Proceed through full readiness, summary and the final Install check. Datahub-only deployment does not schedule automatic registration in the main database. Arrange registration separately and verify it in Any2Info. A standalone Datahub website or service can be deployed without the web applications; a new virtual application still needs its parent site configured.

6. Prepare a test copy

First restore production backups to separate test databases. Select Prepare production database backup for testing; database updating is selected automatically. Follow the applicable walkthrough above and verify the server and all four names at both the database screen and summary. When installing IIS too, set the test Web url. In a preparation-only run the website screen is skipped, although preparation still uses its stored Web url value; have the consultant verify it before starting. Preparation does not restore a backup, duplicate production or discover all remaining integrations. Review the changes listed below before Install, and inspect the resulting test data and external connections before enabling any activity.

Choose an installation path

Installation task	Components to select	Screens that follow
New installation with Datahub	Install IIS packages, Update or create database, Install datahub	Application settings → databases → application pools → website → Outlook add-in → Datahub → users → summary → installation.
Upgrade an existing installation	Select the existing instance, then select the components being updated	The same screens as a new installation, with saved values loaded where available. Check every value before continuing.
Install or update the web applications without Datahub	Install IIS packages; clear Install datahub	Application settings → databases → application pools → website → Outlook add-in → users → summary → installation. Database updating is compulsory with the web applications.
Create or update databases only	Clear Install IIS packages and Install datahub; select Update or create database	Databases → summary → installation. Use Next → Install, or the Update DB only shortcut when available; both reach the readiness checks and summary.
Install or update Datahub only	Clear Install IIS packages; select Install datahub; clear database updating if unnecessary	Datahub → summary → installation. If database updating remains selected, the database screen appears first. See the Datahub-only restrictions below.
Prepare a restored production database for testing	Select Prepare production database backup for testing; choose other components as needed	Database updating is selected automatically. Preparation changes the selected main database after database updating. See the test preparation instructions below.

Selecting no installable component prevents continuation. Selecting IIS packages or test preparation automatically selects and locks database updating. To choose a database-only run, clear the other component selections explicitly.

Component selection and instance name

Field or option	Purpose and use
Instance name (this cannot be changed)	Select an existing local instance to load its saved settings, or enter a permanent name for a new installation. The name identifies installation settings under HKEY_LOCAL_MACHINE\Software\Any2Info\WebSuite and is used in application configuration. Preserve it during upgrades and server migration planning; entering another name does not rename an existing deployment.
Install IIS packages	Selected by default. Deploys AnyService, DataService, DataServiceWorker, Apps, AppsService, Platform, Auth, and MCP, with IIS application pools, virtual applications, and configuration. Also includes application user creation and landing-page deployment. Automatically requires database updating. Clear it for a database-only or Datahub-only run.
Install datahub	Selected by default. Deploys or updates Datahub in the selected hosting mode. Clear it when the existing Datahub should not be changed in this run.
Select an install mode for the datahub	Appears when Datahub is selected. Choose Virtual application (default), IIS website, or Windows service (legacy - app server). These modes use different settings screens; see the Datahub sections below.
Update or create database	Selected by default. Creates missing databases and applies the supplied database updates to the selected main, document, engine, and logging databases. It is locked on while IIS packages or test preparation are selected. Clear it only for a Datahub-only run that needs no database update.
Prepare production database backup for testing	Off by default. Modifies the selected main database to disable production activity and remove specific credentials and user information. Use only against a restored test copy. It does not create a backup or restore one for you.
Loading data…	Status shown while saved instance settings are being retrieved. Wait for an existing instance to finish loading before editing its settings. If loading fails, check the values manually.

If the package’s IIS Packages, Datahub, or Database folder is missing, the corresponding component is disabled. Missing database files also disable test preparation. Obtain the complete installation package for the required work.

Prepare a production backup for testing

Restore the required production databases to separate test databases before running this option. Confirm the SQL Server and all four database names point to the intended test environment. When deploying the web applications too, set Web url to the test address.

The preparation action changes the main database as follows:

• Sets existing dataflow Disabled settings from False to True and marks non-default Datahub registrations as deleted.
• Removes Datahub API key entries; clears stored connection refresh tokens, tokens, client secrets, and passwords; removes Password and Pwd entries from stored connection strings.
• Deletes connection records in CON004 and clears AUT014 records.
• Replaces non-administrator usernames, names, email addresses, and SSO usernames with test values; resets their password values and disables these accounts.
• Replaces administrator profile names, email addresses, and SSO usernames with test values while retaining their usernames and passwords. Administrators’ existing disabled state is retained.
• Clears the targeted user contact/profile fields, profile images, password-reset fields, MFA settings, and biometric requirements for both groups.
• Adds Test - to configured platform, apps, and service titles; clears the configured OpenAI API key and removes the JWT signing private key setting.
• Clears AUT030 and AUT031 records when those tables exist, and points active platform connections to Web url.

These changes affect real database records and are not reversed by clearing the checkbox later. This is targeted preparation, not a guarantee that every item of customer data or every external integration has been anonymized or disconnected. Review remaining customer content and integrations before using the copy.

For a test-preparation run without IIS packages, the website screen is skipped even though preparation still uses the wizard’s Web url value. Have a consultant verify that value before proceeding; use the full IIS installation path when the test website also needs to be configured.

Application version and installation folder

This screen appears when Install IIS packages is selected.

Field or button	Purpose and use
Version to install	Display-only version supplied by the installation package’s configuration. It does not select a version to download. Use the correct package if the displayed version is wrong.
Install folder	Root folder for the web application files. Default: C:\Program Files\Any2Info\IISPackages. Select the existing folder for an upgrade or an appropriate dedicated folder for a new instance.
… beside Install folder	Opens the folder browser. The path box itself is disabled for direct editing. The page requires an absolute path. Readiness checks inspect it without creating a folder; installation creates the required folders.
Apps service name	Name saved as the AppsService Service name setting in the main database. Use the agreed customer/environment service name. When test preparation is selected, the installer prefixes this value with Test - . This does not name a Windows service or an IIS application pool.

SQL Server and database settings

This screen appears for IIS installations and whenever database updating is selected.

Field or button	Purpose and use
Connectionstring	SQL Server connection used to discover, create, and update databases. Replace the sample server, user, and password with the customer values. Example: Server=SQLSERVER\INSTANCE;User Id=Any2InfoUser;Password=<password>;Connection Timeout=15. Supply a server connection without fixing it to an unrelated database.
Test connection	Attempts a connection using the entered string. Success enables the database fields. It does not prove that all databases are correct or that the account has every permission needed to create/update them.
Load databases	Retrieves existing databases and their detected types and versions. Lists are filtered for each database role and can also show databases of unknown type. Reload after changing the SQL Server or credentials.
Main database	Main Any2Info application database, including users, application settings, and Datahub registrations. Select an existing main database or type a new, unique name.
Document database	Database used for document storage. Select the matching existing document database or enter a new name.
Engine database	Database used by the engine components. Select the matching existing engine database or enter a new name.
Logging database	Database used for application logging. Select the matching existing logging database or enter a new name. Prefer selecting existing databases from the loaded list.
Messages below database fields	Green means a database has been accepted for that role. Orange means the installer intends to create the entered name. Red means the database is not accepted for that role; resolve this before proceeding.
Update scripts	Path to the database update archive. Default: Database\UpdatePack.zip beside the installer executable. Use the archive belonging to the installed software version.
… beside Update scripts	Selects a different update archive; the browser filters for ZIP files.
Update DB only	A database-only shortcut, hidden in the standard interface. When available, it clears IIS and Datahub, selects database updating, validates the database names and opens the summary through the full configuration readiness gate. Review the summary and click Install; it does not start migrations immediately.

Check all four database roles. A typing error in a new name can cause a new database to be created instead of updating the intended one. Resolve red messages and check each selected name. Next validates the four distinct database names and then runs database readiness checks; this still cannot identify a valid but unintended customer database for you.

For installations that generate web application configuration, use suitable SQL authentication credentials. Although the connection test can accept Windows integrated authentication, the generated web application connection strings explicitly use SQL authentication. A successful integrated-authentication test therefore does not establish that the deployed applications can connect.

IIS application pools

An application pool is the IIS process configuration used to run one or more applications.

Field or option	Purpose and use
Connected server	Display-only hostname of the Windows server running this installer.
Use prefix for application pools	Off by default. Adds the entered prefix to the web application pool names. Use it when multiple Any2Info instances share one IIS server and require separate pools.
Prefix field	Enabled by the checkbox. The prefix is joined directly to each pool name, so include any desired separator, for example TEST_ produces TEST_Any2InfoApps. Preserve an existing installation’s prefix during upgrades.
Application pools list	Preview of pool names and whether they already exist or will be created. This is a status list, not a component selector.

Use a distinct instance name, folders, database set, website/application paths, and pool names when separating production and test deployments on the same server. A pool prefix alone does not isolate the entire installation.

IIS website and advanced settings

Field or option	Purpose and use
Connected server	Display-only local Windows server name.
Web sites	Select an existing IIS website or enter a name for a new one. Existing sites are reused. A new site uses the chosen install folder as its root. Confirm that an existing site is appropriate before deploying applications into it.
Web url (this has to be a https connection)	Public base address used to build service URLs, authentication redirects, and Datahub registration URLs. Use HTTPS for the intended deployment; the current input checks and site creation also accept HTTP despite the label. Enter a root URL without credentials, application path, query or fragment. Replace the default https://platform.any2info.com with the customer’s address, for example https://any2info.example.com. Include a nonstandard public port if required by the deployment.
Portnumber	Port used when creating the main IIS website binding. Default: 443; allowed range: 1–56000. Keep it consistent with the intended public address and infrastructure. Selecting an existing site does not reconfigure its bindings.
HTTPS certificate (new website)	Select a Local Machine → Personal certificate for a new HTTPS main site. The list loads when opened and shows certificates with private keys as subject and expiry date. Use existing HTTPS binding is suitable for an existing site with a matching valid binding; it does not provide a certificate for a new site. Selecting a certificate does not replace an existing binding. Readiness verifies hostname, validity and key access.
Set or update landing page	Selected by default. Intended to copy the installation package’s root landing-page files to the selected website’s root folder, replacing matching files. Current limitation: clearing it changes the summary but does not stop the copy action. Back up any custom website root files before an IIS installation.
Virtual directorysuffix	Optional suffix appended to application paths, for example _Test produces /Platform_Test and /AppsService_Test. Normally hidden; a saved nonempty suffix makes it visible, and double-clicking the Portnumber label also reveals it. Keep it empty for a standard new installation and preserve existing values during upgrades. This affects URLs and authentication redirects.
Advanced install	Off by default. Shows or hides the advanced options below. Hiding the panel does not clear selections already made in it.
Install as on demand pools	Off by default. Configures all main web application pools for OnDemand start instead of the normal mixture of AlwaysRunning and OnDemand. New OnDemand pools use a 20-minute idle timeout. Use only when the agreed hosting setup permits applications to start on requests and idle out; leave off for a standard installation. This does not change the separately configured Datahub pool.
Enable data protection encryption	Off and disabled for a new installation in this version. When an existing instance has it enabled, that saved state can be loaded. Configures certificate-backed Data Protection for DataService, DataServiceWorker, AppsService, and Auth. It is separate from website HTTPS and does not mean the entire database is encrypted. Preserve an existing enabled setup and its certificates.
Overwrite clientIds	Hidden and selected by default. Its label/summary indicates replacing application authentication registrations, but the current execution code retains existing registrations and attempts to create missing system registrations. Do not rely on this setting to rotate client IDs or secrets. It is unrelated to the Microsoft Graph ClientId field.

For a new main website, the installer creates a binding using Web url’s protocol and hostname and Portnumber. HTTPS assigns the selected machine certificate with SNI. For an existing site, readiness requires a matching binding and checks that binding’s certificate; the installer retains the binding. The selector does not repair or rotate an existing site’s certificate.

If Data Protection is enabled for an existing instance, retain the active and previous certificates with their private keys. Follow the Data Protection certificate backup and restore procedure before moving or rebuilding the server.

Outlook add-in settings

This screen appears in the IIS installation path. Values are written into the Outlook add-in configuration under AppsService.

Field	Purpose and use
ClientId	Application/client ID of the Microsoft Graph application registration used for the Outlook add-in.
ClientSecret	Secret value for that application registration. Enter the actual secret value, rather than a secret identifier. Treat it as a credential.
TenantId	Microsoft Entra tenant ID containing the application registration.

Use values supplied for the customer’s Outlook integration. If the integration is not used, leave these settings empty. The wizard permits empty values and does not validate the credentials or configure the external application registration, permissions, or consent. On upgrades, preserve the existing integration settings unless they are intentionally being changed.

Datahub virtual application mode

Virtual application (default) hosts Datahub as an application under the main Any2Info IIS website. It has a separate application pool and normally shares the main website’s HTTPS binding and certificate.

Field or button	Purpose and use
Install folder	Datahub files location. Default: C:\Program Files\Any2Info\Datahub. Select the existing location for an upgrade or a dedicated location for the instance.
…	Opens the Datahub installation-folder browser.

The application path is /Datahub, with any configured virtual directory suffix appended. For example, a main URL of https://any2info.example.com gives https://any2info.example.com/Datahub when no suffix is used.

This screen has no separate website, port, DNS, or certificate fields: it uses the main website settings. A Datahub-only run skips those main website screens, so use an existing instance with the correct saved website settings. A fresh standalone Datahub virtual application cannot be fully configured through the Datahub-only screens.

Datahub IIS website mode

IIS website hosts Datahub in a separate IIS website, with its own port and optional HTTPS settings.

Field or option	Purpose and use
Connected server	Display-only local server name.
Web sites	Select an existing Datahub website or enter a name for a new one. Existing website bindings are retained.
Portnumber	Datahub listener/site port. Default: 48800; range: 1–56000. Choose an available port appropriate for the network setup.
Install folder and …	Datahub files location and folder browser. Default: C:\Program Files\Any2Info\Datahub.
Install as https	Off by default. Switches the configured Datahub address to HTTPS and reveals DNS name and Certificate. Clear means HTTP. This affects the separate Datahub endpoint, not the main website.
DNS name	Hostname used for the HTTPS Datahub address. Default: localhost. Use the intended hostname and matching certificate for the deployment.
Certificate	Select the Datahub HTTPS certificate. The list is populated from Local Machine → Personal certificates that have a private key and a nonempty friendly name. For HTTPS, ensure the intended certificate is available and selected.

New Datahub sites use the corrected IIS binding format *:port:hostname; HTTPS assigns the selected certificate. HTTP ignores the hidden DNS field and uses an empty hostname. Existing sites retain their bindings, and readiness requires one matching the selected settings. For HTTP it must accept localhost on the chosen port because registration uses http://localhost:port. Correct an existing binding in IIS before retrying. Verify the exact endpoint after deployment.

Datahub legacy Windows service mode

Windows service (legacy - app server) runs Datahub outside IIS as a Windows service. Use it for a deployment that specifically requires the legacy app-server setup.

Field or option	Purpose and use
Datahub instance name (leave empty for default instance)	Identifies the service instance. Empty uses the internal service name Any2infoDataManagementService. A nonempty value is used to form Any2infoDataManagementService_<name> with spaces removed from the suffix. Preserve the existing value during updates.
Windows service start mode	Controls Windows startup behavior when the service is created. Defaults to auto if no mode is selected. See the choices below. Existing services are not guaranteed to have their startup type changed by rerunning the installer.
Portnumber	Listener port, default 48800; range 1–56000.
Install folder and …	Datahub executable/configuration location and folder browser.
Install as https, DNS name, Certificate	The shared screen displays these controls, but service-mode HTTPS produces a blocking TLS-01 result. This installer cannot establish a usable service HTTPS listener; selecting an IIS certificate does not configure one. Use IIS hosting for installer-managed HTTPS, or arrange an independently configured service deployment with the consultant.

Start mode	Meaning and selection advice
auto	Automatic startup with Windows. Standard choice for this service mode.
delayed-auto	Automatic startup after the initial startup phase. Use when an intentional delay is needed.
demand	Manual/on-demand startup. Use when automatic startup is not wanted.
disabled	Prevents normal service startup. Unsuitable when Datahub must run after installation.
boot	Driver-oriented Windows startup setting; rejected by SVC-01 for this application service.
system	Driver-oriented Windows startup setting; rejected by SVC-01 for this application service.

The installer attempts to start selected Datahub services during installation. Verify both the actual service name and startup type in Windows Services, especially when reusing a legacy installation.

Datahub registration and Datahub-only runs

Automatic registration links Datahub to the selected main Any2Info database using its project information and API credentials. The installer schedules registration only when both Install IIS packages and Install datahub are selected. Existing matching registrations may be reused.

A Datahub-only run deploys Datahub without automatically registering it. Arrange registration separately when needed and verify the connection in Any2Info. The hidden Register datahub button has no implemented action; it is not a manual registration method.

Create users

This screen appears when IIS packages are selected. It queues new Any2Info application users for creation in the main database. These are not Windows accounts, SQL accounts, or IIS service identities.

For a clean installation, add at least one administrator. The wizard displays a reminder but does not enforce it. For an upgrade, add only genuinely new accounts; existing users do not need to be recreated.

Field or button	Purpose and use
Create users list	Shows queued Username, Firstname, Infix, Lastname, Email, and Admin rights values. It is not a list of all users already in the database.
Add	Opens the Edit user dialog to queue an account.
Remove	Removes the single selected account from the queue. It does not delete an existing database user. To correct a queued account, remove it and add it again.

Edit user dialog

Field or button	Purpose and use
Username	Any2Info sign-in name. Use a unique name for the intended account.
Firstname	User’s first name.
Infix	Optional surname prefix, for example van or de.
Lastname	User’s surname.
Email	User’s email address.
Password	Initial application password, masked on screen.
Retype password	Enter the password again. Save rejects nonmatching passwords.
Admin rights	Grants Any2Info application administrator rights to the new account. Explicitly check the setting; use it for the initial administrator and leave it clear for ordinary users.
Save	Adds the entered account to the installation’s queue. Database creation happens during installation. Closing the dialog without saving does not queue the account.

The dialog checks that the two passwords match. The users page requires nonblank usernames, and readiness blocks blank or duplicate queued usernames (case-insensitive). It does not prove uniqueness against existing database users or enforce all account and password-quality requirements. Check the account details yourself. A user creation failure can be logged without stopping the entire installer, so verify that the administrator account was actually created.

Summary and installation controls

Control	Purpose and use
Previous	Returns to the preceding settings page for the selected components. Datahub-only runs return from Datahub to databases when database updating is selected, otherwise to component selection. From the summary, Previous returns to the Datahub page for the selected hosting mode. Review the final summary again after changing settings.
Next	Moves along the selected component path. Pages check absolute folders, database names, pool prefix, website name/URL and queued usernames. The staged readiness gates perform additional checks; Next alone is not a deployment guarantee.
Cancel	Asks whether to close the installer. Before installation, this abandons the run. During installation it is not a rollback operation; closing can leave partially applied changes.
Install summary	Lists the planned actions, such as backups, database work, application pools, copying/configuration, users, and registration. Review the selected instance, paths, website, databases, and actions before starting. The landing-page and client-ID limitations described above also apply here.
Install	Replaces Next on the summary screen. Runs all applicable readiness checks again. After acceptance, and only if the summary still matches the settings, saves settings to the local registry and starts the actions. Changed settings require a refreshed summary and another review.
Current installation step	Describes the action currently running.
Progress bar	Progress through installation actions; individual actions can take different amounts of time.
Elapsed	Time since the installation started.
Installation log	Detailed action results, backup paths, and errors. Review the log even if the installer reaches completion.
Close	Available after completion or an error. Closes the installer; it does not undo installed changes.

The installer orders actions across the selected components. These include folder backups, stopping affected hosting components, database creation/updates, optional test preparation, application pool/site/service setup, file copying, configuration, user creation, restarting hosting components, and eligible Datahub registration. There is no automatic transaction covering the entire installation and no automatic rollback of completed actions.

Readiness check reference

When the checklist appears

Point in the wizard	Checks included	What happens next
Next after component selection (Machine stage)	Windows/elevation, runtime and selected application packages; IIS prerequisites when needed.	Continue opens the first applicable settings page. Database package/SQL and deployment settings are checked later.
Next after databases	Database-only check at Configuration stage: names, ZIP, connection, permissions, role/schema and compatibility.	Continue opens pools, Datahub or the summary according to selection.
Entering Install summary (Configuration stage)	All applicable checks, including machine, selected packages, SQL, inputs, storage, IIS/certificates, service and operational advice.	An accepted report permits preparation of the action summary. Returning to settings does not install anything.
Install on summary (BeforeInstall stage)	All applicable checks run again against current settings and state.	Acceptance permits saving settings and starting actions only when the summary still matches.

Checks inspect state without installing roles, repairing runtimes, starting services, changing ACLs, creating test databases/files/folders, executing migrations/plugins or rotating certificates. The wizard uses background checks with a two-minute overall deadline; normally each checker has 30 seconds and database checking has up to 90 seconds within that deadline. A required check that fails or times out blocks; an advisory checker failure warns. Some later rows may be absent when an earlier failure prevents meaningful checking. IIS configuration checks are skipped after a blocking IIS role/service/module result. Fix the first dependency and check again.

Status or control	Meaning and action
Passed	The inspected facts meet this check now. It does not certify the entire deployment.
Blocked	A required fact failed or could not be verified. Normal Continue is disabled; read the row’s details and correct the issue.
Warning	Guidance or uncertainty that permits continuation. Review it and complete any necessary preparation.
NotApplicable	The stated requirement does not apply to this selection/state, such as creation permission when all databases already exist. Many unselected checks are simply omitted.
Row selection	Shows check ID, summary, Required, Detected, remediation and any help URL in the detail pane. Several rows can share an ID for different applications, databases or facts.
Check again	Reruns this dialog’s checks with its captured settings. Use after correcting the machine/package/database state. To change wizard inputs, return to settings first.
Back to settings	Closes the checklist without accepting it. Correct the relevant page and proceed again.
Copy report	Copies the available detailed report for consultation/support. Reports avoid raw exception messages and configuration credentials; they can still contain paths, hostnames, database names and certificate thumbprints. Share appropriately.
Continue	Accepts the current report when no blockers remain. Warnings remain visible. It does not begin installation from an earlier gate.
Override failed checks…	Appears after a run with blockers. Opens a confirmation listing every failed ID and summary and warns of an incomplete/unusable installation. Use only after independently verifying the requirements. Yes accepts the report and returns to the wizard immediately.

An override accepts all blockers in that exact report, rather than an individual row. Their status remains Blocked and a GATE-02 Warning records the overridden IDs and summaries. Checking again discards that acceptance. Changing settings invalidates it; the final pre-install check requires a fresh acceptance/override even if an earlier gate was overridden. Accepting an override closes the dialog immediately. The final accepted pre-install report, including any final override, is written to the installation log; installation errors remain effective. Repeated Install clicks and changes during checking cannot authorize actions using stale results. An override does not fix a prerequisite, bypass page validation or guarantee summary/action execution can succeed.

Machine, runtime and application package checks

Check	Scope and possible result	What to do
ENV-01	Every gate: Passed for Windows Client build 22000+ (Windows 11 or later), or Server at the configured minimum build, with x64 architecture. Blocked for older or unknown installation types/builds or other architectures. A prerequisite-policy or runtime-inspection failure may also appear under this checker ID.	Use Windows 11+ or Windows Server 2019+, x64; retain a valid release Prerequisites.json. If inspection fails, verify permissions and complete package, then retry.
ENV-02	Every gate: Passed when running as Windows administrator; otherwise Blocked.	Relaunch elevated.
NET-01	Every gate: separate Passed/Blocked rows for .NET and Windows Desktop runtime matching the installer process architecture. Stable compatible 10.0 patches satisfy the configured minimum.	Install the matching Desktop Runtime; another major version, prerelease or SDK alone is insufficient.
NET-02	Web/Datahub selected: Passed/Blocked for x64 .NET and ASP.NET Core plus each published payload’s declared framework, architecture and minimum. Unsupported architecture/roll-forward requirements can prevent verification.	Install matching stable runtimes/Hosting Bundle, or obtain supported complete published output. A higher shipped minimum takes precedence.
NET-03	Datahub selected: Passed/Blocked for .NET Framework release value against the configured 4.8 minimum.	Install .NET Framework 4.8+ and complete required restart; this is separate from modern .NET.
PKG-01	Selected web/Datahub packages only, every gate: Passed when required published files exist and required JSON/XML parses; otherwise Blocked. Includes appsettings, runtime/dependency manifests and matching DLLs, applicable web.config, Datahub executable and Extensions/ExtensionHost folders.	Obtain/re-extract the complete correct release. Do not mix versions or remove configuration/manifests. Unselected payloads do not block an independent run.

IIS prerequisite checks

These apply when installing web applications or Datahub in either IIS mode, including machine readiness. A service-only/database-only selection does not require IIS.

Check	Possible result	What to do
IIS-01	Passed for enabled Web Server role and accessible IIS configuration; Blocked for missing role or failed configuration detection.	Install/repair IIS and check administrator/configuration access. Install IIS before the Hosting Bundle.
IIS-02	Passed/Blocked separately for WAS and W3SVC being present, enabled and running.	Enable/start these services manually or repair IIS; complete restarts and check again.
IIS-03	Passed for registered ASP.NET Core Module V2 with readable x64 native binary; otherwise Blocked.	Install/repair the .NET 10 Hosting Bundle after IIS and perform its required IIS restart.
IIS-04	Passed for enabled WebSocket module/effective setting; Warning when absent, disabled or unverified. Existing selected sites/apps are inspected where applicable.	Enable WebSocket Protocol and effective IIS WebSocket support. Continuing with the warning may leave WebSocket features unavailable.
IIS-05	With on-demand mode off: Passed if Application Initialization module exists; Warning otherwise. Omitted when on-demand is selected.	Enable Application Initialization for preload/always-running applications.

SQL and database package checks

These run after database settings and in full readiness/final checks when database updating is selected.

Check	Scope and possible result	What to do
SQL-01	Blocked for absent/invalid/duplicate role selections or duplicate database names; Passed for an established SQL connection. Names must be distinct, non-system names, at most 128 characters, using SQL Server delimited identifiers (including spaces and punctuation such as ampersands); control characters are rejected. Connection/inspection failures or timeouts can appear as Blocked under this ID.	Correct all four roles, connection string and SQL access. Check that valid names identify the intended environment. A successful connection test alone does not replace these checks.
SQL-02	Passed for verified existing migration permissions and needed creation permission. Blocked for unprovable absence/visibility, offline/read-only/inaccessible databases, missing effective CONTROL, incorrect Any2Info role/version identity, or missing creation rights. Creation permission is NotApplicable when no database is missing.	Ask the DBA to verify visibility/access and correct role/schema, grant effective database CONTROL for migrations, and creation rights only where needed; or pre-create using supplied scripts. A database hidden from this login is not assumed missing.
SQL-03	Existing databases: Passed for compatibility at least 130, Blocked below minimum/unreadable. Missing databases: Passed when SQL engine and creation/model plan establish the required level; otherwise Blocked.	Have the DBA review engine support (SQL major version 13+ for creation), each database’s compatibility, model inheritance and creation script. No automatic compatibility increase is performed. Creation checks compatibility again during execution.
PKG-02	Passed for readable database ZIP/layout; Warning when an existing-format pack lacks optional metadata so the exact upgrade path is unverified. Blocked for missing/unreadable ZIP, empty/unrecognized content, invalid/duplicate SQL version filenames, unreadable entries/invalid managed plugins, inconsistent optional metadata, missing creation/timezone resources, or declared downgrade/incomplete upgrade chain.	Use the complete release ZIP and matching creation scripts/resources. Read the detailed failing path/entry. Existing update packs do not require repackaging merely to add metadata; resolve concrete errors and review any uncertainty with the release consultant.

The update ZIP uses root folders Main/, Document/, Engine/, Logging/, Reporting/ and Plugins/ with matching casing. Updates may cover a subset of roles or contain only plugins. Adjacent extracted folders do not replace the selected ZIP. SQL filenames use major.minor or major.minor.revision versions. The exact historical Main/1.0049 (last non config panel script).sql (two spaces before the parenthesis) is exempt from version inventory checks, but must be nonempty/readable; this does not alter updater execution.

Optional root preflight.json, when supplied by the release builder, must consistently declare all four roles, release targets, creation baselines and plugin artifacts. It enables additional chain/downgrade checks. Checks inspect SQL contents and managed-assembly metadata without executing plugin code or certifying plugin behavior. Without these declarations the established update pack remains usable with a warning. Release builders can find the details in the installer prerequisites documentation.

Deployment settings, storage, certificates and services

These apply at full configuration and final readiness, with scope as described below.

Check	Scope and possible result	What to do
CFG-01	All selections require a valid instance name. IIS deployments also validate pool prefix/suffix, selected site names, root HTTP(S) URL, hostname and matching URL/port. Invalid values Block; validated IIS settings can Pass. Website failure details identify component, field, site, host and port.	Names allow letters/digits/spaces/dots/underscores/hyphens, at most 128 characters. Remove suffix path separators and ? # :. Enter root URLs without credentials/path/query/fragment and include a nondefault port. Datahub HTTPS DNS name is hostname/IP only; HTTP ignores this hidden field.
CFG-02	IIS: Blocked for binding collisions, missing matching existing binding, incompatible existing application folders/pools, pool reuse by a new instance, 32-bit existing pool, different Datahub site root, or absent parent site for Datahub-only virtual mode. Service: Blocked for occupied TCP port when creating a new service. No separate pass row is required.	Restore the intended existing settings or resolve collision with administrator. Use distinct site/host/port, folders and pool prefix for a new instance. Existing sites are not rebound automatically. Datahub HTTP bindings must accept localhost; pools created here use native 64-bit execution.
CFG-03	Web selected: Blocked for malformed Graph client/tenant GUIDs or blank/duplicate queued usernames; Warning for incomplete optional Graph credentials. A required input check failure blocks, while failure of the separate operational advisory checker warns. Some duplicate findings may appear.	Enter valid GUIDs and all three Graph values, or leave all empty. Correct queued usernames (duplicates are case-insensitive). No external credential/consent or existing-user uniqueness check is performed.
FS-01	Web/Datahub: Passed for inspected access; Blocked for relative/unsafe root paths, overlapping release/targets, overlapping web/Datahub folders, unavailable parents, known denied write/delete access, unsafe backup overlap or failed safe inspection. Warning where effective ACL rights cannot be fully verified. Links in existing ancestors are resolved; reparse points inside trees prevent safe size inspection.	Choose dedicated absolute nonoverlapping destinations outside package/temp/backup locations. Make storage available and have administrator verify ACL/share write/delete rights. No probe files are created.
FS-02	Web/Datahub: Passed/Blocked for estimated required space on each local volume; Warning for unverified network-share capacity.	Allow payload space at destination plus an uncompressed temporary backup and final backup allowance for existing target contents, including existing backup files. Free space or ask share administrator to confirm capacity. Estimates are not a storage reservation or complete remote permission test.
TLS-01	IIS HTTPS: Passed for a currently valid matching LocalMachine/Personal certificate with accessible RSA/ECDSA private key and permitted server-authentication use. Blocked for missing/expired/not-yet-valid certificate, wrong hostname, absent/inaccessible key, unsuitable usage or unsupported existing binding store. Also Blocked for Datahub service HTTPS.	Select a suitable certificate for a new site; fix an existing site’s binding in IIS. SAN DNS/IP and one-level wildcard matching are inspected; DNS name fallback applies without SAN. Use IIS hosting or an independently verified service TLS deployment for service HTTPS. Local validation does not establish public trust/revocation or application identity key access.
CERT-01	Web with Data Protection enabled: Passed when every recorded active/previous RSA certificate/private key is accessible, or no prior certificates are recorded for a new setup; Blocked for missing/inaccessible original keys.	Restore original certificates and private keys. Preserve previous keys for decrypting existing data; an unrelated replacement is insufficient. This check differs from website TLS.
SVC-01	Datahub Windows service: Passed when settings validate; Blocked for unsafe name, invalid start mode/port, or an existing service pointing to another executable/unsafe unquoted path. Warning for disabled startup.	Preserve the intended normalized service name and executable location; use auto, delayed-auto or demand when it must run. boot/system are rejected. For a new service, resolve occupied port (CFG-02). The same normalized name is used to register, stop and start the service.

Operational and gate checks

Check	Scope and possible result	What to do
OPS-01	After machine stage: Warning for pending reboot; web/Datahub external DNS/firewall/TLS-trust verification; unresolved main hostname on this server; or an advisory-check timeout/failure. Absence of a warning does not prove remote reachability.	Complete restart as arranged, prepare DNS and test exact URLs from a client after deployment. Check firewalls and certificate trust separately.
OPS-02	Warning for selected hosting downtime/configuration replacement, selected database migrations without SQL backups/rollback, and a new web instance with no queued administrator.	Arrange maintenance window; preserve configuration and database backups; queue an administrator or verify an existing one with DBA. These are guidance, not proof preparations have happened.
GATE-01	Blocked when no web, database or Datahub component is selected.	Select at least one installable component and a Datahub mode when applicable.
GATE-02	Warning added only after an explicit accepted override. Lists all overridden blocked IDs/summaries; original blockers remain in the report.	Retain the report/log and independently verify each requirement. Acceptance is limited to that exact run; it does not suppress installation failures.

Checks after installation

1. Review the installation log for failures, including user creation, service startup, and Datahub registration messages.
2. Verify the main and Datahub website bindings, certificates, DNS, and intended ports. Open the public HTTPS address from a client machine.
3. Sign in to the Platform with the intended administrator and confirm the applications connect to the correct databases.
4. Confirm the required IIS application pools or Datahub Windows service are running. Check Datahub connectivity and registration in Any2Info.
5. Test the Outlook add-in if configured.
6. For a test environment, confirm production flows remain disabled, test URLs are correct, and required test credentials and users have been configured before enabling activity.
7. Retain database backups, folder backups, and any required Data Protection certificates and private keys.