When the trial ends, the paid subscription starts and the first term is charged, unless cancelled before. Free Trial: payment method required if signing up for a free trial (credit/debit card or PayPal only).Set-up: to get the protection/service started, you must download and install on each device and/or complete set-up.Contract Type: contract for a monthly or annual subscription, starting when the transaction is complete.Your comments are suggestions are appreciated to achive the mentioned requiremenets in the most efficent and smooth way. I came across the below KB article that talks about the above scenerio, I belive it is also applicable with the latest version of SEP.
I want to know that what would be the intial size of the replication ( I would not want to replicate live update, client packages and logs) as we set up the SEPM in DR site? Would it be 20 GB since the size of sem5 database on the main site is 20GB? Since the SEPM on DR site is going to be in another city so the cummunucation over the WAN link. Your suggestions and comments are appreciated.ġ) The current size of SEPM sem5 database on SQL database is about 20GB in size in the maine site. I have few queries or clarifications in this reguard. We have a requirement to set up another SEPM in our DR site to achieve full site redundency. Hello everyone, curently we have two SEPMs running 14 MP1 with a shared SQL database and configured as HA servers with a single site desigin supporting about 3500 agents. Is there a possibility, a policy or whatever to instruct the lua – update pattern after successful connection to the WAN and begin immediately with checking and downloading the newest pattern? This period is too long, my clients are mainly 10 or 20 minutes online before the close the notebook and drive to the next customer. Now I did a test with an client, and the result was: after connecting to the WAN – it took about 50 minutes!!! only with the rules “use a l live update server” and to use the “default Symantec Server” with enabled scheduling, with setting “continuously”. I split our LiveUpdate policy, one for the internal gups and created a new liveupdate policy for the external clients. these 600 clients are mainly external staff and they are normally not often connected to the internal lan to get gup updates.ĭefinitions older 10 days is definitive to old! We have enabled location awareness, our internal clients are using gup and that works fine and fast.īut i always receive a notification about 600 clients with virus definitions older than 10 Days. I have the admin rights for our site (or sub group?!). so I’ve maybe not the full overview about our sepm landscape.
I’m a site admin for SEPM solution, our site is about 2600 clients small, the sepm server is managed by an external company.
0 kommentar(er)
