), which includes sizing guidelines for the mentioned compoment. Are those guidelines considered adequate for any TEM package combination? In other words, in case I plan to implement several TEM packages (e.g., Lifecycle Management + SUA + Core Protection), and assuming that all managed desktops/servers will benefit from every TEM package, are the sizing guidelines any different from the ones included in the posted link? Or are they the same?
Some of the packages require their own server. For example, I don’t think SUA and SCM can be run together on the same host server. I don’t know if they can coexist with Web Reports either.
You don’t mention how many computers you will be supporting. The more endpoints you will be managing, the more disk space you need, and the more RAM you will want to give SQL. The TEM components are 32bit so they won’t use more than ~3.5G RAM no matter what, and will be happy with it. Stick with 64bit OS on the server, and 64bit SQL so it can use all the RAM you want to give it.
If you are going to be supporting a large volume of endpoints, you will want to be very careful with the design of your drive sub-system. This is where you can get into trouble. Don’t short yourself here. Use a good hardware RAID system. Review
for additional information. If you don’t do the drive system well, it won’t matter how much RAM or how many Cores you install. The system can easily become disk I/O bound. Lots of small writes and reads when computers check-in.
I’m actually more concerned about how will the sizing guidelines change if I have more than one TEM package, rather than if I increase the number of endpoints. I suppose that each additional package will imply more database space used, more drive I/O tasks and more RAM usage in the TEM Server; but I want to confirm if there’s something more “down-to-earth” than this…