Licensing & Reporting

Licensing & Reporting

With  Cloudhouse's license and reporting feature enables you to understand  application usage patterns within your business, including how many people are using what apps, on what OS, when and how often. 

Please note, user and machine name information is hashed using SHA256 algorithm, before being written to file so that no user, or machine identifiable information is visible in the licensing data sent to Cloudhouse.

Containers record deployment and usage events in plain text files, on a central file share using a comma separated value (CSV) format so that it can be imported into a customer’s existing 3rd party system and  submitted to Cloudhouse for billing purposes.

License Usage Filename

Each recorded event is  approximately 260 bytes, and it is written to the file Hashed$UserSID$MachineID_usage.csv, using the following folder structure beneath the folder specified in /usagelocation specified when deploying the Container;

Folder Structure

$usagelocation$\ YYYY \ MM \ Container_ID \

Please  note, in order to create a valid file name, special characters that are  not supported by the file system will be removed from the hash of the User SID and Machine SID. The Deployment and Run commands will attempt  to log each event up to three times, if the file is unavailable or in-use then they will give up, and record an error in the Windows Application log.

Additional Information

Backup & Archiving

Under  the terms of EULA, Cloudhouse has the right to audit customers for up  to three years, for this reason Cloudhouse recommend maintaining back  ups, and archives of the data for up to 3 years. All data on the file share should be backed up as part of the company's standard backup and archiving policies, once data has been submitted to Cloudhouse it can be  stored in the archive, until then Cloudhouse recommends keeping the  data on the file share. 

Was this article helpful?

Can't find what you're looking for?

Contact Support