That's what the document is saying.

But you should also take into consideration the bandwidth from the server to the clients. How they will get their updates and any policies to be enforced that will limit your number of clients. And the maximum database size.

The database size is what could be limiting the deployment of SEP to a set number of clients

Hi,

Your question "can we not add more SEPM server instead of doing a new site"

In Symantec terminology a site is a database.

So you can definately have one site (one database) and add multiple SEPM's (only for SQL).

But again as rightly said by mon_raralio you will have to consider the bandwidth utilization as well.Because there has to be communication between SEPM and clients ,hence you will have to check with bandwidth requirement. Below is a small example of length of time needed to perform a content distribution update in a best case scenario:

Concurrent Connections x Content Size* ÷ Available Bandwidth = Content Distribution Time

Example: -

 *** Note that The time is under best case scenario.
• Latency can also be affected by network utilization and protocol overhead.****

T1 (1.54Mbps)
5,000    30 mins
15,000   2 hours

10 Mbps
5,000   4 mins
15,000  14 Minutes

100 Mbps

5,000  30 secs
15,000 2 Minutes

1 Gbps
5,000  3 secs
15,000 9 Seconds

...Barkha

Hi,

All clients will get there contents from internal LU servers, so I don't think there will be any problem with the network (we also have at least 10 Mbps to the clients)

//Seorm