@rirish in my experience your proposed sizing should be ok, however a few questions and thoughts:
-How many cores on that single CPU?
-Are you planning that your App Server and DB Server are the same server?
-Be sure to have a separate virtual server for your Test, Pilot & Train DB.
-SQL will attempt to use all the memory and resources it can, be sure to configure your SQL Instance to not use more than 75% of your Memory, this will provide overhead for the AppServers and RD sessions or any other services.
-In SQL you can also specify which Cores SQL will use. Your SQL Server License wil specify how many cores you should be assigning. I usually do not allow SQL to use all Cores, this provides CPU overhead and I get a metric on SQL. SQL trypically isn’t CPU heavy
-You didn’t mention storage but I would make sure you provide lots of storage, here is how I usually organize my storage:
- System\OS Drive (just the OS) - whatever you usually need for the OS (80 GB?)
*Programs Drive - where I try to install programs including Epicor & IIS website store (80 GB?)
*Data - where all DB’s are stored (Epicor, Reports, SSRS, EnterpriseSearch, DataDiscovery, Transaction Logs, etc) (1 TB - this might be a little overkill but storage is cheap and if something crazy happens you have lots of margin. Min 500GB)
*Backup - where all DB backups are stored (including DB & transaction log backups) (500GB - Dependent on your companies retention policies)
-If I were you, and that CPU has at least 4 cores I would try your setup and see how things go. With how few users you have you should be ok. I have several clients with 20 users and 10 MES users and here is their config:
- 8 Core Single CPU
- 64GB Memory