Endpoint Protection

Dear Technical experts,

we Updated SEPM MR5 to MR6a, all Polices everything fine on 32 bit OSs.

but we got two problems a. policies not updating on WIN7 64bit

                                         b. clients not finding through Find unmanaged computers option

pls give the solution..

Krishnamraju

This is the wrong forum.  This is ticketing software.

However, make sure the client can talk to the server.  Is there a green dot on the SEP shield in the system tray in Windows 7?  If not, it has communication problems -- try disabling the firewall or adding a TCP port exception for 8014.

Does this help?

Please provide more details.

Operating System on the Server?

Any specific policy not updating or any policy is not updating?

Do you have SEP installed on all the computers? The computers those you are trying to find using Find Unmanaged Computers do they have SEP?

Just disable the Windows Firewall  and see what happens, for both a, and b...

Is anybody here know or recommend which is the best malware --anti-spy and antispam tool? We have symantec endpoint 11.06 as virus tool but now we are looking for a malware tools.

I did a lot of search and found webroot corporate antispy edition and sunbelt Counterspy as well as malwarebytes but I am not sure which one is better since I never heard about them. I cannot find any malware reviews on the web site.

Someone also recommended symantec critical system protection. Has anyone used this prodcut beofre. Is it harder on the system and a resource hog?

Any reply will be appreciated!!!

mxu

"Oh no, Symantec Endpoint Protection did not catch it!  It is 11:45 a.m. on September 27, and I'm using the defs I got from the server yesterday at noon.  SEP must be a total failure.  I will download MalwareBytes and get the definitions from 11:30 a.m.  Hey, look!  It caught something SEP did not catch.  MalwareBytes must be better than SEP at catching and removing malware."

In reality, RapidRelease definitions for SEP published at 11 would have caught the malware if you bothered to download them.  If you really want a security-in-depth strategy, take your Webroot dollars and spend it on a secure network perimeter, or on a project to train users on security, or on restricting permissions, or on website filtering, or better Windows patching, or keeping third-party apps (like browsers and plug-ins like Java, Adobe Reader, Flash, etc) up-to-date.

*SEPM MR6a

* Windows 2003 Ent R2

* SEP installed in all PCs through pushing with find unmanaged computers Option

and SEP64 bit installed through Migration and deployment option in Win7 64 bit, 

every thing fine but any policy not updating in WIn7

Regards

Krishnamraju

Replace sylink file manually in one of the affected clients and see the result

For this
export the communications settings from the server

In the console, click Clients.

Under View Clients, select the group in which you want the client to appear.

Right-click the group, and then click Export Communication Settings.

In the Export Communication Settings for group name dialog box, click Browse.

In the Select Export File dialog box, locate the folder to where you want to export the .xml file, and then click OK.

In the Export Communication Settings for group name dialog box, select one of the following options:

To apply the policies from the group from which the computer is a member, click Computer Mode.

To apply the policies from the group from which the user is a member, click User Mode.

Click Export.

If the file name already exists, click OK to overwrite it or Cancel to save the file with a new file name.

To finish the conversion, you or a user must import the communications setting on the client computer.

For this
Copy the SylinkDrop.exe file to the desktop of the client you want to be managed.
This tool can be found on CD 2 of the Symantec Endpoint Protection 11 installation files, in the folder "\TOOLS\NOSUPPORT\SYLINKDROP". It can also be obtained from Symantec Technical Support.
Double-click SylinkDrop.exe.
 When prompted to select a Sylink.xml file, select the Sylink.xml you created in previous steps.
Click on update sylink.
After replacing it will give a message as sylink has been replaced successfully. 

Or 

You can use this method also for changing the sylink file

On the client computer , click Start > Run, type smc -stop, and click OK.
 Copy the Sylink.xml into the C:\Program Files\Symantec\Symantec Endpoint Protection folder, and replace any existing Sylink.xml file.(This name is important)
Click Start > Run, type smc -start, and click OK.