Patch Management Solution

 View Only
  • 1.  Migration to new version of Symantec Patch Management datafeed

    Broadcom Employee
    Posted Mar 05, 2024 11:53 AM
    Edited by Dmitri Gornev Mar 05, 2024 11:55 AM
    Symantec Patch Management solution will migrate to a new version of patch datafeed (7.4) after March 2024 Patch Tuesday and we encourage you to verify its functionality using Beta datafeed URL.
     
    To participate in Beta:
     
    In the Import Patch Data for Windows task, open the General section
    Click Edit on the Import patch data from the custom location: line
    Select the second radio button for Custom location and paste in this URL, https://www.solutionsam.com/imports/7_4/patch/windows/pmimport.cab
    Leave the default of No Authorization and click OK
    Click Save changes.
    Depending on your version of OS and Patch Management solution you may get "The Alternative Location field appears to be invalid" error.
    Just click "Save changes" again to retry - newer TLS version will be automatically attempted to access datafeed and the new import URL will be saved successfully.

    The main focus of this exercise is the execution of the assessment and installation of updates (there are no changes to content imported on the server side). New datafeed includes changes to the assessment and deployment tools, the way how they integrate with each other and process the assessment results.

     
    Please note that the following operating systems will no longer be supported with the new datafeed version: 
    Windows XP
    Windows Vista
    Windows Server 2003
    Windows Server 2003 R2
    Windows Server 2008
     
    We will provide additional notification when 7.4 datafeed will be promoted to production (it will re-use the same default URL https://www.solutionsam.com/imports/7_1/patch/windows/pmimport.cab).
    Fallback 7.3 datafeed URL will be provided in parallel for a period of time.

    We would like to thank you for your attention and feedback.



  • 2.  RE: Migration to new version of Symantec Patch Management datafeed

    Broadcom Employee
    Posted 9 days ago

    Please note that 7.4 Beta URL is no more updated after release of 7.4 datafeed version to production.




  • 3.  RE: Migration to new version of Symantec Patch Management datafeed

    Posted 4 days ago

    After the Patch Assistance Tool version is upgraded, the Scan result file, STPatchAsession.xml, is not generated successfully. The same result occurs in both 7.1/7.4.




  • 4.  RE: Migration to new version of Symantec Patch Management datafeed

    Broadcom Employee
    Posted 3 days ago

    Hi JaeHeung,

    may you share the following artifacts?

    1. Contents of the assessment package (C:\Program Files\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery\{6D417916-467C-46A7-A870-6D86D9345B61}\cache) without WindowsPatchData.zip file from problematic machine.
    2. Verbose logs of the assessment utility:
    - enable verbose mode of the agent (see https://knowledge.broadcom.com/external/article/179702/how-to-configure-logging-on-the-notifica.html)
    - set registry key (DWORD) SOFTWARE\Altiris\Altiris Agent\Patch Management\Patch Assessment\LoggingLevel to 2bc (700)
    - click on 'Start assessment scan' button in the agent UI to start assessment scan and wait for it to finish.
    - collect agent logs
    3. DPDTrace logs

    Thank you,
    Dmitri.




  • 5.  RE: Migration to new version of Symantec Patch Management datafeed

    Posted 2 days ago
    Dear, Dmitri

    This is Kim Jae Heung.

    I tested both 7_1 and 7_4 PMImport for the computer where the error occurs.
    This does not occur equally on all systems.
    However, once a system occurs, it continues to occur.
    What I checked is that an error occurred when the STPatchAsession.xml file
    was created. Please check below.

    Extracted from a.log

    <event date='04/08/2024 22:51:59.9760000 +09:00' severity='4'></event>
    hostName='kittalt' source='BaseApplication::Run'
    module='AeXPatchAssessmentU.exe' process='AeXPatchAssessmentU.exe'
    pid='10372' thread='10748' tickCount='4710140' >




    *<event date='04/08/2024 22:51:59.9910000 +09:00' severity='1'></event>
    hostName='kittalt' source='Utils::ComException::ComException'
    module='AeXPatchAssessmentU.exe' process='AeXPatchAssessmentU.exe'
    pid='10372' thread='10748' tickCount='4710156' > MSG='Utils::Xml::StringToDocument()- Couldn't load XML text']]>*
    <event date='04/08/2024 22:51:59.9910000 +09:00' severity='4'></event>
    hostName='kittalt' source='BaseApplication::Run'
    module='AeXPatchAssessmentU.exe' process='AeXPatchAssessmentU.exe'
    pid='10372' thread='10748' tickCount='4710156' >


    <event date='04/08/2024 22:52:00.0070000 +09:00' severity='1'></event>
    hostName='kittalt' source='BaseApplication::Run'
    module='AeXPatchAssessmentU.exe' process='AeXPatchAssessmentU.exe'
    pid='10372' thread='10748' tickCount='4710171' >
    load XML text (0x80004005)]]>

    <event date='04/08/2024 22:52:00.3510000 +09:00' severity='4'></event>
    hostName='kittalt' source='CAuxilliaryPackage' module='PatchMgmtAgents.dll'
    process='AeXNSAgent.exe' pid='1040' thread='9300' tickCount='4710515' >


    <event date='04/08/2024 22:52:00.3510000 +09:00' severity='1'></event>
    hostName='kittalt' source='AssessmentTool' module='PatchMgmtAgents.dll'
    process='AeXNSAgent.exe' pid='1040' thread='9300' tickCount='4710515' >



    *<event date='04/08/2024 22:52:00.3510000 +09:00' severity='4'></event>
    hostName='kittalt' source='AeXPatchUtil' module='AeXPatchUtil.exe'
    process='AeXPatchUtil.exe' pid='8700' thread='10656' tickCount='4710515' >
    *

    Extracted from *STPatchAssessment.xml *
    If it's a normal(no error) STPatchAssessement.xml file is

    <patchscan ~~~~~~~~="" at="" the="" beginning="" of="" the="" show="" ~~~~~=""></patchscan> at the
    end of this.

    But, On the computer where the error occurs, it is created as follows.

    <patchscan ~~~~~~="" at="" the="" beginning="" of="" the="" show="" ~~~~~~~="" failed:=""></patchscan>
    Error 2: at the end of this.

    This means that the xml file was created and suddenly interrupted.

    I changed it to 7_3 and tested it.
    You changed to PMimport 7_3, ran the import again, performed a
    configuration update on the client, downloaded the System Assistance files
    again, and ran System Assistance.
    The results are executed without errors. STPatchAsessment.xml is also
    generated normally.

    Thank you & Best regards.
    Kim Jae Heung





    2024년 4월 9일 (화) 오후 9:54, Dmitri Gornev via Broadcom <mail@broadcom.com>님이
    작성:

    > Hi JaeHeung, may you share the following artifacts? 1. Contents of the
    > assessment package (C:\Program Files\Altiris\Altiris Agent\Agents...
    > -posted to the "Patch Management Solution" community
    > [image: Broadcom] <https: community.broadcom.com="">
    > Patch Management Solution
    > <https: community.broadcom.com/symantecenterprise/communities/community-home/digestviewer?communitykey="9eac1757-c53a-4efc-aac8-d63ff93fd247">
    > Post New Message <broadcom-patchmanagementsolution@connectedcommunity.org>
    > Re: Migration to new version of Symantec Patch Management datafeed
    > <https: community.broadcom.com/symantecenterprise/discussion/migration-to-new-version-of-symantec-patch-management-datafeed#bm9d7fae24-96fc-4e3c-b8d9-018ec2e88365="">
    > Reply to Group
    > <broadcom_patchmanagementsolution_9d7fae24-96fc-4e3c-b8d9-018ec2e88365@connectedcommunity.org?subject=re:+migration+to+new+version+of+symantec+patch+management+datafeed> Reply
    > to Sender
    > <https: community.broadcom.com/symantecenterprise/communities/all-discussions/postreply?messagekey="9d7fae24-96fc-4e3c-b8d9-018ec2e88365&ListKey=2e9b0b51-5ba5-498c-8e24-089d6ce9a3d7&SenderKey=422e7b8a-d586-46a3-890d-17b3c0ac020f">
    > [image: Dmitri Gornev]
    > <https: community.broadcom.com/network/members/profile?userkey="422e7b8a-d586-46a3-890d-17b3c0ac020f">
    > Apr 9, 2024 8:54 AM
    > Dmitri Gornev
    > <https: community.broadcom.com/network/members/profile?userkey="422e7b8a-d586-46a3-890d-17b3c0ac020f">
    >
    > Hi JaeHeung,
    >
    > may you share the following artifacts?
    >
    > 1. Contents of the assessment package (C:\Program Files\Altiris\Altiris
    > Agent\Agents\SoftwareManagement\Software Delivery\{6D417916-467C-46A7-
    > A870-6D86D9345B61}\cache) without WindowsPatchData.zip file from
    > problematic machine.
    > 2. Verbose logs of the assessment utility:
    > - enable verbose mode of the agent (see
    > https://knowledge.broadcom.com/external/article/179702/how-to-configure-logging-on-the-notifica.html
    > )
    > - set registry key (DWORD) SOFTWARE\Altiris\Altiris Agent\Patch
    > Management\Patch Assessment\LoggingLevel to 2bc (700)
    > - click on 'Start assessment scan' button in the agent UI to start
    > assessment scan and wait for it to finish.
    > - collect agent logs
    > 3. DPDTrace
    > <https: forums.ivanti.com/s/article/dpdtrace-gui-tool-used-to-troubleshoot-patch-detection-issues?language="en_US">
    > logs
    >
    > Thank you,
    > Dmitri.
    > *Reply to Group Online
    > <https: community.broadcom.com/symantecenterprise/communities/all-discussions/postreply?messagekey="9d7fae24-96fc-4e3c-b8d9-018ec2e88365&ListKey=2e9b0b51-5ba5-498c-8e24-089d6ce9a3d7">*
    > *Reply to Group via Email
    > <broadcom_patchmanagementsolution_9d7fae24-96fc-4e3c-b8d9-018ec2e88365@connectedcommunity.org?subject=re:+migration+to+new+version+of+symantec+patch+management+datafeed>*
    > *View Thread
    > <https: community.broadcom.com/symantecenterprise/discussion/migration-to-new-version-of-symantec-patch-management-datafeed#bm9d7fae24-96fc-4e3c-b8d9-018ec2e88365="">*
    > *Recommend
    > <https: community.broadcom.com:443/symantecenterprise/discussion/migration-to-new-version-of-symantec-patch-management-datafeed?messagekey="9d7fae24-96fc-4e3c-b8d9-018ec2e88365&cmd=rate&cmdarg=add#bm9d7fae24-96fc-4e3c-b8d9-018ec2e88365">*
    > *Forward
    > <https: community.broadcom.com/symantecenterprise/communities/all-discussions/forwardmessages?messagekey="9d7fae24-96fc-4e3c-b8d9-018ec2e88365&ListKey=2e9b0b51-5ba5-498c-8e24-089d6ce9a3d7">*
    > *Flag as Inappropriate
    > <https: community.broadcom.com/symantecenterprise/discussion/migration-to-new-version-of-symantec-patch-management-datafeed?markappropriate="9d7fae24-96fc-4e3c-b8d9-018ec2e88365#bm9d7fae24-96fc-4e3c-b8d9-018ec2e88365">*
    >
    > -------------------------------------------
    > Original Message:
    > Sent: Apr 08, 2024 01:13 PM
    > From: JaeHeung Kim
    > Subject: Migration to new version of Symantec Patch Management datafeed
    >
    > After the Patch Assistance Tool version is upgraded, the Scan result file,
    > STPatchAsession.xml, is not generated successfully. The same result occurs
    > in both 7.1/7.4.
    >
    > Original Message:
    > Sent: Mar 05, 2024 11:52 AM
    > From: Dmitri Gornev
    > Subject: Migration to new version of Symantec Patch Management datafeed
    >
    > Symantec Patch Management solution will migrate to a new version of patch
    > datafeed (7.4) after March 2024 Patch Tuesday and we encourage you to
    > verify its functionality using Beta datafeed URL.
    >
    > To participate in Beta:
    >
    > In the *Import Patch Data for Windows* task, open the General section
    > Click Edit on the *Import patch data from the custom location:* line
    > Select the second radio button for *Custom location* and paste in this
    > URL, www.solutionsam.com/imports/7_4/patch/windows/...
    > <https: www.solutionsam.com/imports/7_4/patch/windows/pmimport.cab="">
    > Leave the default of *No Authorization* and click OK
    > Click *Save changes*.
    > Depending on your version of OS and Patch Management solution you may get
    > "The Alternative Location field appears to be invalid" error.
    > Just click "Save changes" again to retry - newer TLS version will be
    > automatically attempted to access datafeed and the new import URL will be
    > saved successfully.
    >
    > The main focus of this exercise is the execution of the assessment and
    > installation of updates (there are no changes to content imported on the
    > server side). New datafeed includes changes to the assessment and
    > deployment tools, the way how they integrate with each other and process
    > the assessment results.
    >
    > Please note that the following operating systems will no longer be
    > supported with the new datafeed version:
    > Windows XP
    > Windows Vista
    > Windows Server 2003
    > Windows Server 2003 R2
    > Windows Server 2008
    >
    > We will provide additional notification when 7.4 datafeed will be promoted
    > to production (it will re-use the same default URL
    > www.solutionsam.com/imports/7_1/patch/windows/...
    > <https: www.solutionsam.com/imports/7_1/patch/windows/pmimport.cab).="">
    > Fallback 7.3 datafeed URL will be provided in parallel for a period of
    > time.
    >
    > We would like to thank you for your attention and feedback.
    >
    >
    >
    >
    > You are subscribed to "Patch Management Solution" as kimjh@kitt.co.kr. To
    > change your subscriptions, go to My Subscriptions
    > <http: community.broadcom.com/preferences?section="Subscriptions">. To
    > unsubscribe from this community discussion, go to Unsubscribe
    > <http: community.broadcom.com/higherlogic/egroups/unsubscribe.aspx?userkey="a0456a89-ccb0-4599-b272-018e1cd8fa74&sKey=KeyRemoved&GroupKey=2e9b0b51-5ba5-498c-8e24-089d6ce9a3d7">.
    >
    >
    > Copyright © 2005-2023 Broadcom. All Rights Reserved. The term "Broadcom"
    > refers to Broadcom Inc. and/or its subsidiaries.
    >
    > Hosted by Higher Logic, LLC on the behalf of Broadcom - Privacy Policy
    > <https: www.broadcom.com/company/legal/privacy-policy=""> | Cookie Policy
    > <https: www.higherlogic.com/legal/privacy=""> | Supply Chain Transparency
    > <https: www.broadcom.com/company/citizenship/governance-and-ethics#supply="">
    > | Terms of Use <http: termsandconditions="">
    >

    --


    **KITT* - System Consulting, S/W Solution, Rental & Maintenance, Network
    & Security*




  • 6.  RE: Migration to new version of Symantec Patch Management datafeed

    Posted 2 days ago
    I'm sending you a capture file because I can't see the pasted characters.
    a.log
    [image: image.png]

    STPatchAssessment.xml
    [image: image.png]




    2024년 4월 11일 (목) 오전 10:23, JaeHeung Kim via Broadcom <mail@broadcom.com>님이
    작성:

    > Dear, Dmitri This is Kim Jae Heung. I tested both 7_1 and 7_4 PMImport for
    > the computer where the error occurs. This does not occur equally on...
    > -posted to the "Patch Management Solution" community
    > [image: Broadcom] <https: community.broadcom.com="">
    > Patch Management Solution
    > <https: community.broadcom.com/symantecenterprise/communities/community-home/digestviewer?communitykey="9eac1757-c53a-4efc-aac8-d63ff93fd247">
    > Post New Message <broadcom-patchmanagementsolution@connectedcommunity.org>
    > Re: Migration to new version of Symantec Patch Management datafeed
    > <https: community.broadcom.com/symantecenterprise/discussion/migration-to-new-version-of-symantec-patch-management-datafeed#bmea5fc586-ce2d-40f8-abc0-186cdd357283="">
    > Reply to Group
    > <broadcom_patchmanagementsolution_ea5fc586-ce2d-40f8-abc0-186cdd357283@connectedcommunity.org?subject=re:+migration+to+new+version+of+symantec+patch+management+datafeed> Reply
    > to Sender
    > <https: community.broadcom.com/symantecenterprise/communities/all-discussions/postreply?messagekey="ea5fc586-ce2d-40f8-abc0-186cdd357283&ListKey=2e9b0b51-5ba5-498c-8e24-089d6ce9a3d7&SenderKey=a0456a89-ccb0-4599-b272-018e1cd8fa74">
    > [image: JaeHeung Kim]
    > <https: community.broadcom.com/network/members/profile?userkey="a0456a89-ccb0-4599-b272-018e1cd8fa74">
    > Apr 10, 2024 9:23 PM
    > JaeHeung Kim
    > <https: community.broadcom.com/network/members/profile?userkey="a0456a89-ccb0-4599-b272-018e1cd8fa74">
    > Dear, Dmitri
    >
    > This is Kim Jae Heung.
    >
    > I tested both 7_1 and 7_4 PMImport for the computer where the error occurs.
    > This does not occur equally on all systems.
    > However, once a system occurs, it continues to occur.
    > What I checked is that an error occurred when the STPatchAsession.xml file
    > was created. Please check below.
    >
    > Extracted from a.log
    >
    >
    > hostName='kittalt' source='BaseApplication::Run'
    > module='AeXPatchAssessmentU.exe' process='AeXPatchAssessmentU.exe'
    > pid='10372' thread='10748' tickCount='4710140' >
    >
    >
    >
    >
    > *
    > hostName='kittalt' source='Utils::ComException::ComException'
    > module='AeXPatchAssessmentU.exe' process='AeXPatchAssessmentU.exe'
    > pid='10372' thread='10748' tickCount='4710156' > MSG='Utils::Xml::StringToDocument()-
    > Couldn't load XML text']]>*
    >
    > hostName='kittalt' source='BaseApplication::Run'
    > module='AeXPatchAssessmentU.exe' process='AeXPatchAssessmentU.exe'
    > pid='10372' thread='10748' tickCount='4710156' >
    >
    >
    >
    > hostName='kittalt' source='BaseApplication::Run'
    > module='AeXPatchAssessmentU.exe' process='AeXPatchAssessmentU.exe'
    > pid='10372' thread='10748' tickCount='4710171' >
    > load XML text (0x80004005)]]>
    >
    >
    > hostName='kittalt' source='CAuxilliaryPackage' module='PatchMgmtAgents.dll'
    > process='AeXNSAgent.exe' pid='1040' thread='9300' tickCount='4710515' >
    >
    >
    >
    > hostName='kittalt' source='AssessmentTool' module='PatchMgmtAgents.dll'
    > process='AeXNSAgent.exe' pid='1040' thread='9300' tickCount='4710515' >
    >
    >
    >
    > *
    > hostName='kittalt' source='AeXPatchUtil' module='AeXPatchUtil.exe'
    > process='AeXPatchUtil.exe' pid='8700' thread='10656' tickCount='4710515' >
    > *
    >
    > Extracted from *STPatchAssessment.xml *
    > If it's a normal(no error) STPatchAssessement.xml file is
    >
    > at the
    > end of this.
    >
    > But, On the computer where the error occurs, it is created as follows.
    >
    >
    > Error 2: at the end of this.
    >
    > This means that the xml file was created and suddenly interrupted.
    >
    > I changed it to 7_3 and tested it.
    > You changed to PMimport 7_3, ran the import again, performed a
    > configuration update on the client, downloaded the System Assistance files
    > again, and ran System Assistance.
    > The results are executed without errors. STPatchAsessment.xml is also
    > generated normally.
    >
    > Thank you & Best regards.
    > Kim Jae Heung
    >
    >
    >
    >
    >
    > 2024년 4월 9일 (화) 오후 9:54, Dmitri Gornev via Broadcom 님이
    > 작성:
    >
    > > Hi JaeHeung, may you share the following artifacts? 1. Contents of the
    > > assessment package (C:\Program Files\Altiris\Altiris Agent\Agents...
    > > -posted to the "Patch Management Solution" community
    > > [image: Broadcom]
    > > Patch Management Solution
    > >
    > > Post New Message
    > > Re: Migration to new version of Symantec Patch Management datafeed
    > >
    > > Reply to Group
    > > Reply
    > > to Sender
    > >
    > > [image: Dmitri Gornev]
    > >
    > > Apr 9, 2024 8:54 AM
    > > Dmitri Gornev
    > >
    > >
    > > Hi JaeHeung,
    > >
    > > may you share the following artifacts?
    > >
    > > 1. Contents of the assessment package (C:\Program Files\Altiris\Altiris
    > > Agent\Agents\SoftwareManagement\Software Delivery\{6D417916-467C-46A7-
    > > A870-6D86D9345B61}\cache) without WindowsPatchData.zip file from
    > > problematic machine.
    > > 2. Verbose logs of the assessment utility:
    > > - enable verbose mode of the agent (see
    > > knowledge.broadcom.com/external/article/179702/...
    > <https: knowledge.broadcom.com/external/article/179702/how-to-configure-logging-on-the-notifica.html="">
    > > )
    > > - set registry key (DWORD) SOFTWARE\Altiris\Altiris Agent\Patch
    > > Management\Patch Assessment\LoggingLevel to 2bc (700)
    > > - click on 'Start assessment scan' button in the agent UI to start
    > > assessment scan and wait for it to finish.
    > > - collect agent logs
    > > 3. DPDTrace
    > >
    > > logs
    > >
    > > Thank you,
    > > Dmitri.
    > > *Reply to Group Online
    > > *
    > > *Reply to Group via Email
    > > *
    > > *View Thread
    > > *
    > > *Recommend
    > > *
    > > *Forward
    > > *
    > > *Flag as Inappropriate
    > > *
    > >
    > > -------------------------------------------
    > > Original Message:
    > > Sent: Apr 08, 2024 01:13 PM
    > > From: JaeHeung Kim
    > > Subject: Migration to new version of Symantec Patch Management datafeed
    > >
    > > After the Patch Assistance Tool version is upgraded, the Scan result
    > file,
    > > STPatchAsession.xml, is not generated successfully. The same result
    > occurs
    > > in both 7.1/7.4.
    > >
    > > Original Message:
    > > Sent: Mar 05, 2024 11:52 AM
    > > From: Dmitri Gornev
    > > Subject: Migration to new version of Symantec Patch Management datafeed
    > >
    > > Symantec Patch Management solution will migrate to a new version of patch
    > > datafeed (7.4) after March 2024 Patch Tuesday and we encourage you to
    > > verify its functionality using Beta datafeed URL.
    > >
    > > To participate in Beta:
    > >
    > > In the *Import Patch Data for Windows* task, open the General section
    > > Click Edit on the *Import patch data from the custom location:* line
    > > Select the second radio button for *Custom location* and paste in this
    > > URL, www.solutionsam.com/imports/7_4/patch/windows/...
    > >
    > > Leave the default of *No Authorization* and click OK
    > > Click *Save changes*.
    > > Depending on your version of OS and Patch Management solution you may get
    > > "The Alternative Location field appears to be invalid" error.
    > > Just click "Save changes" again to retry - newer TLS version will be
    > > automatically attempted to access datafeed and the new import URL will be
    > > saved successfully.
    > >
    > > The main focus of this exercise is the execution of the assessment and
    > > installation of updates (there are no changes to content imported on the
    > > server side). New datafeed includes changes to the assessment and
    > > deployment tools, the way how they integrate with each other and process
    > > the assessment results.
    > >
    > > Please note that the following operating systems will no longer be
    > > supported with the new datafeed version:
    > > Windows XP
    > > Windows Vista
    > > Windows Server 2003
    > > Windows Server 2003 R2
    > > Windows Server 2008
    > >
    > > We will provide additional notification when 7.4 datafeed will be
    > promoted
    > > to production (it will re-use the same default URL
    > > www.solutionsam.com/imports/7_1/patch/windows/...
    > >
    > > Fallback 7.3 datafeed URL will be provided in parallel for a period of
    > > time.
    > >
    > > We would like to thank you for your attention and feedback.
    > >
    > >
    > >
    > >
    > > You are subscribed to "Patch Management Solution" as kimjh@kitt.co.kr.
    > To
    > > change your subscriptions, go to My Subscriptions
    > > . To
    > > unsubscribe from this community discussion, go to Unsubscribe
    > > .
    > >
    > >
    > > Copyright © 2005-2023 Broadcom. All Rights Reserved. The term "Broadcom"
    > > refers to Broadcom Inc. and/or its subsidiaries.
    > >
    > > Hosted by Higher Logic, LLC on the behalf of Broadcom - Privacy Policy
    > > | Cookie Policy
    > > | Supply Chain Transparency
    > >
    > > | Terms of Use
    > >
    >
    > --
    >
    >
    > **KITT* - System Consulting, S/W Solution, Rental & Maintenance, Network
    > & Security*
    >
    > *Reply to Group Online
    > <https: community.broadcom.com/symantecenterprise/communities/all-discussions/postreply?messagekey="ea5fc586-ce2d-40f8-abc0-186cdd357283&ListKey=2e9b0b51-5ba5-498c-8e24-089d6ce9a3d7">*
    > *Reply to Group via Email
    > <broadcom_patchmanagementsolution_ea5fc586-ce2d-40f8-abc0-186cdd357283@connectedcommunity.org?subject=re:+migration+to+new+version+of+symantec+patch+management+datafeed>*
    > *View Thread
    > <https: community.broadcom.com/symantecenterprise/discussion/migration-to-new-version-of-symantec-patch-management-datafeed#bmea5fc586-ce2d-40f8-abc0-186cdd357283="">*
    > *Recommend
    > <https: community.broadcom.com:443/symantecenterprise/discussion/migration-to-new-version-of-symantec-patch-management-datafeed?messagekey="ea5fc586-ce2d-40f8-abc0-186cdd357283&cmd=rate&cmdarg=add#bmea5fc586-ce2d-40f8-abc0-186cdd357283">*
    > *Forward
    > <https: community.broadcom.com/symantecenterprise/communities/all-discussions/forwardmessages?messagekey="ea5fc586-ce2d-40f8-abc0-186cdd357283&ListKey=2e9b0b51-5ba5-498c-8e24-089d6ce9a3d7">*
    > *Flag as Inappropriate
    > <https: community.broadcom.com/symantecenterprise/discussion/migration-to-new-version-of-symantec-patch-management-datafeed?markappropriate="ea5fc586-ce2d-40f8-abc0-186cdd357283#bmea5fc586-ce2d-40f8-abc0-186cdd357283">*
    >
    > -------------------------------------------
    > Original Message:
    > Sent: 4/9/2024 8:54:00 AM
    > From: Dmitri Gornev
    > Subject: RE: Migration to new version of Symantec Patch Management datafeed
    >
    > Hi JaeHeung,
    >
    > may you share the following artifacts?
    >
    > 1. Contents of the assessment package (C:\Program Files\Altiris\Altiris
    > Agent\Agents\SoftwareManagement\Software Delivery\{6D417916-467C-46A7-
    > A870-6D86D9345B61}\cache) without WindowsPatchData.zip file from
    > problematic machine.
    > 2. Verbose logs of the assessment utility:
    > - enable verbose mode of the agent (see
    > https://knowledge.broadcom.com/external/article/179702/how-to-configure-logging-on-the-notifica.html
    > )
    > - set registry key (DWORD) SOFTWARE\Altiris\Altiris Agent\Patch
    > Management\Patch Assessment\LoggingLevel to 2bc (700)
    > - click on 'Start assessment scan' button in the agent UI to start
    > assessment scan and wait for it to finish.
    > - collect agent logs
    > 3. DPDTrace
    > <https: forums.ivanti.com/s/article/dpdtrace-gui-tool-used-to-troubleshoot-patch-detection-issues?language="en_US">
    > logs
    >
    > Thank you,
    > Dmitri.
    >
    >
    >
    >
    > You are subscribed to "Patch Management Solution" as kimjh@kitt.co.kr. To
    > change your subscriptions, go to My Subscriptions
    > <http: community.broadcom.com/preferences?section="Subscriptions">. To
    > unsubscribe from this community discussion, go to Unsubscribe
    > <http: community.broadcom.com/higherlogic/egroups/unsubscribe.aspx?userkey="a0456a89-ccb0-4599-b272-018e1cd8fa74&sKey=KeyRemoved&GroupKey=2e9b0b51-5ba5-498c-8e24-089d6ce9a3d7">.
    >
    >
    > Copyright © 2005-2023 Broadcom. All Rights Reserved. The term "Broadcom"
    > refers to Broadcom Inc. and/or its subsidiaries.
    >
    > Hosted by Higher Logic, LLC on the behalf of Broadcom - Privacy Policy
    > <https: www.broadcom.com/company/legal/privacy-policy=""> | Cookie Policy
    > <https: www.higherlogic.com/legal/privacy=""> | Supply Chain Transparency
    > <https: www.broadcom.com/company/citizenship/governance-and-ethics#supply="">
    > | Terms of Use <http: termsandconditions="">
    >

    --


    **KITT* - System Consulting, S/W Solution, Rental & Maintenance, Network
    & Security*




  • 7.  RE: Migration to new version of Symantec Patch Management datafeed

    Broadcom Employee
    Posted 2 days ago

    Hi JaeHeung,

    may you attach the files themselves?

    Do you see any difference in endpoints that experience the issue vs. other endpoints (OS version, language, software installed, etc.)?

    Thank you,
    Dmitri.




  • 8.  RE: Migration to new version of Symantec Patch Management datafeed

    Broadcom Employee
    Posted 2 days ago
      |   view attached

    Hi JaeHeung,

    we prepared a debug version of assessment tool that should identify what exact XML was not processed properly ('Utils::Xml::StringToDocument()- Couldn't load XML text') when generating the output file. Please find AeXPatchAssessmentU.exe attached to this message (in Zip archive).

    How to steps:

    1) replace AeXPatchAssessmentU.exe with the test version of the utility in the package folder C:\Program Files\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery\{6D417916-467C-46A7-A870-6D86D9345B61}\cache
    2) collect verbose logging of assessment
    - set registry key (DWORD) SOFTWARE\Altiris\Altiris Agent\Patch Management\Patch Assessment\LoggingLevel to 2bc (700)
    - run AeXPatchAssessment.exe manually from the package folder (not AeXPatchAssessmentU.exe) and wait for it to finish.
    - collect agent's logs


    Thank you,
    Dmitri.


    Attachment(s)

    zip
    AeXPatchAssessmentU.zip   649 KB 1 version