Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Security Community Blog

Showing posts tagged with Installing remove filter
t_dawgy78 | 04 Aug 2009 | 0 comments

The Symantec Protection Suite Small Business Edition Promotion is available through end of this year.
For those of you on older Symantec products, this is a great way to upgrade to the new Protection Suite Small Business Ediiton, which includes the new SEP SBE 12.0.
Offer details are located here: http://go.symantec.com/protection-suite-promo
:Upgrade to SPS SBE and get up to a 30% discount. This offer is valid through the end of this year, and is for any current Symantec customers on the following products:
• Symantec Antivirus Corporate Edition
• Symantec Client Security
• Symantec Backup Exec System Recovery Desktop Edition
• Symantec Mail Security for Microsoft Exchange
• Symantec Premium Antispam
• Symantec AntiVirus for Macintosh

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.  The...

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 rush 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 client configurations. As another...

sezam | 14 Jan 2010 | 0 comments
Some time I face with customer which have a problem with continuous SEP installation.

This could be connected with 2 problems:

1. Domain or Local User privileges are to restricted[remember to much restrictions is also not good. You need to know how to balance with restrictions]
2. Installation is corrupted.

This problem is annoying because Windows Installer want to install SEP client continuously which can be very nervous.
 

Solution for this problem is to:




 

1. Find UninstalString value for Symantec Endpoint Protection which is situated in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

2. Paste this string to command line with changed option /I to /X (  ex.  MsiExec.exe /X{68B52EFD-86CC-486E-A8D0-A3A1554CB5BC}   ) 

sezam | 14 Jan 2010 | 5 comments

 REMEMBER THAT ONLY SUITABLE VERSION FOR WINDOWS 7 IS SEP 11.0.5 RU5

 
Sometimes SEP client is unable to install itself on Windows7 operating systems.

The problem is connected with 2 issues.
 

1. EXE file extractor[FreeExtractor] is not working correctly.

Sometimes on Windows 7 setup.exe file cannot automatically extract into %TEMP% folder.
To resolve this issue You need to Extract setup.exe file application like Winrar and install SEP using setup.exe or *.msi file in extracted folder.

2. Live Update application cannot be installed.


To resolve this problem You need to perform first step from point 1. but in hear firstly You need to install Live Update using LUSETUP.exe file after install it using setup.exe or *.msi file.
Second solution is to install SEP as unmanaged client.

JBrown039 | 11 Jan 2010 | 0 comments

Recently i left my old company and need to uninstall my previous version of symantec version 10.1.5 manually.  I keep getting a password prompt when i try to uninstall the program from add/remove programs.  Is there a way to bypass this step?

Mhine | 05 Jan 2010 | 2 comments

Ghost Solution Suite 2.5, the latest version, is not currently compatible with Windows 7. Symantec is working on an update to GSS 2.5 that will allow for installation as well as the cloning of Windows 7. We will update this article when that update is available.

Although unsupported the Ghost executables from GSS 2.5 LU3 (build 2165) may clone a Windows 7 file system when used in a PreOS environment.
There are a few things to consider if you plan to test the cloning of Windows 7:

· Do NOT install Ghost Solution Suite on the Windows 7 Operating System. Install it into XP or Vista to then use the executables.

· We suggest that you use the Ghost Boot Wizard to create bootable media with the Ghost cloning Executables that can then either connect to a GhostCast Server session or clone to local hard drives

GertjanA | 04 Dec 2009 | 0 comments

When installing multiple EV-servers, where multiple Exchange, File, Domino etc servers need to be checked, it is not very friendly you have to key in the list of servers on each install of Deployment Scanner.

To get the list of servers on all of your Deployment Scanner's do the following:

Install Deployment Scanner on all the servers that need to have it.
Start Deployment Scanner on 1 server, put in the required servers to check, and let it run.
Close Deployment Scanner
Goto the C:\Program Files\Enterprise Vault folder, and copy the file PreReqConfig.xml to the same location on the other servers you installed D.S. on.

Start Deployment Scanner on the other servers, and you will see that the entries are present.

Gertjan

snekul | 24 Nov 2009 | 1 comment

First, some background. We were setting up a new box running Server 2008 R2 Core on x64.  In my department, we push out SEP to all our servers via Group Policy.  On this new Server 2008 R2 Core on x64 box the install of SEP failed.  We were puzzled until we ran into another application (in this case VMware Tools) that did not install properly either.  We discovered that Server 2008 R2 Core does not have an "Installer" folder inside the Windows folder--this would usually be C:\Windows\Installer.  Upon creating the folder, VMware Tools installed fine and on a reboot, SEP installed just fine as well.

Also, we were pushing out RU5, as that is necessary for full support on Server 2008 R2.

So, if you run into trouble installing SEP (or anything else for that matter) on Server 2008 R2 Core, make sure you have an "Installer" directory in your Windows folder.

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...