Setting Up ePo 3.5

[drew1701d]

Hi,
Just trying to get a general idea of what other organizations are doing when it comes to setting up ePo 3.x. According to the documentation for sizing a server for your environment they recommend the SQL server installation be located on a separate server from the actual ePolicy Orchestrator install, is this really necessary? Or is this just cost savings to take advantage of only one SQL server licenses as opposed to multiple. Microsoft recently stated the norm for their products (i.e. SMS & MOM) to be installed on the same server where SQL will reside.
At my previous job we did just fine with our ePo 2.5 server running everything from one system.
If two servers are required, should the SQL server match the ePolicy server in terms of hardware specs?
Thanks In Advance
Andrew

 

[jfp23]

I've been running with both SQL and EPO on the same server without a problem

 

[terry712]

mines is on same box - no probs

 

[JimmyZ1]

i'm on seperate boxes no problems

 

[Windexx]

I'm on separate boxes with 40k clients. If done again, I would separate the two if I had the budget but it does work well. An advantage of separation is to separate the load of the SQL and master from each other and if one goes down it won't affect the other...easier to recover.

"There is no patch for stupidity

 

[vectorgod]

How many machines will you be managing?

 

[drew1701d]

will be managing 6k clients, in simulations we've seen significant network traffic increase for servers dependant on SQL instances on boxes other than their own. I think we'll load everything on one box and add a secondary epo server if things become too hectic for one to handle, though acccording to McAfee it shouldn't.