How do I confirm that a server is suitable for my software and licences?
Hardware compatibility, software support and licence permission are separate checks. A program starting successfully does not prove that its vendor supports the environment or that your licence permits the deployment. Confirm all three before moving a production workload.
Before you start
- An inventory of commercial and open-source components and the proposed deployment model.
Instructions
1. Check the supported configuration
Record exact versions, operating systems, CPU architecture, virtualisation requirements, database editions and required extensions. Include agents and integrations that are easy to overlook. Ask the software vendor about dedicated hardware, shared infrastructure or hosted-service restrictions where relevant.
2. Review licence scope
Identify whether rights depend on cores, sockets, instances, users, devices or another measure. Check hosting rights, remote-access usage, standby instances and transfer between servers. Microsoft’s published licensing guides illustrate why server software and access rights may require separate evaluation; the applicable agreement determines your entitlement.
3. Confirm service suitability
Provide Britixo with the workload description, anticipated network use and specialist requirements. Ask about any relevant service restrictions and supported configuration options. Keep written confirmation of unresolved compatibility or licence questions with the project record before ordering or enabling the workload.
Check the result
- Each critical component is supported on the chosen platform and has the required entitlement.
- The proposed use fits the confirmed service scope.
Troubleshooting
- A licence worked on the old server but fails after migration
- Check hardware binding, activation limits, permitted reassignment and the new resource count with the vendor. Do not bypass activation or assume an old entitlement transfers automatically.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.