Symantec Management Platform (Notification Server)

 View Only
  • 1.  Deployment Compliance SQL Query returns inaccurate results

    Posted Nov 22, 2016 01:14 PM

    Hello,

    I inherited our current 7.1 Symantec Notification Platform from my predecessor about a year ago, including 2 Notification Servers, 2 SQL Servers, 2 site servers  and about 5000 machines. After the deployment of a policy we run a SQL Query to get an overview of the results, returning 1 entry for each computer and a status "Not Applied", "In Compliance" or "Not In Compliance".

     

    When I started, the query returned about 95% of computers as "In Compliance" with an average of 5% falsely reporting as "Not Applied". When remoting into the computer and observing the Altiris Agent, the status of those endpoints was in fact "In Compliance". A 5% False Negative rate wasn't too bad at the time and we just went with it, understanding that this is how things would be from now on.


    The problem is as following: Over the last half year, the computers falsely returning "Not Applied" has grown from 5% to over 40% per deployment. This is creating a lot of manual follow up work for me. Does anyone perhaps know why this is happening and what I can do to resolve this?


    SQL Query used (start/end dates and policy name change per deployment:

    USE Symantec_CMDB

    DECLARE @PolicyName   nvarchar(256),

            @ComputerName nvarchar(256),

            @SoftwareName nvarchar(256),

            @StartDate    datetime,

            @EndDate      datetime

     

    SELECT  @StartDate    = '20161115', 

            @EndDate      = '20161122'

     

     

    BEGIN

    SELECT  @EndDate   = DATEADD( ss, 86399, @EndDate )        -- + 23:59:59

     

    SELECT  @PolicyName   = LOWER( N'POLICYNAME' ),

            @ComputerName = LOWER( N'%' ),

            @SoftwareName = LOWER( N'%' )

     

    EXEC [dbo].[sp_SWM_SoftwareComplianceStatus]

            @in_PolicyName   = @PolicyName,

            @in_ComputerName = @ComputerName,

            @in_SoftwareName = @SoftwareName,

            @in_StartTime    = @StartDate,

            @in_EndTime      = @EndDate,

    --@in_ScopeCollectionGuid = '%ScopeCollectionGuid%',

            @in_TrusteeScope = N'{2E1F478A-4986-4223-9D1E-B5920A63AB41},{582029E2-FC5B-4717-8808-B80D6EF0FD67},{7091A13C-55C3-4E51-B164-8955EE25E1C2},{B760E9A9-E4DB-404C-A93F-AEA51754AA4F},{BBE5AFA7-989C-4C07-88EC-4ECA8599CBB6}'

            --@in_Culture      = '%_culture%'

    END



  • 2.  RE: Deployment Compliance SQL Query returns inaccurate results

    Posted Dec 01, 2016 04:34 PM

    bump



  • 3.  RE: Deployment Compliance SQL Query returns inaccurate results

    Posted Dec 02, 2016 07:32 AM

    Hi,

    The only way to go is to start planing for an upgrade. I am not 100% sure if you can go directly from 7.1 to 8.0 however all versions ater 7.1 are much more stable. I remember the time on 7.1. The were lots of issues all the time. Also there were lots of problems with the agents. This is kind of what you describe. The agents doing there job, however they do not correctly report back. But the were also problems with agents where it only helped to restart the service locally (restart of the os did not help).

    Anyhow there are some tools to help you even on 7.1. Check out RAAD. This is great tool to check and troublehsoot clients locally from remote. Again just do this as long as you are on 7.1. As prio 1 is to get to upgrade.

    Another reason to upgrade especially when you ask about "compliance". Check out this blog:

    https://www.symantec.com/connect/blogs/plug-itms-cms

    There you seen the "nice" overwiew of compliance built-in in the console (enhanced view).

    So lose not too much time on troubleshooting 7.1. Go ahead with the upgrade:

    https://support.symantec.com/en_US/article.DOC8649.html

    Stefan



  • 4.  RE: Deployment Compliance SQL Query returns inaccurate results

    Posted Dec 02, 2016 07:35 AM

    It seems like you have to go to 7.5 or 7.6 first

    https://support.symantec.com/en_US/article.DOC7718.html

     before you can go to 8.0

    https://support.symantec.com/en_US/article.DOC9160.html