ITMS Administrator Group

 View Only
  • 1.  BUG or BUG - Did you have some your w2003 clients updating their plugins before the base agent ?

    Posted Oct 15, 2012 01:48 PM

    If you run the Agent detail report, you will have current numbers each plugins/agent versions:

    select [Agent Name], [Product Version], [Count] = count(*) from dbo.Inv_AeX_AC_Client_Agent 
    join vItem on _ResourceGuid = Guid 
    group by [Agent Name], [Product Version] 
    order by [Agent Name], [Product Version]
     
    A very usefull report should be in the platform by default, also use this one in drill-down below:
    SELECT     vri4_Computer.Guid AS _ItemGuid, vri4_Computer.Name, [dca6_AeX AC Client Agent].[Agent Name], [dca6_AeX AC Client Agent].[Product Version], 
                          [dca5_AeX AC Identification].[Client Date], [dca5_AeX AC Identification].[Last Logon User], vri4_Computer.[User], vri4_Computer.[OS Name], vri4_Computer.[IP Address],
                           vri4_Computer.[System Type]
    FROM
       vComputer AS vri4_Computer
          LEFT OUTER JOIN [Inv_AeX_AC_Identification] AS [dca5_AeX AC Identification]
             ON ([vri4_Computer].[Guid] = [dca5_AeX AC Identification].[_ResourceGuid])
          LEFT OUTER JOIN [Inv_AeX_AC_Client_Agent] AS [dca6_AeX AC Client Agent]
             ON ([vri4_Computer].[Guid] = [dca6_AeX AC Client Agent].[_ResourceGuid])
    WHERE
       (
       [dca6_AeX AC Client Agent].[Agent Name] LIKE '%PluginName%'
    AND
       [dca6_AeX AC Client Agent].[Product Version] LIKE '%PluginVersion%'
       )
     
    You perhaps will notice a strange behavior, after updating MP1 (or not after MP1, never know), some Windows server 2003, were updating their plugins, without having updated the base agent…

    The plugins upgrade policies are (most) excluding by default the follow filter’s members:

    Windows Computers Requiring Symantec Management Agent Upgrade

    So the plugins will auto-upgrade by default, only on “updated base agent” latest version…

    That is nice, because you just have to upgrade your base agent, carefully on a pilot group, before deploying worldwide, isn’t?

    You don't and keep default "all deploy one shot" ? You should'nt do that, you know :) All the same I do not see new agents problems from a long time.

    All the plugins will follow only on the Pilot computers… Should be! And is not: I was surprise to see a few systems, still having the previous version base NS agent, updating to the latest plugins before ???

    I spent a few times to investigate and found the following, and reproduce this problem in 2 installations.

    The function:

    fnIsSupportedClientOS([OS Name], [OS Revision])

    used inside this filter “Windows Computers Requiring Symantec Management Agent Upgrade

    Seems to provide a RANDOM result: Shoudl try this query below your own installation to see.

    Select

    vcomputerex.[OS Name]

    , [OS Version]

    , IsManaged

    , dbo.fnIsSupportedClientOS(vComputerEx.[OS Name], vComputerEx.[OS Revision]) AS SupportedClientOS

    , COUNT(*) AS NBcomputers

    from vComputerEx

    where dbo.fnIsSupportedClientOS(vComputerEx.[OS Name], vComputerEx.[OS Revision])  = 0

    group by vcomputerex.[OS Name], [OS Version], IsManaged, dbo.fnIsSupportedClientOS(vComputerEx.[OS Name], vComputerEx.[OS Revision])

    Customer 1 shows:

    1 computer is not a "supported OS", using windows Server 2003 ???

    OS Name

    OS Version

    IsManaged

    SuppCltOS

    NBpcs

    CentOS 4/5 (32-bit)

     

    0

    0

    1

    Microsoft Windows 2000

    5.0

    0

    0

    3

    Microsoft Windows Server 2003

    5.2

    1

    0

    1

    OnTap

    7.3.1

    0

    0

    3

    OnTap

    8.0.1

    0

    0

    3

    OnTap

    8.0.2

    0

    0

    5

    Other (32-bit)

     

    0

    0

    1

    Samba

    3.0.20

    0

    0

    3

    Unknown Linux

     

    0

    0

    26

    vmnix-x86

     

    0

    0

    15

     

    Customer 2 shows

    This time, 6 computers 2003, and 1 win7 is not "supported OS"

    OS Name

    OS Version

    IsManaged

    SuppCltOS

    NBpcs

    HDS NAS OS

    8.2.2374.08

    0

    0

    2

    Linux

    2.6.18.8

    0

    0

    1

    Microsoft Windows 2000

    5.0

    0

    0

    132

    Microsoft Windows NT

    4.0

    0

    0

    21

    Microsoft Windows Server 2003

    5.2

    1

    0

    6

    Windows 8 Professionnel

    6.2

    0

    0

    1

    Windows 7 Édition Intégrale

    6.1

    1

    0

    1

     

    More strange  also others servers, with same  OS Name & Version, give a correct result, with the same fn !?!

    angry

    If you run this query, focus on the OS I see a problem (but perhaps not only those one)

    select

    vcomputerex.[OS Name]

    , [OS Version]

    , IsManaged

    , dbo.fnIsSupportedClientOS(vComputerEx.[OS Name], vComputerEx.[OS Revision]) AS SupportedClientOS

    , COUNT(*) AS NBcomputers

    from vComputerEx

    where [OS Name] IN('Microsoft Windows Server 2003','Windows 7 Édition Intégrale')

    group by vcomputerex.[OS Name], [OS Version], IsManaged, dbo.fnIsSupportedClientOS(vComputerEx.[OS Name], vComputerEx.[OS Revision])

    Customer 2:

    OS Name, OSV, IsMgd, SupOS, NBpcs

    Microsoft Windows Server 2003, 5.2, 0, 1, 43

    Microsoft Windows Server 2003, 5.2, 1, 0, 6

    Microsoft Windows Server 2003, 5.2, 1, 1, 1

    Windows 7 Édition Intégrale, 6.1, 1, 0, 1

    Customers 1:

    OS Name                                     OSv IsMgd SupOS  NBpcs

    Microsoft Windows Server 2003      5.2     0       1          23

    Microsoft Windows Server 2003  5.2      1       0         1

    Microsoft Windows Server 2003      5.2      1       1         19

    Here the fn

    Seems not possible to display

    Such 2 different results…

    USE [Symantec_CMDB]

    GO

    /****** Object:  UserDefinedFunction [dbo].[fnIsSupportedClientOS]    Script Date: 10/15/2012 18:07:54 ******/

    SET ANSI_NULLS ON

    GO

    SET QUOTED_IDENTIFIER ON

    GO

    ALTER function [dbo].[fnIsSupportedClientOS](@sOSName nvarchar(64), @sOSRevision nvarchar(64))

    returns bit as

    begin

                    declare @fRes bit;

     

                    set @sOSName = LOWER(@sOSName);

                    set @sOSRevision = LOWER(@sOSRevision);

                    if

                    (

                                   @sOSName LIKE '%windows xp%'

                                   OR @sOSName LIKE '%server 2003%' and

                                                                                                                                 (@sOSRevision is null or @sOSRevision != '' and @sOSRevision not like '%service pack 1%')

                                   OR @sOSName LIKE '%2008%'

                                   OR @sOSName LIKE '%vista%' and (@sOSRevision is null or @sOSRevision != '')                              OR @sOSName LIKE '%windows 7%'

                                   OR len(@sOSName) = 0

                                   OR @sOSName is null

                                   OR @sOSName LIKE '%unknown windows%'

                    )

                                   set @fRes = 1;

                    else

                                   set @fRes = 0;

     

                    return @fRes;

    end

     

    Informatics is not random system, normally …

    SQL server are:

    • version SQL 2008 standard 64 bits (10.0.2531.0), EN, Collation "French_CI_AS"... in customer 2
    • and SQL 2008 standard 64 bits (10.50.1617.0), EN, "SQL_Latin1_General_CP1_CI_AS (Yes we know not in the list, but when migrating from 7.0, no way to change collation: don't try this, we already...)

     



  • 2.  RE: BUG or BUG - Did you have some your w2003 clients updating their plugins before the base agent ?

    Posted Oct 15, 2012 01:58 PM

    In the same time, I do not feel the "filters" updated after MP1, why such 2500, 2614 obsolete build for NS agent (just see the software / Agent and plug-in Filters: search "Symantec Management Agent")



  • 3.  RE: BUG or BUG - Did you have some your w2003 clients updating their plugins before the base agent ?

    Posted Oct 16, 2012 06:07 AM

    Thanks for this info, something for the rest of us to look out for.

    I roll out almost everything (Agents, OS patches, software updates) to test group (5 machines), wait a week, Pilot group (50-200 machines depending on total), wait a week, 20% (machines ending in '2' or '5') wait a week and only then to all targets.

    Motto, always check the "Computers" view of your targets.