United Kingdom Endpoint Management User Group

 View Only

How to correct the DS 7.5 HF6 latest plugin version filters, so that they will allow machines to upgrade to the HF6 version? 

May 27, 2014 12:45 PM

After installing DS 7.5 HF6, you will notice the following:

"path\Altiris\Notification Server\NSCap\bin\Win32\X86\Deployment\Agent\Symantec_DeploymentSolutionAgent_7_5_x64.msi"

and

"path\Altiris\Notification Server\NSCap\bin\Win64\X64\Deployment\Agent\Symantec_DeploymentSolutionAgent_7_5_x64.msi"

both have a version of 7.5.1603.0

 

The "Computers with latest Deployment Plug-in installed on Windows", "Computers with latest Deployment Plug-in installed on Windows (x64)" & "Computers with latest Deployment Plug-in installed on Windows (x86)"  filters look for:-  t1.[Product Version] >= '7.5.1602'

--/Computers with latest Deployment Plug-in installed on Windows:
            SELECT Guid FROM vRM_Computer
            WHERE Guid in
            (select  t1._ResourceGuid from Inv_AeX_AC_Client_Agent t1
             INNER JOIN  vRM_Computer r
             ON r.Guid=t1.[_ResourceGuid]
             INNER JOIN Inv_AeX_AC_Identification AI
             ON AI._ResourceGuid = r.Guid
             AND ( UPPER(t1.[Agent Name]) = UPPER('Altiris Deployment Agent')
          OR UPPER(t1.[Agent Name]) = UPPER('Deployment Solution Plug-in') )
             AND UPPER(AI.[OS Name]) LIKE UPPER('%Windows%')
             AND t1.[Product Version] >= '7.5.1603' )

--/Computers with latest Deployment Plug-in installed on Windows (x64):
            SELECT Guid FROM vRM_Computer
            WHERE Guid in
            (select t1._ResourceGuid from vRM_Computer r
            INNER JOIN Inv_AeX_AC_Client_Agent i
            ON i._ResourceGuid=r.Guid  
              INNER JOIN Inv_AeX_AC_Identification a
   ON r.Guid = a.[_ResourceGuid]    
   INNER JOIN Inv_AeX_AC_Client_Agent t1
   ON r.Guid=t1.[_ResourceGuid]
         AND ( UPPER(t1.[Agent Name]) = UPPER('Altiris Deployment Agent')
         OR UPPER(t1.[Agent Name]) = UPPER('Deployment Solution Plug-in') )
            AND UPPER(a.[OS Name]) LIKE UPPER('%Windows%')
             AND (UPPER(i.[Agent Name]) = UPPER('Altiris Agent')) AND (i.[64 Bit] ='1' )         
            AND t1.[Product Version] >= '7.5.1603')

--/Computers with latest Deployment Plug-in installed on Windows (x86):
           SELECT Guid FROM vRM_Computer
            WHERE Guid in
            (
            SELECT r.Guid FROM  vRM_Computer r
            INNER JOIN Inv_AeX_AC_Client_Agent ic
            ON ic._ResourceGuid=r.Guid  
            INNER JOIN Inv_AeX_AC_Identification a
   ON r.Guid = a.[_ResourceGuid]    
   INNER JOIN Inv_AeX_AC_Client_Agent t1
   ON r.Guid=t1.[_ResourceGuid]
            AND ( UPPER(t1.[Agent Name]) = UPPER('Altiris Deployment Agent')
         OR UPPER(t1.[Agent Name]) = UPPER('Deployment Solution Plug-in') )
            AND UPPER(a.[OS Name]) LIKE UPPER('%Windows%')           
            AND (t1.[Product Version] >= '7.5.1603')
            AND (UPPER(ic.[Agent Name]) = UPPER('Altiris Agent') AND (ic.[64 Bit] ='0' or ic.[64 Bit] is null))         
            )

 

 

 

This oversite obviously prevents existing DS plugin resources from upgrading to the HF6 version.

 

 

There are three ways to correct this: 

1.  Clone and then edit the existing filters, and then modify the upgrade policies to use the correct filters. 

2.  Export the existing filters, edit them via an XML Editor, and then reimport them. 

3.  Update the filter SQL definitions directly via the database. 

 

 

Methods:

Option 1 does not need any further help.

Option 2 is easy too; however, I have attached my modified XML files that can be imported for your convenience (importing them will replace the existing ones and retain their non-editable state). 

Option 3 is most likely not supported as it requires running an UPDATE command against the Item tables State column associated with those three filters.

 

Statistics
0 Favorited
0 Views
1 Files
0 Shares
0 Downloads
Attachment(s)
7z file
DS 7.5 HF6 corrected filters.7z   2 KB   1 version
Uploaded - Mar 11, 2020

Tags and Keywords

Comments

Jun 06, 2014 04:55 PM

Seeing as the plugins version have changed in SP1 (7.5.3219) this appears to not be an issue in SP1 for those that are interested.

May 29, 2014 01:11 PM

NP.  Everyday is a learning day...

May 29, 2014 01:07 PM

Thank you, I did figure out what I was doing wrong.

May 29, 2014 01:05 PM

Right-click the folder where the filters reside in, and then choose the import option.

This is how you import xml within the console.

You could also use the ImportExportUtil.exe to import the xml files via command line.

May 29, 2014 12:34 PM

Can you explain how you imported you XML, when there is only an option to export????

May 28, 2014 01:04 PM

Yes and yes.

It's much easier to import the xml I have attached as they will overwrite the existing filters.

May 28, 2014 11:09 AM

With regards to Step 1. where you state to " Clone and then edit the existing filters, and then modify the upgrade policies to use the correct filters."  do you mean to modify the filters that include the offending filters in thier exclusion list to reference the 'newly modified' filters in the exclusion list instead of the 'upgrade policies'?

I think these are the three filters that need to have thier 'exclusions' section modified by removing the exsting 'filter exclusion' and add in the newly modified one created above.:

1. Computers requiring Deployment Plug-in upgrade on Windows

2. Computers requiring Deployment Plug-in upgrade on Windows (x86)

3. Computers requiring Deployment Plug-in upgrade on Windows (x64)

But in order to do that, you actualy have to clone those three filters in order to modify them.  THEN go into the policies to install/upgrade the DS plug-in and reference THOSE three new filters you created in the previous sentence.

Related Entries and Links

No Related Resource entered.