
ashwini.karigowda@valmetpartners.com asked a question.

ashwini.karigowda@valmetpartners.com asked a question.

shocko asked a question.
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?

shocko asked a question.
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?

mkrautler@tampaairport.com asked a question.
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

ashwini.karigowda@valmetpartners.com asked a question.

johmjosu asked a question.
Firsth time logon does not work. Can I create a new user in inventory and have that syncronised to splamanger database to get access?

Snow Product Releases Blog — Hameed Iqbal (Flexera Software)
Official release of Snow Integration Manager 26.3.0
We are pleased to announce the release of Snow Integration Manager 26.3.0
This release includes:
· Oracle Linux Virtualization Manager connector: Added a new connector for collecting inventory from OLVM environments into SAM on Snow Atlas and Snow License Manager.
· Discovery data from file connector: Added support for populating the DiscoveryDate field in discovery manifests.
· ServiceNow ITSM connectors: Added a configurable page size for computer data retrieval.
· ServiceNow ITSM connectors: Fixed OAuth authentication through connector-configured proxy servers.
· HCL BigFix connector: Fixed duplicate device identity attributes that could cause incorrect device merges.
· VMware vSphere connector: Fixed BIOS serial-number formatting for inventoried virtual machines.
· VMware vSphere connector: Fixed proxy configuration restoration after aggregation.
· BMC Discovery connector: Improved handling of software records with missing names.
· HCL BigFix connector: Fixed missing records when processing large paginated datasets.
· Microsoft Hyper-V connector: Fixed authentication for service accounts specified in UPN format.
· Red Hat OpenShift Virtualization connector: Corrected host and datacenter identity mapping.
· Snow XML connector: Improved processing of network adapter data without a MAC address.
· HCL BigFix connector: Improved validation of software-instance and software-metric inclusion rules.
Customer Impact:
Oracle Linux Virtualization Manager Connector
Before this release: Customers using Oracle Linux Virtualization Manager, including those transitioning from the legacy Oracle VM platform, did not have a supported SIM connector for collecting OLVM virtualization inventory into SAM on Snow Atlas or Snow License Manager. This resulted in limited visibility into OLVM-managed hosts, virtual machines, clusters, and their relationships, increasing reliance on manual collection or alternative approaches.
After this release: The new connector automatically collects inventory from OLVM environments through the OLVM API and imports OLVM-managed hosts, virtual machines, clusters, and their relationships into SAM Core on Snow Atlas and Snow License Manager. This expands virtualization inventory coverage, reduces reliance on manual processes, and helps customers transitioning from Oracle VM to OLVM maintain visibility across their virtualized environments to support license-compliance processes.
For configuration information, refer to the Oracle Linux VM connector user guide.
Discovery Data From File Connector
· The addition of the DiscoveryDate field provides a consistent discovery timestamp, improving metadata consistency and reliable processing across discovery sources.
ServiceNow ITSM Connectors
· The configurable page size improves computer-data retrieval reliability by allowing customers to adjust the number of records retrieved according to their environment and payload size.
· OAuth requests now use the proxy settings configured in the connector, supporting reliable ServiceNow authentication in environments that require proxy communication.
HCL BigFix Connector
· Corrected device identity mapping prevents distinct devices from being incorrectly merged, improving device identification and host-to-virtual-machine relationships.
· Improved pagination ensures complete processing of large datasets, reducing the risk of missing software inventory records.
· Improved filtering validation prevents inconsistent software-instance and software-metric selections, supporting more complete and reliable inventory data.
VMware vSphere Connector
· Preserving BIOS serial numbers exactly as reported by VMware vSphere improves consistency when comparing or combining data from multiple inventory sources.
· Correct restoration of proxy settings allows subsequent connector operations to use the appropriate network configuration without restarting Snow Integration Manager.
BMC Discovery Connector
· Filtering software records with missing names prevents malformed records from disrupting downstream processing while preserving valid software inventory data.
Microsoft Hyper-V Connector
· Correct handling of UPN-formatted service accounts supports successful authentication and data aggregation against remote SCVMM servers.
Red Hat OpenShift Virtualization Connector
· Corrected host and datacenter mapping improves the accuracy of reporting, grouping, and license allocation in Snow Atlas and Snow License Manager.
Snow XML Connector
· Allowing network adapter data without a MAC address aligns validation with the XML schema and improves XML data-processing reliability.
Release information
Product: Snow Integration Manager
Release Tier: Minor Release
Release Version: 26.3.0
Release Date: 2026-09-21
Release Availability: GA
Release Notes: SIM 26.3.0 Release Notes
Product Documentation: SIM Documentation, ITSM Documentation
Distribution method: Installer available for downloads here

Download link does not work:
https://community.flexera.com/s/article/Snow-Integration-Manager-Downloads
"Uh oh! We've hit a snag!"

carolai asked a question.
Meanwhile a lot of application license metrics are based on users.
In our environment we have many users, that work with several userID's. And in our environment that are valid userid's.
Unfortunately in Snow License Manager it is not possible to group several UserID's to one person, assign the license to that person and then all license requirements for the different userID's will be covered.
I am aware, that there are many ideas in Snow Ideas Board to cover that requirement, I also created an idea several years ago and voted for others.
Unfortunately it seems Snow is not able to provide a solution for this.
Does anybody have implemented a workaround for that ?
I would be really interested in new ideas.

Yes I also already voted for that, years ago 😒
The idea has enough votes, I think. Also a long time has gone by. Snow's Max Schönhuber already anwered 4 years ago, this is considered by Product management.
Because it still is not implemented, it unfortunately looks like Snow cannot implement that.
Meanwhile I think perhaps an additional field in a license could at least be used as workaround.
In any case we need 2 fields for quantity in a license, real license quantity and entitlement quantity.
That could be also used for Windows Server licenses, we always need to add the entitlement quantity (16), but cannot add the real license quantity ( 1 / 8)
That's why I already implemented a custom field to know the real license quantity, that helps for SA renewals.
In case of user licenses that perhaps could be used to add the real license quantity 1, and change entitlement quantity based on number of userid's of that user, so we can assign all userid's to that license and then compliance can be calculated correctly.
Yet for Visual Studio license assignments, I use a SQL script, that updates a custom field when a user has assigned a VS license and based on that custom field I use compliance exclusions. But this I can't do for all licenses with user metric, that why I asked for ideas.
But also @SamuelBaughan idea using powershell scripts or export/import could be helpful.

duwaynefink asked a question.
Just trying to understand the cadence of when Snow updates the SRS for us to download and update our environment.

Snow updates SRS rules on daily basis, normally in the evening
But you need a licensekey for SRS and enable software recognition updates in SUS
In SUS you also can see, when last SRS update was done.