Loading
How to add a fake local application to SLM

A customer would like to add 'fake' applications.

These do not have a registry key or executable. Their like functional applications.

They want to use it for budget calculations, manually connect computers/computers.

I read the SLM 8.3 SMACC document.

It talks about 'local applications' or 'commercial application' without registry keys or executable.

But i seem to miss where the description is how to set this up.

I already added an 'Application' in the recognition part via the SMACC without any rule, but that does not show up in the SLM Web UI.

Other applications with rules (registry key, executable) do show up and are discovered on computers. So that kind of local applications is working.

A pointer to the proper document will be helpful too.

Regards,

Marcel Rijsbergen


  • Siegfried Gammay (Flexera Software)

    Hi Marcel, did you start an application search with filter setting “also include not installed / used” parameter, see screenshot? Unfortunately my screenshot is from SLM 9.3.1, but with SLM 8 there is this kind of filter also available. Regards Siggi
  • Hi Marcel, I would recommend that you add "(Local)" at the end of every local application you add into SMACC. This helps you identify if a locally added application has later become recognised with rules and it also helps you search in the add license search box for the locally added application.  With regards to the application not appearing at all, double check in the SMACC tool that it was saved, sign out and back into the SLM web front and check that it still doesn't appear. I would then advise that if it hasn't still, wait until tomorrow after the DUJ has taken place as I have found that in past experiences, this has helped when I have deleted local applications.  Are you using the wildcard "%" to help with the search in the license search box? Kind regards, Aurora. 
    Expand Post
    • thx, used this recommendation, indeed easy to group items.
  • Hello, Can someone point me in the right direction on where the instructions are to "add an application", either local or "fake"? In addition to the original post I find this would be useful to be able add a "license" as a place to upload related docs. Or even in the case where a real application isn't being discovered yet for whatever reason, you could still upload docs like the POs and invoices for safekeeping until the actual App showed up. Then just edit the license to reflect the real application once it is discovered.  Sometimes there is a several week delay between purchases and installations of SW. Hence things get put on the backburner and forgotten. I hope this made sense :-)
    Expand Post
    • Hi Thomas, I totally agree with you. There are a few things you can do here.  You can add in the local application by logging into the Snow Management and Configuration Center (SMACC) and hitting the "New Application" button on the top left hand corner.  You will then be required to populate the name and select a manufacturer for the application. I would suggest always adding "(Local)" at the end of any application you create. This is so, if the SRS add this in the mean time, you will know which one was created by yourself and which one has been added globally.  Alternatively, if you do not have access to the SMACC tool, you can add in an incomplete license (the incomplete license setting must be enabled in the SMACC tool's configuration options to allow incomplete licenses to be added) and populate all of the information you have at hand and upload the documents you wish to. You can then go back and edit the license once the application has been recognised.  I hope this helps. Kind regards, Aurora. 
      Expand Post
      • Hi, Just be aware that when you create your own application, you can’t set downgrade paths and you can’t create bundles. So after Snow recognizes an installation, check if there is evidence (reg or exe file) in the smacc. If so let Snow create the application and remove your own. Also when you added the rule to your own application. It’s just that you can be sure that all the dowgrade path and bundles are correct. Espacialy when a customer upgrades to a newer version. Without correct downgrade paths the compliance of this application is always incorrect.  Grt. Michel
        Expand Post
      • Aurora, This is exactly what I was looking for. Since I don't have access to SMACC (yet anyway) the incomplete license solution should work just fine. Apparently we don't have this enabled since I have tried this and haven't been able to save it. I'll see about having our Admin change this setting.   Thanks!! 

Related  Product Forums


                     → Flexera One



                      → Snow Atlas



                      → FlexNet Manager



                      → Snow License Manager



                       → App Broker


       Need help finding an answer?


        Ask a Question →


Loading
How to add a fake local application to SLM