Intel,Altiris Group

my client, several days ago uninstall norton partition magic in their server which also have symantec endpoint protection manager console and endpoint client, at the end of the process they choose to uninstall also the shared files from symantec, after that the symantec endpoint manager and client could not be operated again.
they tried to repair the damage, but in the end they decided to uninstall the symantec endpoint protection manager console and client.
after that they call me to support their problem.
i install the server but not at the same port they used to used which 8443, but at 8015
and then i deploy the client, but the client cannot online with the server, the status always offline,
can u guys help me?
thank u

regards,


Mike

u first uninstalled completly ther after u installed, some old file are not uninstalled that's why u use different port

have you checked the firewall in both the machines?? are both of them communicating with each other? also tell which operating system is running on both of the machines, also tell which version of symantec endpoint are u using, it would be much easier if you give these details.

For the client you deployed, did it already have the SEP client installed?  If not, then I agree with Sapta to check your firewall epecially on the server that it is not blocking ports for client communication.  Since your were able to deploy a client, how did you do this?  From the Migration and Deployment wizard? 

Also to note, was the client installation package exported again since uninstalling/re-installing the SEPM?  If not, export another client installation package to ensure you have the correct sylink.xml file in the package.  For the client not communicating with the server, uninstall SEP and delete the default installation folder for SEP on the client (search for all sylink.xml files for the folders to delete)  then push or install the newly exported client installation package from the SEPM.  Your client may have the old sylink.xml file trying to talk to the server on port 8443 which is why the client is showing the server offline.

after they uninstalled, to have a clean instalation, i used regedit to clean all the symantec products, but the 8443 port maybe being used by the clients to update, because the are 150 clients on the server

absolutely rick,
but we need these details, unless we cannot proceed further....

did you use the clean wipe tool or manually deleted the registry entries of symantec?

yes, the firewall which active is from symantec, both can comunicate, they on the same workgroup, they using xp pro, and the version symantec endpoint they using are 11.0.4000.2295

ok, i'll try and then will report to you guys, thank u

Hi Sapta,

I completely agree, more details are needed and manager/client versions should *always* be included for any thread posted for support (wish this was a required field when posting). However, my post covers many versions of SEP/SEPM.  To me, it sounds like a sylink.xml issue where the clients are trying to communicate on the wrong port (since he changed the port on uninstall/reinstall). 

i totally agree with you in this regard, the clients are not communicationg with the server for sure, otherwise it would have been a different problem, sylink.xml file can be considered as a valid reason for this problem, lets see what update we get from the thread starter.

Replacing sylink.xml file with the Sylink replacer utilities should be first tried to the solve any communication issue you have. It's a great utility and easy to work with.

Check some other forum, where sylink replace procedure is explained in details. (I do not know right now, else I would have given it to you)

Tejas

Hi,

       You mentioned that you reinstalled the SEPM on the server and used port 8015 instead of 8443 during the configuration. Since the clients were reporting to the old SEPM they are configured for port 8443, however now that the port has changed the clients will not communicate with the manager. Here are a few things that you should consider when you face such a issue.

If the OS on the SEPM server is Windows 2008, you need to configure the Windows Firewall and allow the port 8015 through the firewall.

Check whether the clients on which endpoint is installed have a PASSWORD for uninstallation of this software because if that is the case the clients wont get the new sylink.xml file and hence will not report to the manager.

Create a new Client package and push it to one or two clients and check whether they communicate with the SEPM Console.

If you open the SyLink.xml file for the agent, you can verify if the agent is configured to connect to the correct port. You will see something similar to the following:

<Server Address="10.10.10.133" HttpPort="8014"

Where the ip address is the address of the Policy Manager that the client connects to and the http port is the port number that the client connects to on the policy manager.

Perhaps if you change the port on the policy manager to match the agents, this might solve your issue.