Endpoint Protection

 View Only
  • 1.  SEP Content Distribution Monitor Duplicate Entries

    Posted Mar 12, 2013 11:52 AM
      |   view attached

    I am seeing a couple of duplicate entries for GUPs in the Content Distribution Monitor.  Generally the duplicate contain the same details as the other entry, but on some of them they are slightly different.  I know this is not a supported tool from Symantec, but I am hoping someone in the community might know why this happens.

    I love this tool, but I want to make sure the information I am getting from it is accurate, and these duplicates (see attached) leave me questioning whether the GUP is up to date or not.



  • 2.  RE: SEP Content Distribution Monitor Duplicate Entries

    Posted Mar 12, 2013 11:57 AM

    If you search in SEPM, do you see multiple entries as well? What version of SEP are you on? If you delete the older entry this should fix automatically. Was a re-install of the client recently done?



  • 3.  RE: SEP Content Distribution Monitor Duplicate Entries

    Posted Mar 12, 2013 12:17 PM

    Whats the version of the monitor ..2.8?

    https://www-secure.symantec.com/connect/videos/sep-content-distribution-monitor-introduction



  • 4.  RE: SEP Content Distribution Monitor Duplicate Entries

    Posted Mar 12, 2013 01:10 PM

    Content Monitor version is 4.8.

    I'm seeing the problem more on my 12.1.2015.2015 SEPM, but see 1 or two on my SEP 11 server also.

    I searched for duplicate entries on the SEPM and there are none.  The SEPM shows the client is up to date.

    As to the question of a re-install being done, that is probable, particuarly on the SEP 12 server where I see most of the duplicates.  I am migrating clients from SEP 11 to SEP 12 slowly (location by location) and clients are being upgraded to the new version as part of that process.



  • 5.  RE: SEP Content Distribution Monitor Duplicate Entries

    Posted Mar 12, 2013 01:17 PM

    Duplicates would show up quite a bit in 12.1 RU1 but it ended up being a bug so it doesn't sound like this is the issue in your case. I would suggest a call to support.