Hardware configuration when EMS and SQL Server run on different machines with no FortiGate connected

The following table shows the configurations when EMS and SQL Server are running on different Windows Server machines with no FortiGate connected and multitenancy disabled:

Number of managed endpoints	EMS server machine		SQL server machine		Suggested keep alive interval	Deployment duration
	Number of virtual CPUs	Memory (RAM) (in GB)	Number of virtual CPUs	Memory (RAM) (in GB)
10 000 to 20 000	8	6	4	16	120 seconds	1 to 2 days
20 000 to 50 000	16	8	6	22		3 to 4 days
50 000 to 75 000	20	10	10	26		4 to 5 days
75 000 to 150 000	26	14	16	44	180 seconds	6 to 8 days
150 000 to 250 000	32	20	26	56	240 seconds	10 to 14 days

The following table shows the configurations when EMS and SQL Server are running on different Windows Server machines with no FortiGate connected and multitenancy enabled with up to 20 sites:

Number of managed endpoints	EMS server machine		SQL server machine		Suggested keep alive interval
	Number of virtual CPUs	Memory (RAM) (in GB)	Number of virtual CPUs	Memory (RAM) (in GB)
10 000 to 20 000	8	8	4	22	120 seconds
20 000 to 50 000	16	10	8	28
50 000 to 75 000	20	12	12	32
75 000 to 150 000	26	16	18	54	180 seconds
150 000 to 250 000	32	22	28	66	240 seconds

The following table shows the configurations when EMS and SQL Server are running on different Windows Server machines with no FortiGate connected and multitenancy enabled with up to 500 sites:

Number of sites	Number of managed endpoints	EMS server machine		SQL server machine		Suggested keep alive interval
		Number of virtual CPUs	Memory (RAM) (in GB)	Number of virtual CPUs	Memory (RAM) (in GB)
200	Up to 100000	34	22	30	100	180 seconds
	100000 to 200000	38	24	36	120	240 seconds
300	Up to 100 000	40	24	38	130	180 seconds
	100 000 to 200 000	44	26	42	160	240 seconds
500	Up to 100 000	46	26	44	200	180 seconds
	100 000 to 200 000	52	30	46	230	240 seconds