Cloudhouse Alchemy's Licensing and Usage Reporting features enable you to ensure you are compliant with the Terms and Conditions of your End User Licensing Agreement (EULA), for creating and managing Alchemy Compatibility Packages.
These features also help you understand application usage patterns within your business, including information on how many people use each application, on which OS, when, and how often.
By default, Cloudhouse Alchemy Compatibility Packages automatically report their usage data as detailed Website and Port Requirements for Alchemy Licensing and Usage Reporting, whenever the following Compatibility Package-related events occur:
- Deployment
- Start
- Uninstall
Important
A valid Online Reporting Token must be present in the Compatibility Package’s root folder on deployment and prior to the first run. On the first run, a Run Token is copied to the relevant location depending on the deploy type. A Compatibility Package will fail to deploy or run successfully without a valid Online Reporting Token or Run Token.
Deployment Event Reporting
A deployment reporting event is recorded each time the Cloudhouse.Container.Deployment.exe is triggered, whether by command line, script or deployment tool.
It reports whether a Compatibility Package deploy or uninstall operation is performed.
Note
Compatibility Packages can be deployed into a Virtual Desktop Infrastructure (VDI) environment using a Golden Image from which computers are created. When the Compatibility Package is deployed into the Golden Image, only a single deployment event is recorded.
Deployment events are not reported when the image is cloned.
Important
Different URLs and behaviour occurred in previous versions of Usage Reporting. See DEPRECATED: Alchemy Automated HTTPS Usage Reporting for details.
Run Event Reporting
An asynchronous usage event is recorded each time the Cloudhouse.Container.Run.exe is triggered during an application start event.
Important
Different URLs and behaviour occurred in previous versions of Usage Reporting. See DEPRECATED: Alchemy Automated HTTPS Usage Reporting for details.
Data Privacy
Although user and machine information is collected (User SID and Machine SID), this is automatically hashed using the SHA256 algorithm before it is recorded anywhere. Hashing the data ensures it remains private to the customer. No user or computer identifiable information is ever sent to Cloudhouse in usage data.
The following data is collected when usage is reported and sent securely over HTTPS:
UTC_TimeStamp, UsageId, PackageId, Event, Operating_System, CPU_Core_Count, Deploytype, UserSidHash, MachineSidHash, AAV Version, Deployment Version
What happens next?
We will process your usage data against your contracted license agreement, contacting you via the licensing@cloudhouse.com email address only if your usage has exceeded your contracted usage.