Video Screencast Help
Security Community Blog
Showing posts tagged with Upgrade
Showing posts in English
SebastianZ | 14 Apr 2014 | 0 comments
  • Symantec Product Security has posted SYM14-005 Symantec LiveUpdate Administrator Unauthenticated/Unauthorized Account Access Modification and SQL injections advisory. This is a high severity advisory which affects LiveUpdate Administrator 2.3.2.99 and earlier. As part of normal best practices, Symantec strongly recommends keeping all operating systems and applications updated with the latest vendor patches.

Affected Products

...

Product

Version

Build

Solution(s)

Symantec LiveUpdate Administrator

2.x

2.3.2 and prior

Upgrade to LUA 2.3.2.110

Muad'Dib | 03 Apr 2014 | 0 comments

I ran into an issue changing the Installed Feature set on clients and i wanted to share my solution.

I was following the below tech Article on how to add or remove features:

http://www.symantec.com/docs/TECH90936

What was happening is that when the client received the new Install Package with the updated feature set, the client would never update its installed features.

For example, if i had a client group which was installed without the Firewall feature, but then i wanted to add the Firewall feature it would not install.

After tons of searching around i found the following VERY helpful post:

https://www-secure.symantec.com/connect/forums/remove-sep-components-update-content

My situation was very similar. If the client was upgrading versions (for example from 12.1 RU3 to 12.1...

ukDavidC | 18 Jun 2010 | 2 comments

When upgrading our SEE management servers from 7.0.4 and 7.0.5 I noticed the entire 'Symantec' registry key and subkeys was deleted. This is OK if you're just running SEEms on the server but will break anything else such as SEPM and you'll only notice when you reboot and it doesnt start.

As a precaution, backup the key! Of course standard procedures suggest this would be done on test servers first :)

DominikG | 20 Nov 2009 | 0 comments
I recognized something strange, which has been quite confusing for some of our customers. Actually the current version von Endpoint Protection (11 RU5) is published with two different version numbers. The packages, you receive through LiveUpdate are listed as 11.0.5002.0 in the Endpoint Protection Manager, but packages you create from other sources, e.g. downloads from Symantec’s fileconnect , are listed as 11.0.5002.333.
 
This fact makes it possible to import both versions into the Manager, if you received the packages through LiveUpdate onto your MR4 system and then upgrade it to RU5. After that you will see that four packages with the mentioned two different version numbers get listed under “install packages”.
Now, if you install the package with number 11.0.5002.0 onto a client, it gets actually also listed as installed version 11.0.5002.333. So the whole issue is just wrong information in the Manager, which the software cannot...
Bijay.Swain | 06 Oct 2009 | 1 comment
We are using 1000 license of SCS 3.1 . And all of the Pcs are spread over 20 Km area .  Now we are upgrading those clients to Symantec Endpoint Protection.
Now the problem is we are in a workgroup model network (No active directory domain) so we can’t use group policy/Login script/domain admin account to use push deployment feature of SEP. And Sep doesn’t have any web deployment feature like SCS had earlier. I searched for any option for remote deployment in a workgroup model network but unable to get any solution.
 
So decided to try something which will work in my environment and I came up with an idea, which I have recorded (procedure) as a .swf  file and putting it in the website .It may help others to deply client in workgroup.
Best feature of this is it also removes the old version of Symantec antivirus if present on the client system. You just have to call the user and ask him to open the website...
mthompson | 29 Sep 2009 | 4 comments

I'm a bit confused about the renewal of SEP11.0.  I know it no longer requires a license file or activation but i'm confused about yearly renwal.  Has that gone away?  My system never says its out of date or that the virus definitions have expired.  How am I to know if they have exprired or need renewal? Especially if my system always has a current up to date - date.

I also recenlty installed this on a completly different network for another company and it installed with old 2008 definitions with the warning that said it was out of date but than it did a Live Update and all was well.  I haven't registered anything yet, so this new system is doing the samething, how to know if it is out of date?

Do I really have to worry about this anymore if I buy it once, am I all good?  Confused on what the web-site says and what a Sales Rep says.

---- also on the same note, if I don't have to renew every year is this beacuse Symantec...

Kedar Mohile | 28 Sep 2009 | 2 comments

Migrating SEPM DB to SQL 2008

The procedure would remain same as before. You might want to check the following

  1. Remove the SEPM from any replication setup with other SEPMs
  2. Backup the SEPM server certificate
  3. Backup the existing SQL database using SEPM backup and Restore wizard
  4. Install an instance of Microsoft SQL Server 2008
  5. Uninstall the Symantec Endpoint Protection Manager
  6. Reinstall the Symantec Endpoint Protection Manager configured to use a new Microsoft SQL Server 2008 database
  7. Restore the SEPM server certificate
  8. Restore the backup copy of the database
  9. Reconfigure the Symantec Endpoint Protection Manager database to recognize Microsoft SQL Server 2008 by running Management Server Configuration Wizard

Reference: Symantec Endpoint...

shp | 04 Aug 2009 | 1 comment

Hi All...

I would like to share my story regarding Symantec Endpoint Protection.  I am from HCL Infosystems Ltd, where I am a Customer Engineer managing a team of five people.  Specifically, I manage SEP deployments for our customers.

This particular customer had an older AV software installed which wasn't providing thorough protectio - a virus outbreak in the network caused many of the machines to go down for extended periods of time.  The customer decided to go with SEP primarily because of its new features.  Specifically, they wanted individual management points in each location, and one central location to manage the entire infrastructure.  Previously, they were not able to bring all clients under one management console due to various difficulties.  The deployment consisted of 49 locations across India, with one server in each location.  Additionally, one server was deployed in Bangalore as the primary server. ...

IanZ | 20 Jul 2009 | 1 comment

Last year, we started looking at SEP11. As we're still running on SAV8 for majority of the servers and clients, with a few SAV9 and SAV10, I believe it's about time to start upgrading to the latest version. I checked the features, documentations, forums, blogs, articles and everything about SEP and I'm getting a negative feedback, a lot of people are complaining. Some even call it a nightmare! Very discouraging. I kept on thinking, as the Server Technology Analyst and only 1 year with the company, I don't want to risk my new job as well as mess around with the servers. Is SEP11 ready for primetime, or is it a disaster? SEP11 is September 11, hmmm, a 9/11 disaster! So we didn't rushed to deploy this. Instead, I started working on test servers and clients. At the same time, as I'm the only one who's going to deploy and implement this, I need to have a plan, a very safe one.

I created a project plan, first looking at the existing SSC setup and...

Rafeeq | 16 Jul 2009 | 8 comments

Hi There,

I'm Rafeeq, I work as a security consulant for a client, we handle their entire security infrastructure,including IPS signatures and network monitoring.
My client has around 2000+ computers in their environment. They had a mixed enviroment consisting of SAV 8.x and SAV10 running on two different domains with mixed mode. Their license was about to end for SAV 10 this september , hence they decided to go for an upgrade , client did not have any second thoughts of chosing different antivirus vendors no matter even if it comes for free, the reason they had (i'm sure we all agree to these points :) )

1) The detection rate of symantec is higher than any other antivirus companies i agree to this coz symantec has global sensors all over for this detection

              4 symatnec SOC
              74 symantec Monitored Countries...