Endpoint Protection

I have a number of clients who are showing up in my console as umanaged.  The sylink.xml file is right (since it is the SAME one on some workstations that are working).  I've dealt with support who had me do the sylinkreplacer, run syllink monitor on test clients.  Taking this one client here's their sylink monitor file

05/05 15:46:58 [3080] <CSyLink::mfn_DownloadNow()>
05/05 15:46:58 [3080] </CSyLink::mfn_DownloadNow()>
05/05 15:47:46 [688] <ScheduleNextUpdate>Manually assigned heartbeat=1 seconds
05/05 15:47:46 [5652] AH: (InetWaiting) urgent exit event on InetCtrlBlock: 01C1CB50
05/05 15:47:46 [5652] Throw Internet Exception, Error Code=997;AH: failed to send request...
05/05 15:47:46 [5652] <MaintainPushConnection:>COMPLETED
05/05 15:47:46 [5652] <ScheduleNextUpdate>new scheduled heartbeat=32 seconds
05/05 15:47:46 [5652] HEARTBEAT: Check Point 8
05/05 15:47:46 [5652] <PostEvent>going to post event=EVENT_SERVER_DISCONNECTED
05/05 15:47:46 [5652] <PostEvent>done post event=EVENT_SERVER_DISCONNECTED, return=0
05/05 15:47:46 [5652] <IndexHeartbeatProc>====== IndexHeartbeat Procedure stops at 15:47:46 ======
05/05 15:47:46 [5652] <IndexHeartbeatProc>Set Heartbeat Result= 2
05/05 15:47:46 [5652] <IndexHeartbeatProc>Sylink Comm.Flags: 'Connection Failed' = 0, 'Using Backup Sylink' = 0, 'Using Location Config' = 0
05/05 15:47:46 [5652] Use new configuration
05/05 15:47:46 [5652] HEARTBEAT: Check Point Complete
05/05 15:47:46 [5652] <IndexHeartbeatProc>Done, Heartbeat=32seconds
05/05 15:47:46 [5652] </CSyLink::IndexHeartbeatProc()>
05/05 15:47:46 [5652] <CheckHeartbeatTimer>====== Heartbeat loop stops at 15:47:46 ======
05/05 15:47:58 [3080] <CSyLink::mfn_DownloadNow()>
05/05 15:47:58 [3080] </CSyLink::mfn_DownloadNow()>

(and yes this was after turning on debug for the sylink key in this machine's registry


I'm not sure where to proceed next.  The clients get updates just fine.  I do have WSUS in a customized install ON the same server as SEP.  (yes I had to reinstall WSUS since SEP merrily overwrote half the IIS settings since the developers at Symantec insisted on using the same file structure.

I really don't want to have to visit all the workstations that show up as unmanaged.  So what else can I do?

The workstations happy as it can be.  It just shows up on my console as unmanged.

Oh and the little green dot IS on the SEP logo in the system tray, so the pc also thinks that IT is managed.

I'd love to get this solved. 

When you say it shows up in the console as unmanaged, what do you mean?  Are you talking about Find Unmanaged Computers?  Feel free to upload a screen shot of what you see in the SEPM, or the whole sylink log, since the portion you included doesn't show nearly enough.  (Upload as a file not as a copy/paste.)

sandra

I could do the picture but all it says after I search for "find unmanaged computers" from my SEP management console  is the computer I sent the information (the other screen shot) with it's name, IP and "deployed status" as no. 

i..e in my console after I search for unmanaged, the console says this particular computer IS unmanaged.  (so I choose to believe that the console thinks it's unmanaged)

I can go reproduce the picture, but it seemed pretty evident.  I searched for unmanaged, this computer came up.  The console does not thing this particular client is managed, but the client end seems to think it is because of the sys tray logo saying so.

Do you have clients distributed in various sites or domains..find unmanaged computer will show all the clients which are not managed by that particular SEPM.

Even though found via Find Unmanaged Computers, does the client computer appear or not appear in the correct group?

Title: 'Symantec Endpoint Protection clients do not appear in the Management console, but are being updated and the shield icon shows a green dot.'
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007111510031148

I'm in a worldwide company but the clients are on the local segment.  I'm searching by IP address which is unique for my site

Nope not that as an issue.