Loading
Skip Feed
  1. Release notification: Enhanced application and computer reporting

     

    We are pleased to introduce enhancements to the Applications per computer and user and Applications per computer reports in Snow Atlas, providing greater flexibility and more detailed information for reporting and analysis. The enhancements include:

     

    1. More detailed application version information: The application Full version is now available as an optional report column in both reports, helping customers identify installed application versions more precisely for reporting and compliance analysis.
    2. More reliable computer identification: The Computer GUID is now available as an optional report column in both reports, providing a unique identifier to reliably correlate software records with computer and organizational data, even when computer names are not unique.

     

    Summary:

    Release domain: SAM on Snow Atlas

    Release tier: Minor release

    Release date: 13 November 2026

    Expand Post

  2. Flexera's Snow Atlas Office Hours (Topic: Using Your Data – Reporting Best Practices) Tuesday, November 17th.

    Hello, join us to get more value from Snow Atlas with a monthly, hands-on session designed around the topics that matter most to your team.

    Hosted by our SMEs, these sessions are built to help you accelerate time to value, adopt new features, and solve your toughest use cases alongside peers. Each session is 30 minutes of focused training followed by 30 minutes of open Q&A and discussion. Giving you the opportunity to learn best practices and get your real-world questions answered in the same hour.

    For this call, our topic is Using Your Data – Reporting Best Practices. Now that your data is healthy, your entitlements are in and you understand your license position, we'll show you how to put that data to work. We'll cover choosing the right reports, building a regular reporting rhythm with scheduled reports, flagging licenses and agreements that expire in the next 90, 60 or 30 days, sending reports to people outside Snow Atlas, delivering reports to SharePoint to feed Power BI dashboards, and sharing reports (that you have set criteria and customised with filters) with colleagues.

    Please share with your colleagues if they are interested in joining.

    Tuesday, November 17th at 10:00am ET / 3:00pm GMT

    This session will focus on Using Your Data – Reporting Best Practices. Click the link attached to add the meeting to your calendar.

    What to expect

    • 60 minutes — 30 min training, 30 min live Q&A and open discussion
    • Led by Snow Atlas experts — practical guidance, not slideware
    • Bring your questions — real answers to real-world reporting, configuration, and optimization challenges
    • Exclusively for Snow Atlas customers — hosted live on Microsoft Teams

    Why attend

    • Faster time to value from the features you're already paying for
    • Direct access to product and services experts in a live, interactive format
    • Practical, repeatable best practices you can apply immediately
    • A touchpoint with the Snow Atlas team

    Any questions, please ask here or email Nancy at Nabercrombie@flexera.com.

    Expand Post

  3. Has anyone had problems with scheduled reports not sending via email?
    Question with a best answer.

    Best Answer

    Yes, due to one past SLM update (i dont remember which) we had that problem. I guess the update of password field changes did delete old setting. What is your SLM version?

     

    Solution a) was to enter the SMTP data in SMACC again.

     

    https://docs.flexera.com/release-notes/on-premises/snow-license-manager/snow-license-manager-26/#slm26-2-0

     

    image 

    Alternative solution or rootcause b) can be, that your SMTP switched to another authentications. If a) does not resolve check you SMTP or set another SMTP server for testing purpose.

     

    Resolved?

     

    BW

    Björn

    Expand Post

    1 of 3

  4. Reporting on applications marked as uninstalled (UI)

    We have carried out a clean-up exercise and uninstalled a specific application, such as Docker, from several PCs. We now need a report to document these removals.

    When viewing an individual PC in Snow Atlas, I can see “UI” in the application’s remark field, indicating that it has been uninstalled. However, I cannot find how to report on this field across all PCs.

    Is there a way to create a report listing all PCs where a specific application has “UI” in the remark field? Ideally, we would also like to include the uninstall date, if available.

     

    Thank you in advance for your help on which report or filters to use .

    Expand Post

    1 of 2
    • Andy Mason (Flexera Software)

      Hi cschuermans,

       

      As MicBoo has stated the "Application installation history" could help, the other alternative is to use the ""Applications per computer" report and put the criteria of the applications you are focused on. From here you choose from the filter "Installed" and set that to No - This will show any instances that have had usage reported within a set time period (30,60,90 days customisable by your own environment) but does not have installation files or .exe physically on the machine.

       

      image 

      Hopefully this helps.

       

      Also in regards to reporting we have a Snow Atlas Office Hours set for next Tuesday 17th November at 3pm UTC - We will be focusing on best practise advise around reports available within Snow Atlas and how to get the most from them. This will also have a section at the end where you can ask questions directly to our inhouse SMEs - If you feel that maybe of interest please find the link to the meeting invite in this post - https://community.flexera.com/s/feed/0D5PL000010cdXt0AI

       

       

       

      Expand Post

    • Andy Mason (Flexera Software)

      Hi Ivan,

       

      As this is working for some users and not all on your environment, best advise i could give would be for you to raise a support ticket - https://community.flexera.com/s/support-hub - so they can check the difference between the Adobe Admin Console and what is being reported via the connector.

       

      You may want to log onto your SIM (Snow Integration Manager) and check the connection is still bringing in live data.

       

      Also confirming if this is reflecting in Atlas or Snow License Manager as different resolutions maybe needed.

       

      I ask that once you have raised the call, you send the ticket number to "engage@flexera.com" and myself or one of my colleagues in Digital Customer Success will reach out to you to ensure you get to a resolution and also see where we can also help you with getting full value from the solutions.

      Expand Post

  5. We are using Snow Atlas for Asset management, and we have one machine that shows as active but has not scanned since 10/12/2025 and also still shows Ver 7.0.0 when we are currently pushing out 26.1.1 via company portal.

    Nothing seems to bring the machine up to date. We did test the connection to the server from the machine and that tested okay. Any Ideas as to why it would not be talking back to the server would be welcomed

    Thankyou

    Adam


    • Andy Mason (Flexera Software)

      Hi Adam,

       

      As this is a unique machine on your environment, best advise i could give would be for you to raise a support ticket - https://community.flexera.com/s/support-hub - so the team can look into the snowpack file and the agent and find if something isn't being actioned from the data.

       

      One thing to check though, if you go to the machine record and choose edit - is the "Disable auto editing" option ticked as this can sometime be switch on and stop the quarantine process from actioning (Used for situations like Maternity leave so machines aren't automatically archived or deleted).

       

      image 

      Expand Post

  6. MercedesO (Flexera Software) asked a question.

    💬 Community question: As AI adoption grows, what are you doing to maintain visibility over usage and licensing?

    Thank you @SamuelBaughan​  for sharing your experience and insights in our latest Community Voices feature! Samuel raises a valid point about maintaining visibility as AI adoption grows. I'm curious to hear from others in the Snow Atlas and Snow License Manager community, how are you approaching visibility over AI usage and licensing? Are you seeing similar challenges?

    You can read Samuel's Community Voices profile here


  7. Finding vulnerable components with SLM and SAM Core – guidance document

     

    With PHP2Shell (CVE-2026-109618 / CVE-2026-109619) and Broccoli2Shell (CVE-2026-111497) published within days of each other, many of you have asked how to use Snow License Manager and SAM Core to find affected devices. The attached document walks through it.

     

    It covers:

    • How to work out what a vulnerable component looks like on disk, and which products bundle or embed it

    • Installed software versus file evidence, and why file evidence often finds the copies you didn't know about

    • Step by step: finding recognised applications, then using the Files per computer report to get exact versions and paths

    • What the standard inventory does not see (DLLs, shared libraries, non-default folders, statically linked code, language packages, containers) and how to close those gaps

    • A checklist you can reuse for the next vulnerability

     

    PHP2Shell and Broccoli2Shell are used as worked examples, but the document is meant as general guidance for detecting future vulnerabilities of this kind.

     

    Please note: the guidance is based on a standard setup with the default inventory agent configuration. If you have changed your agent configurations (for example scan paths or file types) or the settings that control which file extensions are transferred to the frontend, your results may differ from what is described: you may see more files, or fewer.

     

    Always check the latest vendor advisories for fixed versions before acting.

     

    Questions and feedback are welcome in the comments.

    Expand Post

    Max_Schoenhuber and MercedesO like this.

End of Feed
End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
Unanswered Questions
Skip Feed
  1. MercedesO (Flexera Software) asked a question.

    💬 Community question: As AI adoption grows, what are you doing to maintain visibility over usage and licensing?

    Thank you @SamuelBaughan​  for sharing your experience and insights in our latest Community Voices feature! Samuel raises a valid point about maintaining visibility as AI adoption grows. I'm curious to hear from others in the Snow Atlas and Snow License Manager community, how are you approaching visibility over AI usage and licensing? Are you seeing similar challenges?

    You can read Samuel's Community Voices profile here


  2. Has anyone tried the ai ingestion feature with bulk uploads? Is there a way to manage name differences on invoices effectively?

    Using the ingest feature to migrate licences to Snow Atlas. The names on the Invoices very often don't match to the names in Flexera, assuming it has something to do with this. (an AI Normalization Agent automatically suggests application names and SKUs based on data from Technopedia). This is resulting in a heavy requirement for manual fixing to enable the ingest to process, this is rendering a cool function, less useful than manual upload.

     

    Any tips?


  3. Offline installer for SLM 26.2 & 26.3

    When I try to run Snow Update service on our single Snow server that is hosting SLM, SIM & Inventory Server, it fails and the error details make it look like it's trying to downgrade the database? Anyone have any offline installers (for Internet restricted server) for SLM 26.2 & 26.3? When I go to the website & click on "Latest Version" it downloads SnowLicenseManagerSetup_9.32.0 instead.

     

    image


  4. Report full computer name instead of Hostname

    We are using Snow License Manager on-prem Version 26.3 Build 9732 with the snow inventory agent 7 insatalled on Windows 2016+ servers and Linux Servers. We noticed that the 'Computer Name' column in the inventory is reported as the HostName . For example if the computer DNS name is systemA.lab.net it's reported as systemA.

     

    Q: How can we get it to show the full computer name including domain?


  5. Domain Name Inventory Inconsistencies

    We are using Snow License Manager on-prem Version 26.3 Build 9732 with the snow inventory agent 7 insatalled on Windows 2016+ servers and Linux Servers. We noticed that the domain name is reported as the domain ShortName (down-level domain name) on Windows whereas on Linux the FQDN of the domain is reported. For example if the domain is lab.net on Linux it's reported as lab.net but on windows as LAB.

     

    Q: How can we get Windows to report the FQDN of the domain it's joined to?

     


  6. Why does my DataExplorer backup give me an unhandled exception during Snow Inventory upgrade?

    I cannot run the Snow Inventory Data Explorer (a prompt from the Snow Inventory installer) to export all my computers from Snow (to back it all up prior to an upgrade) while I'm trying to upgrade Snow Inventory Server from v6 to v25.1.

     

    When I run the installer it asks for the SQL db connections (which I think are correct because I can login to SQL from that machine as that account) but it gives me an unhandled exception error saying it invalid object name 'client' (see exception below) and then just crashes. I couldn't find any logs in Event Viewer nor any for DataExplorer under C:\Program Files\Snow Software\Logs\ directory.

     

    I'm upgrading the following components versions below, is there any way to get this data backed up without having ot go through the DataExplorer backup process? Any assistance would be greatly appreciated, thanks in advance!

    Inventory 6 -> 25.1

    LicenseMgr 9 -> 26.1

    Integration 6.3 -> 26.2

     

     

     

    Unhandled Exception (truncated):

     

    ************** Exception Text **************

    System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'Client'.

      at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

      at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

      at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

      at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()

      at System.Data.SqlClient.SqlDataReader.get_MetaData()

      at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)

      at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)

      at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)

      at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)

      at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)

      at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)

      at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)

      at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)

      at SnowSoftware.DB.DataFactory.ExecuteSPDataSet(String StoreProcName, String[] ParamNames, String[] ParamValues) in c:\Development\Snow Data Transfer\Source\DataFactory.cs:line 37

      at SnowSoftware.SnowDataTransfer.TransferManager.GetComputerList(String connectionString, String siteName, String computerName) in c:\Development\Snow Data Transfer\Source\TransferManager.cs:line 43

      at SnowSoftware.SnowDataTransfer.frmMain._btnTransfer_Click(Object sender, EventArgs e) in c:\Development\Snow Data Transfer\Source\frmMain.cs:line 218

      at System.Windows.Forms.Control.OnClick(EventArgs e)

      at System.Windows.Forms.Button.OnClick(EventArgs e)

      at System.Windows.Forms.Button.WndProc(Message& m)

      at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    ClientConnectionId:400a19c0-0677-44cc-a603-4c153db35a40

    Error Number:208,State:1,Class:16

    Expand Post

End of Feed
End of Feed
8 Chatter Feed Items
Loading
Snow License Manager | Flexera Community