Symantec Management Platform (Notification Server)

 View Only
  • 1.  Modifying Discovered Software Resources

    Posted Jul 11, 2014 06:21 PM

    I currently have a piece of agent based software I deployed with a managed software policy that is version 1.0 A push from the software's server was made to upgrade it to version 1.2. Both of these versions have different GUIDs. Because the detection rule uses GUID1.0, when the software is updated to 1.2 I get the managed software policy constantly re-installing software vesion 1.0. I believe I have corrected this by setting up the discovered resource for 1.2 as a '"Supersedes" Association for the 1.0 software resource. On the managed deliever policy for 1.0 I checked "Do not install if a newer version of this software is already installed". It also warns me a newer version 1.2 exists.

    Confusing yet?

    It appears everything is working but when my pre-download detection checks for 1.2 it still says "Not Detected". I would like to troubleshoot the Discovered resource for 1.2 to check the metadata and confirm the GUID. How do I do this? The software resource doesn't show up in any format under the software catalog, nor does it show up under All Resources when I search there. I do not have the installer for the 1.2 software so I can't import my own software resource to the catalog. I need to work from the discovered one. These discovered ones must live outside the software catalog?!?



  • 2.  RE: Modifying Discovered Software Resources

    Posted Jul 12, 2014 05:15 AM

    You should be able to find the Discovered resource under Manage > Software > Newly discovered...

    But it probably won't have the MSI GUID. I'd right-click > Assign type > Software Release and then add the MSI GUID as a Detection Check.

    If you look in the Inventory of a PC with the v1.2 software it should show the Software with a column showing a number indicating how it was discovered, there's a KB article listing the discovery sources somewhere but I'm afraid i can't find it at the moment. How the software is discovered is considered proprietary info AFAIK.
     



  • 3.  RE: Modifying Discovered Software Resources

    Posted Jul 14, 2014 03:03 PM

    That's the puzzling part to me. It doesn't exist under "Newly Discovered Sofware" but when I edit any software resource it is available to add as a "Software Component". My issue is it is not being detected in the pre-download detection.

     

    MCF.png



  • 4.  RE: Modifying Discovered Software Resources

    Posted Jul 14, 2014 05:01 PM

    I just found it under the root of the software components as opposed to releases. That must be the difference. From there I could right click and edit the resource, so now it has a GUID associated with it. Thank you for leading me down the right path.

    MCF2.png

    EDIT: with the detection rule added for the newer resource, the managed job is now working as expected.



  • 5.  RE: Modifying Discovered Software Resources
    Best Answer

    Posted Jul 15, 2014 08:03 AM

    You can right-click > Actions > Assign Type > Software Release. Not sure why it wasn't under newly discovered (Edit: unless you have a Software Product that contains it).
     



  • 6.  RE: Modifying Discovered Software Resources

    Posted Jul 15, 2014 01:07 PM

    That was exactly it. There was a software product with a generic version so it was getting grouped into that. I have corrected this and now it is under 'newly discovered'. Thank you very much.

    EDIT: I also didn't realize it could be done from the view under Settings > Notification Server > Console Settings > Software > Software Catalog . This might be a little easier than doing it through the "All resources" like I was previously.



  • 7.  RE: Modifying Discovered Software Resources

    Posted Jul 16, 2014 08:51 AM

    This is the view that everyone used before the Silverlight Enhanced Console Views/Activity Center came along. It does make it easier to find Software Resources that have been discovered in your organisation but not assigned a type specifically.