Snow standard edition

Using Snow, you can track license entitlements against usage in public cloud platforms to reduce audit risk. Snow License Manager automatically identifies unused cloud subscriptions and software installations so you can optimize license or subscription level, uninstall and harvest licenses. With immediate insight into total investment, compliance risk and overspend for either a single application or the whole product family, you can see license optimization opportunities and take action to reduce costs.

Download a complimentary copy of the guide for a detailed view of the SAM tools market, key use cases and more. Our team is standing by to discuss your requirements and deliver a demo of our industry-leading platform. True visibility to only pay for what you need. Contact Us. Request A Demo. Snow License Manager empowers you to reduce software costs and risks. Limited visibility of technology use drives waste and poor governance.

Incomplete visibility into technology usage across on-premises, cloud and mobile Wasted technology spend Unable to identify and manage risks Unable to effectively respond to compliance and governance audits.

Improve visibility to minimize compliance risks and reduce software costs. Complete visibility of assets across the enterprise Optimization of cloud-based software Simplified management of complex data center licensing Powerful contract, renewal and financial management. How It Works. Unlock a unified view of all assets. Snowsight , the next-generation SQL worksheet for advanced query development, data analysis, and visualization.

SnowCD , a command line diagnostic tool for identifying and fixing client connectivity issues. Programmatic interfaces for Python , Spark , Node. Snowpark , a library that provides an intuitive API for querying and processing data in a data pipeline.

Bulk unloading to delimited flat files and JSON files. Snowpipe for continuous micro-batch loading. Snowflake Connector for Kafka for loading data from Apache Kafka topics. Streams for tracking table changes. Tasks for scheduling the execution of SQL statements, often in conjunction with table streams. Database replication between Snowflake accounts within an organization to keep the database objects and stored data synchronized. Database failover and failback between Snowflake accounts for business continuity and disaster recovery.

As a data provider, securely share data with other accounts. As a data consumer, query data shared with your account by data providers.

Secure data sharing across regions and cloud platforms through data replication. Snowflake Data Marketplace , where providers and consumers meet to securely sharing data. Data Exchange , a private hub of administrators, providers, and consumers that you invite to securely collaborate around data.

Next Previous. Docs » Introduction to Snowflake » Snowflake Editions. Note The Snowflake Edition that your organization chooses determines the unit costs for the credits and the data storage you use. Other factors that impact unit costs are the region where your Snowflake account is located and whether it is an On Demand or Capacity account: On Demand: Usage-based pricing with no long-term licensing requirements.

Capacity: Discounted pricing based on an up-front Capacity commitment. Note To access your account, you can use an account identifier that specifies your organization name and account name. FIX - When configuring an Active Directory discovery task, the Admin Console disables hidden fields to prevent misplaced configuration values FIX - The inventory data related to xml files used to identify Adobe application licensing information is processed and stored independently from the data related to swidtag files Enhancement - Improved Processing Logic: Inventory Server classifies the software data of a computer without a reported operating system and the same data of a computer with an unrecognized operating system with separate OSType identifiers.

Enhancement - New setting MaxProcessingFileSize for processing inventory scan result files: FileProcessorModule, in the Inventory Server configuration file, implements the new setting MaxProcessingFileSize: if a file is picked for processing and its size exceeds the configured value in bytes , the file is rejected and sent to the error folder with a log stating that the file size exceeds the configured value. The default value is null , which translates to an unlimited file size. Enhancement - During the service startup, Inventory Server checks if the database schema is up to date and, if needed, performs the necessary updates.

Enhancement - Inventory Server improves parallel access to the database to enable better concurrent processing of inventory data. Enhancement - The Data Update Job procedures transferring data related to Cloud Application Metering have been optimized for performance and to transfer less data. Enhancement - The File Extractor tool has been updated with quality-of-life enhancements. FIX - The operating-system of Hyper-V servers and some computers reported from 3rd party data sources is correctly recognized as Windows.

FIX - The size for the Name attribute of pre-recognized software data transferred during the Data Update Job has been increased to characters to prevent issues during the Data Update Job. FIX - The size for the Software Version data transferred during the Data Update Job has been reduced to characters to prevent issues during the Data Update Job , the complete resolution will require a future update of Snow License Manager.

FIX - Inventory Server implements an improved logic to check if the endpoint configured for use is available during service startup. FIX - Service Gateway installations implement a more robust self-update logic to update to the same version as the Master Server FIX - The port availability check has been temporarily disabled; this check normally would stop the service startup if the configured endpoint is already in use by another process.

FIX - Configuration Manager correctly writes secondary endpoint addresses in the configuration file when configuring a Service Gateway or a Standalone Receiver installation. FIX - VMware is now spelled correctly in the database table inv.

When the value of this setting is set to "true", after processing an updated ruleset, the module automatically publishes the new definitions to all agents, without the need for further configurations in the Snow Inventory Admin Console. Enhancement - The internal procedures used to assign targets to a deployment task have been optimized for better performance when processing a large number of objects simultaneously.

Enhancement - The internal procedures used to remove data from the Snow Inventory database have been optimized for better performance when processing a large number of objects simultaneously. FIX - The scope of the identity enumerator for software data has been expanded to prevent issues with software recognition FIX - This version of Snow Inventory Server improves the logic that prevents it from processing inventory files and run the garbage collector during the Data Update Job: the mentioned processes are now temporarily halted while the Data Update Job reads from the Snow Inventory database during its "MainStream" part and during the execution of custom stored procedures FIX - Computers inventoried through Snow Integration Manager will present their first reporting date as ClientInstallDate in Snow Inventory, if the information cannot be retrieved from the original data source.

This will be reflected in Snow License Manager in an upcoming release FIX - An Active Directory Discovery scan is not blocked when the server cannot establish its identity due to a communication timeout. FIX - A missing resource used in the agent deployment process has been reintroduced. FIX - When processing an inventory file, the computer heartbeat is updated to reflect the inventory scan date of the file, unless the heartbeat already recorded is more recent.

FIX - Snow Inventory Master server checks the connection to the configured database when the service is started and quits immediately if the database cannot be contacted. FIX - The logging for the processing and the deployment of updated cloud application discovery rules has been improved. The settings allow to configure the timeout values, in seconds, for connection attempts and command executions against the database. FIX - The CommandTimeout setting can be adjusted to enable Snow Inventory Server to correctly add a large number of computers as target for an update task NEW - Support for proxy servers in the Service Gateway configuration: When configuring a Service Gateway, it is now possible to configure a proxy server and eventual credentials to use when communicating with the Master Server or another Service Gateway.

Enhancement - To improve consistency and reliability of the inventory data for computers that receives it from more than one source such as agents and Integration Manager connectors , Snow Inventory Server now implements an improved logic to consolidate incoming inventory scan results. Enhancement - It is now possible to configure the last-activity span for computers or users that are inventoried via Active Directory Discovery. The default value is 90 days. When Active Directory Discovery results are processed and the combination of the LastLogonActivity and the WhenChanged attributes of an object is more recent than the value of DaysSinceLastLogin, the object data is processed.

Otherwise, the data is discarded. FIX - The Inventory Server service will not start, and an error will be recorded in the log file, if it is configured to use a TCP port already bound to another process. FIX - Temporary files generated while receiving inventory data are removed if the connection is not closed graciously FIX - Computers reporting Inventory data using Snow Inventory Client are now correctly identified when the Sitename configuration parameter is changed FIX - Snow Inventory Server can now process and store information on the number of logical processors FIX - Computers where the operating-system is recognized as server-class are always presented as servers FIX - Alibaba Cloud virtual machines are recognized as such FIX - Nutanix virtual machines are recognized as such.

FIX - Active Directory discovery can be performed on domains different than the one of the server where Snow Inventory Server is installed FIX - Invalid discovery files are discarded and don't interfere with processing other files.

FIX - The indexes for the metering tables of databases upgraded from version 6. FIX - Database stored procedures used in the Data Update Job now take into consideration the start time of the job itself. Enhancement - Extended Active Directory user discovery. Enhancement - Improved performance in the Data Update Job. FIX - Snow Inventory Server Configuration Manager now can correctly change the database connection settings in the configuration file for a Master server instance.

FIX - Snow Inventory Server now locks inventory files being processed to prevent excessive memory consumption and to allow the files to be completely processed FIX - Email addresses from the Active Directory user discovery feature are now processed correctly FIX - Inventory Server now uses an alternate method to check the availability of discovered computers FIX - Inventory Server now correctly performs the discovery of Active Directory computers and users according to its default configuration, if present.

FIX - The logic used to detect Adobe software installations has been updated to reflect the format of swidtag and slconfig. Note: processing data from the slconfig. FIX - Logical file-system volumes that are part of a virtual volume will no longer contribute twice to the total disk space shown in Snow License Manager FIX - Oracle Database 19c is now correctly recognized.

FIX- Snow Inventory Server now implements a more accurate mapping of computers which reported inventory data and computers that were discovered on the network or in Active Directory.

The new feature "Site name grouping" is used to further improve the results of the mapping; note: this might require some additional configuration to be performed in the Admin Console. FIX- Leveraging the "Scan status report" feature, Snow Inventory Server can now correctly handle the data reported by the Snow Integration Manager BigFix connector on the installed applications and on the virtual machines run on a computer; note: the implementation of this functionality in Snow Integration Manager will be available in a future release PRB FIX- Snow Inventory Server now correctly handles virtual machine data for a host when this data is reported by multiple data sources.

It is recommended to run a full aggregation of all the connectors configured in the Integration Manager after applying this update. PRB 6. This allows to easily replicate the data to a test environment and to facilitate troubleshooting. To enable this functionality, Snow Licensed Manager 9. FIX- In some scenarios, the Data Update Job would fail with an error like "The maximum system-generated unique value for a duplicate group was exceeded This has been corrected PRB FIX- Oracle Database version 18c is now recognized correctly.

FIX- The Inventory Admin Console now correctly prevents defining more than one weekly task in the agent configuration, to ensure that the resulting configuration file is valid PRB FIX- Virtual application packages that were reported multiple times are now handled correctly and will not cause errors in the execution of the Data Update Job PRB FIX- The names for virtual machines reported by their host is now stored as reported, and not truncated at the first period '.

Existing collected information will be deleted when this update is applied. Monitors along with these new properties can be seen in the Inventory Snow Management and Configuration Center plugin.

If the same server reports back again, a new entry will be created. This has been corrected ensuring that the duplicate entries do not stop the processing of other entries. FIX - A correction has been made in Inventory Snow Management and Configuration Center plugin preventing adding the group "Discovery metadata" from "Available columns" to "Selected columns" while creating a new discovery view from causing an error message PRB This has been corrected, and during the run time of operations a dialog box will be shown.

This dialog box block user interactions until all operations have completed or the user aborted the interaction by clicking on a button on this dialog. Aborting the interaction will not roll back any data. Any devices that have been deleted will remain deleted PRB FIX - Every web application record must have a valid and non-empty name.

FIX - Previously, when exporting an agent configuration using the Inventory Snow Management and Configuration Center plugin, some mandatory tags were omitted; such as "Action" and "Oracle". This is no longer the case. FIX- Communication issues with gateway servers installed on a Google cloud service or Amazon AWS, resulting in An unhandled error has occurred in an initialization or run task entry in the logfile have been resolved and Snow Inventory Server now connects correctly to service gateways in virtualized environments PRB FIX- When users log in to an application multiple times within very short time intervals, Snow agents can report identical user entries, which results in duplicate entry errors on the Snow Inventory database.

This improvement ensures that virtual machines can be correctly matched to their host, and inventory data collected from these machines will be correctly shown in Snow License Manager views and reports PRB FIX- Additional error handling has been added to prevent incorrect processing of application pathnames containing a period. Such pathnames are now correctly interpreted, and a corresponding software row for the application is created in the Inventory database PRB An error no longer occurs if the procedure to get the speed of a processor returns a value of more than 10GHz.

Duplication errors caused by software rows with the same ClientID and Name no longer arise, as duplicates are now ignored. FIX- Hostname only mode has been modified to identify different types of agent reporting for the same hostname, ensuring that correct network topologies are created PRB This will improve the core-factor mappings in Snow License Manager.

FIX- Snow Inventory Server now considers all characters of the inventoried software information when generating a unique identifier softwarehash , instead of only using the first characters.

FIX- Additional data handling has been added to prevent the Inventory Admin Console from unexpectedly quitting when users with either low bandwidth or large data sets were switching between device information pages. The Unix Agent has been updated to mimic the operating system behavior, and now runs the legacy command in addition to the standard pkg info command, and collates the result to provide a more comprehensive inventory.

FIX-The agent now includes additional error-handling to process filenames retrieved by the Solaris package manager. When the agent encounters filenames that include characters outside of the POSIX standard, it now completes processing and creates a valid snowpack file containing inventory data. FIX-Unix file commands executed by the agent that return more data than standard error is set to manage previously caused the agent to wait indefinitely.

Additional error-handling has been added to the agent to prevent it from waiting in such scenarios. FIX-The version number for the Solaris 10 operating system is now inventoried correctly. FIX- Logging of syslog can now be enabled and disabled using the Syslog setting in the logging section of the agent configuration file.

FIX- When a connection to the Inventory Server fails, the agent now logs an error instead of a warning in the log file. In most cases, there is no need to change the agent configuration, but for more detailed information on the new behavior, you can refer to the Agent configuration topic on the Docs Portal.

Enhancement - The agent attempts to send pending scan result files every time it successfully contacts one of the configured endpoints IDEAS-I Enhancement - Each PowerShell script run during an inventory scan is executed in a separate context. This prevents a failure in one script execution from affecting any others. Enhancement - The agent reports the resulting status of scanning the computer for swidtag files, together with the resulting content; this will enable future releases of Snow Inventory Server and Snow License Manager to better handle recognition of added, removed, or changed software.

FIX - The agent can record application usage when the service is run by a user who is a part of the local Administrators group. FIX - The agent reports when the scanning for swidtag files has been performed but returned no results FIX - The agent does not append unexpected Unicode characters when reporting the name of the device that originates the session for remote application usage FIX - The agent implements a more robust method to collect metadata for running executables, improving the logging in case of failure FIX- The Agent now cleans the log files generated by Windows after scanning for virtualized applications FIX- The amount of total memory reported by the Agent for Windows is now consistent with other platforms and it reflects the total amount of physical memory instead of the amount of memory available to the operating system PRB FIX- The agent now does not collect data about environment variables and file shares when the configuration setting software.

FIX- In some scenarios, temporary files were left on the client after a scan involving virtualized applications. This is no longer the case PRB NEW- It is now possible to configure the Agent to never retrieve updates from its configured endpoint s. FIX - The executable file cloudmeteringhost. This will prevent alerts from security software. FIX - When retrieving printer information, the printer share is now included in the result file.

Additional logic has been added to the agent to ensure that all requested data is extracted from the virtual registry PRB and PRB FIX- When the agent encounters multiple copies of the same file — same name and metadata — in different locations, it now reports all instances ensuring correct software recognition PRB FIX- It is now possible to use environment variables in the agent configuration file to exclude locations of the local file system locations from an agent scan PRB FIX- Logical errors preventing some PowerShell scripts from running successfully are resolved so that the agent can run custom and Snow scripts successfully PRB Reduced memory usage for web metering rules.

Enhanced script-tampering protection. Diagnostics enabler for cloud application metering. Hardening of dll search path. Issues related to invalid metering data collected from computers that are locked at midnight or locked when the agent runs the scheduled scan have been resolved, ensuring that all data collected by the agent is processed. The agent now searches the correct registry based on its architecture.

Product keys for Windows 8 and higher are now correctly extracted from the target machine. This setting defines the timeout value, in seconds, for requests to the server endpoint and has a default value of 15 seconds. Intel Coffee Lake-U processors. Intel Z AMD ThreadRipper If the agent is started and the stored time has passed is used to determine whether the scan time has passed.

If so, a scan is carried out immediately. We have added a new setting, Software-Include, which will function together with the existing Software-Exclude configuration settings. If Software-Include paths are present in the agent configuration file, the agent will scan the specified paths. If Software-Include paths are not set, the agent will scan all local disks.

If Software-Exclude paths are included, these spaces will not be included in the scan. FIX- Lingering application metering data for applications that have been removed no longer causes software rows to be created for the removed application PRB, PRB Fix - The agent collects information on the Java runtime environment installation from its manifest instead of the executable output Fix - To avoid duplication of users when the agent reports on application usage, the username format always begins with the domain or computer name.

Note: Existing users are not removed from the database and must be managed in Snow License Manager To facilitate having a complete visibility over the user computing estate, Snow Inventory Agent for macOS now natively supports both Apple M1 chips and Intel chips. FIX - The logic used to determine an application usage time has been improved to account for adjustments of the computer time FIX - The agent correctly includes the logs in the. FIX - The logs related to installing or removing the Cloud Application Metering extension for Firefox are now reported at the verbose level FIX - Inventory Agent can make the browser run the cloudmeteringhost process when the browser extension is deployed using third-party tools.

FIX-Cloud metering data is now stored with the correct domain name information. Previously, domain data stored in the wrong format would cause the cloud metering data to not show up at all in Snow License Manager. FIX- The agent now removes empty snowpack files to prevent issues with some external proxy configuration PRB 6.

When cloud-application metering is enabled in Snow Inventory Admin Console, the MacOS agent monitors SaaS applications accessed through Safari via a browser extension installed on the target machine.

The agent gathers metering data for SaaS applications running in Safari, as well as the name of the browser. This data is packaged together with the normal inventory scan of the target machine and sent to Snow Inventory Server for storage and processing. FIX - The agent will no longer report a new login event for a user when xMetering is enabled and a new process is executed within the user context PRB FIX - The agent will no longer generate a file with extension.

FIX - Significantly reduced the memory used by the xMetering process when recording a large amount of information in the log files PRB FIX- In some cases, it is not possible for the agent to extract the install date for an application from the local machine.

Previously, the agent entered the scan date into this field. It now leaves the install date field empty so that incorrect data is not presented to the user in Snow License Manager PRB This setting defines the timeout value, in seconds, for requests to the server endpoint.

The default value is 15 seconds. This parameter is enabled by default. Enhancement- Functionality to detect and gather information about NVMe-disks on newer MacBooks has been added to the agent. Full utilization of this functionality is dependent on an upcoming release of Inventory Server. Enhancement- The curl library has been updated to maintain compatibility and ensure that the latest vulnerability patches included in these libraries are applied, such as the most recent release of the communication protocol TLS 1.

Enhancement- The request header sent to the server now includes site name. In the future, this data will enable the Inventory Server to block unwanted agents more efficiently. Enhancement- The capability to gather information from local disks has been upgraded to support new Apple file systems and hardware. Full utilization of this functionality is dependent on an upcoming release of Inventory Server PRB FIX- The agent now reports the correct number of physical cores when Hyper-Threading is enabled on the machine being scanned.

FIX- The agent no longer causes a segmentation error when the running update-package command is run from the command line PRB Update Details Snow Integration Manager 5. Product: Snow Integration Manager Current version: 5. Enhancement - SIM installer connector names updated for consistency. Enhancement - Additional validation for proxy profiles. When you create a proxy profile, Snow Integration Manager now validates all required fields before you can save the profile.

FIX - The Microsoft connector now supports connecting to Microsoft Cloud for US Government, the mission-critical cloud for US federal, state, local, and tribal governments and their partners Enhancement - VMware vSphere connector: The connector now supports use of proxy profiles, configurable from the Proxy profiles tab in Snow Integration Manager. The connector configuration now requires a link to the API root address instead of the server address.

An option to manually select the API version to use for collecting the data is also added to the connector. It is now possible to select one of the three values: Display name, User principal name, Logon name FIX - VMware vSphere connector - Fixed an issue for cluster-free environments, where the aggregation would previously fail and not continue Improved security—Customers can now indicate a proxy server to connect to AWS.

Enhancement - Greater flexibility for VMO connectors When configuring any Snow Virtual Management Option connector, customers can now enter the global site name, in additional to the usual local site name.

The window also shows information about the aggregation progress. It is also possible to cancel the ongoing aggregation from this window. FIX - Amazon AWS Discovery connector: Issues regarding regional restriction and new regions are fixed with the introduction of region login enhancement, as detailed above , Note: Using the legacy DCC naming option is not recommended.

FIX - ServiceNow Discovery connector - Corrected an issue where the connector would not finish processing all devices if any device had an empty name The connector now interprets numbers larger than 60 correctly FIX - Aha!

SIM 5. The configuration now also accepts hostname. Affected customers may need to review their configuration. Having empty both cluster name and datacenter name causes Data Update Job to fail.

The connector now populates all relevant attributes FIX - ServiceNow Discovery connector: Changed the data collection logic to try again if an api call fails on first attempt. Enhancement Microsoft connector: All of the PowerShell cmdlets previously used for fetching M data have been removed for the connector.

For more details, see the enhancements notes above. Processed files now have a timestamp in the file name FIX - Added an option to set the maximum batch size used when uploading data to RemedyForce The following connectors or compatibilities have been discontinued in Snow Integration Manager 5.

Enhancement - Microsoft Azure Discovery connector: Added filtering of instances based on a wildcard filter and instance provisioning time. The default start value is 30 days. Some users experienced errors from powered off or unavailable hosts when the filter was not active. FIX - Aha! SaaS connector - FIX - Adobe Creative Cloud connector - The connector is now correctly assigning users to subscriptions when group assignment is used FIX - Improved handling of missing host data, preventing errors during aggregation and allowing the file output to continue , This gives our customer the ability to use different proxy settings for different connections.

In this version we have added support for proxy profile to two connectors : Microsoft Office and Adobe Creative Cloud. In the connector configuration window , a dropdown is added , to both Snow License Manager and Office connection , where the user can choose proxy profile to be used Enhancement - Adobe Creative Cloud connector: Added support for proxy profiles. Activity is now based on the last event generated by the user According to development best practices in.

NET, all security protocol references are removed from the code. Security protocol negotiation is now handled by the operating system completely. Enhancement - BMC Remedy The connection timeout and the number of instances to upload per batch can now be configured.

Added V2 API endpoints for fetching of computers and software instances. Detailed OS data is being collected. Discovered UNIX packages data is being collected. Discovered Windows executable files data is being collected.

Added batch size textbox to control the number of items fetched by the API calls. FIX - Microsoft Azure connector - The connector log messages are improved to avoid the impression that it fails to get data from some Azure deployments Snow Inventory 3.

Added full vendor names to connector names. Log setting is now retained on upgrade to a newer version. The installer now checks to see if Snow Integration Manager is already installed and, if so, use the old path rather than needing the customers to re-enter a non-default path for installation.

This behavior is now changed and the errors are now logged in the default log. Microsoft SCCM had the end of life in FIX-SLM Data Exporter — Fixed an issue where the export files were not consistent from one aggregation to another and handled error messages that occurred with every aggregation. PRB 5. Enhancements-Office connector - The connector is now collecting two new fields, Country and Department information on Office users. Note: To view this information Snow License Manager 9. Enhancement- BMC Remedyforce connector Introduced Delta aggregation with the use of the last scan date on devices reducing the amount of data for each aggregation.

Added collection of mobile applications. Added bios serial number to computer system objects in addition to the existing relationship to a bios object. Mobile devices are now correctly added as phones and tablets instead of computer systems. Added SLM status field to mobile devices.

Removed mapping to field Description. ShortDescription is only mapped when there is relevant information in SLM that does not have an equivalent in Remedyforce. Map model to computers and mobile devices. Added logging of Apex processing time to the SIM log. Increased performance on big data sets. Also added filter option Include applications and include users with a relationship of type most frequent user.

Enhancement- Citrix XenServer connector- Added import server list functionality to ease the configuration process. Enhancement- ServiceNow Discovery connector- Added filtering tab with the option to exclude devices based on ServiceNow system class.

Enhancement- Miss Marple connector Made performance optimizations that reduce memory consumption, especially in large environments. Added an option to backdate metering data to cover periods between SIM aggregations.

Resolved an infrequent issue with Operating System names. FIX - Proxy issues, even with valid settings, that were causing the connection to Snow License Manager and ServiceNow to fail have been resolved so that connection now succeeds. FIX- Transfer of data does not occur while the Data Update Job is running, ensuring that changes made to a customer environment are correctly reflected in the Snow License Manager database.

FIX - Filtering has been updated to ensure that virtual machines running in VMware, Hyper-V, or other environments are correctly identified as such.

Virtual machines identified as other are ignored. When the slash character is missing, it is now automatically appended. If only one customer is available, it is automatically selected. The new connector for Adobe Creative Cloud extracts the necessary data points from the Adobe portal to visualize and calculate the insights provided by Snow License Manager, including: email users use to access their Adobe account, last logon information, and usage requires Snow License Manager 9.

NET Framework. NEW - MobileIron version NET Framework 4. NEW - Microsoft Office connector data points that are not used by Snow License Manager are no longer extracted by this connector, reducing the amount of data collected. Connection issues when using TLS 1. NET 4. FIX - Microsoft Office FIX - Missing buttons. Removed hardcoded string prepended to short description field.

Out of memory and most frequent users changes. Added option to filter out applications. To more accurately display VMware hierarchy, user-defined datacenter names are no longer supported. FIX - Hyper-V — scanning no longer fails for virtual machines that do not have a guest service installed for the entire scan PRB Support for the upcoming release of Snow for ServiceNow, version 3.

Additional data for software instances is now extracted from Snow License Manager, including: install date, date-and-time first and last used, run information, average usage time, usage in minutes, and users FIX - When configured to target a remote inventory server, discovery.

FIX - To handle large environments: the token to BMC Remedyforce is now renewed to prevent loss of access during long runs; and error-handling has been added to the paging system. FIX - SaaS: The WebEx connector now retrieves the date and time of a user's most recent activity correctly, and consequently correct usage data is now being collected. NEW - HP UD — to enrich the data provided by this connector: software metering is now included in the data provided by this connector, the field IsPortable is now set to True for laptops and portable devices; an additional field, IsTablet , has been added to client element, parsing of LogicalDisk entities has been improved, and If available valid filename is extracted for file pathnames ending with a zero.

NEW - BMC Remedyforce — filtering options for desktops, servers, laptops, logical disks, and optical drives have been added for data gathered from Snow License Manager. FIX - Azure Discovery — bad request aggregation error no longer arises when retrieving data from Azure. XSF file extensions can be handled. The connector now extracts data for: Drives other than hard-disks, such as CD-ROMs, and floppy-disks, as a physical disk element Environment variables, such as the location of user profiles OS services, such as the name and location of operating-system services Parsing virtual machine elements now correctly identifies the entity as virtual Additional data is extracted for software elements NEW - HP UD: HP-Universal Discovery UD Formerly known as HP-DDMI — a new connector has been added to reflect the product name change by the vendor.