Client Management Suite

 View Only
  • 1.  Altiris Managed Software

    Posted Jul 06, 2012 04:53 PM

    I need a pointer to some How-to's or samples. I just completed the on-line Altiris training and I'm trying to 'Set it and forget it!'.

    I'm starting with an opensource application we use called PDFCreator.

    Newly discovered/undefined software shows: 10 versions. 0.8.0, 0.9.2, 0.9.3, ..., 1.2.2.

    Managed software shows: PDFCreator 1.2.3 (company pdfforge GbR), 1.2.3 (company Frank ...), 1.4.0 (company Frank ...), 1.4.1 (company Frank ...).

    Metered Software, Usage Tracking shows: PDFCreator 1.4.0 (Company pdfforge GbR).

    Deliverable Software Software releases shows: PDFCreator 1.2.3 (pdfforge GbR), 1.4.0 (pdfforge Gbr) and 1.4.1 (pdfforge GbR0

    We had a task to install PDFCreator 1.2.3.

    I downloaded and created a software package for 1.4.0. I told it to supersede all other releases.

    I noticed there was a 1.4.1 release. I downloaded it. Created a software package and installed it on one PC.

    How do I resolve the Company? pdfforge GbR vs Frank Heindorfer, Philip Chinery. Have the same problem with WinZip, the Company name has changed 4 or 5 times.

    How do I associate programs so I can meter? Should I install the application on a PC before I create the package, run software inventory and then move from newly discoverd to managed?

    There is more, but I'll be happy to figure out this part.

     

    P.S. This is my first post, so if I'm doing something wrong please point me in the right direction.

     

    Bob Stein

     

     



  • 2.  RE: Altiris Managed Software

    Posted Jul 07, 2012 05:35 AM

    It's best to meter using the Software Product instead of a separate metering policy.

    Don't worry too much about the "Company" - you can merge Company names, search for "merge" in the console. Personally, I'd do it for "Adobe Systems" and "Adobe Systems ltd" but not totally different names like you have. I'd welcome comments from others about that.

    "Supersede" figures in two places, in the "Associations tab of the deliverable Software Release and the "Automatically upgrade superseded..." option in Managed Software Delivery Policies. The Associations tab info is what the Policy uses but there has to be an uninstall Command Line (and Software Package if required by the command line) for the Superseded Software Release.

    If you create a Software Product for PDF creator don't be too prescriptive about the criteria. You can use the pipe symbol '|' as an or for the Company but I wouldn't bother putting anything in the "Company" field, just "PDFCreator" for name and '1.' in the "Version" filter. You don't need to this time but I always check in Manage > Software Catalog and check the box to show all software products  to make sure there isn't one already that my custom named Deliverable Software Release hasn't matched with, we use "APP_" prefix on all the Deliverable Softwrae we create.

    You should make sure that there is only one PDFCreator Software Release at 1.4.1, use Actions > Resolve Duplicate Software Resources if there are more than one. My preference is to merge the one I've created into the discovered one - you'll have to remove your created one from any policies first. Better still, when you import the Software to create a Deliverable Software Resource, malke sure you check for a dicoverd resource first and "Update existing".

    I think it's a good idea to test your unattend install on a test box then run Full Inventory to make sure it is discoverd and you have a (discovered) Software Release to update when you import.