Endpoint Protection

This is a fresh install independant of the SEPM server install. I wanted to install the client, just to see what options there are/were, and when I did the install, there were 2 errors from the get go, I will attach a picture to show the example

I have even tried to copy the Sylink.xml from the SEPM to no avail. It continues to show as it does in the picture. It is also well past the heartbeat time. The Shield has a small red cross out circle at the bottom right side of it saying there are multiple problems. The first question I have is how to resolve this, the second is why didn't the Sylink.xml fix work? (I have never gotten it to work)

Thank you.

Here is another shot

I thnik your installation might have gone corrupted try to uninstall the client & then reinstall it from the installation CD as an unmanaged client & see what happens.

Even still if it does not work then try this document

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007112113262148

 Also make sure that you are using the latest version of SEP.

It sounds like there is an issue with the package you are using to install.

I would recommend logging into the SEPM (while local to the box or via the Java Remote Console) and exporting a new install package from the Admin tab.

Try the steps given below 

1. Uninstall SEP
2. Change DCOM permissions
3. Reboot the machine
4. Re-install SEP

Checking DCOM settings

The last place to check rights on a computer is in its DCOM settings.

To verify Distributed COM properties

1. On the Windows taskbar, click Start > Run.
2. Type the following, and then click OK:
   
   dcomcnfg
   
    
3. Do one of the following, depending on your operating system:
   • In Windows XP/2003, click Component Services > Computers > My Computer. Then right-click My Computer and click Properties.
   • In all other versions of Windows, go on to the next step.
4. On the Default Security or Default COM Security tab, under Default Access Permissions, click Edit Default.
5. Verify that Administrators, Interactive, and System accounts are set to Allow Access, and then click OK.
6. Under Default Launch Permissions, click Edit Default.
7. Verify that the Administrators, Interactive, and System accounts are set to Allow Launch, and click OK.
8. Do one of the following, depending on your operating system:
   • In Windows XP/2003, skip the two following steps.
   • In all other versions of Windows, go on to the next step.
9. In the Default Configuration Permissions section, click Edit Default.
10. In the Registry Key Permissions window, verify that the following are set to Full Control, and then click OK:
    
    CREATOR OWNER
    ...\Administrators
    SYSTEM
    
     
11. On the Default Properties tab, verify that Default Impersonation Level is set to Identify.
12. Click Apply, and then click OK.
13. Restart the computer for the changes to take effect.

This IS the latest installation. This is also NOT a package, this is STRAIGHT from the CD1 folder that I downloaded from Fileconnect. I wanted to test a straight forward install without using SEPM, so far it has been a disaster.

It was my objective NOT to use a package from the SEPM server. I wanted to do an install as if I were doing it with a CD. After this testing, I will NOT permit my administrators to install it in this manner, because the results were all negative and there was a lot of overhead into testing it, installing it and removing it.  When we installed SAV, we would have the choice to select the managed clients and associate it accordingly, this is NOT available in SEP local installations. I personally feel this is a drawback but from the experience I will have to develop a procedure for any future installations of SEP to the clients. :-(

Wow, this product is quite complex, I am developing a whole new skill out of putting this project together alone. I will check the DCOM configurations on my PC tomorrow, I just hope that I do not have to do this wide scale.
I will advise further tomorrow.

The DCOM is not the part of SEP. it is the part of OS.

If there is incorrect permission then only we look for DCOM else it is not required.

...It is very difficult to tell if the change to the DCOM configuration worked. When I previously had an issue, I would simply try to uninstall, and when I did do so, the uninstall just hung and said it had 20 minutes, this morning I decided to wait it out, only to meet a "fatal error" uninstallation issue. Previously I had used cleanwipe to remove the SEP client from the local install, and it certainly lived up to its name, but not only wiping out SEP, it also wiped out my network connections, it was anything BUT a clean wipe. I restored the connections, and decided to disable ALL symantec services and do the uninstall and re install, the uninstall was successful as we the re install, now it is time to try my luck with using sylink.xml.

I will advise...

Worked PERFECTLY this time.

Thank you again.