The situation described is a common one in multi-localization on-premises BC environments, and the good news is that running multiple localizations on a single server is entirely feasible — the installer limitation encountered is a GUI constraint, not a platform restriction.
Multiple BC Service Instances on One Server
The BC installer is designed to manage a single installation per server, but the platform itself fully supports multiple service tier instances on the same machine. These are created and managed through the BC Administration Shell using PowerShell, bypassing the installer GUI entirely:
Each instance requires a unique set of four ports (management, client services, SOAP, OData), its own Windows service, and its own localized database. Firewall rules need to be updated accordingly.
SQL Collation Considerations
Latin-based localizations (W1, AT, DE, CZ, etc.) can all share a single SQL instance without issues. However, Cyrillic-based localizations (RU, BG, SR) require a different collation and should be placed on a separate named SQL instance on the same SQL VM:
| SQL Instance |
Collation |
BC Localizations |
| SQLVM\LATIN |
Latin1_General_CI_AS |
W1, AT, DE, CZ, FR, ES, ... |
| SQLVM\CYRILLIC |
Cyrillic_General_CI_AS |
RU, BG, SR, ... |
The overall architecture that emerges is clean: one BC VM running multiple service instances, and one SQL VM running two named SQL instances grouped by collation family. This scales well as new country localizations are added, without requiring any additional infrastructure.
PLEASE Mart it as verified if you have find useful
