Use the Machine option when you need to deploy a Cloudhouse Alchemy Compatibility Package to a specific folder on a specific computer for all users to use, but when each user should have their own data stored in their own HKCU Registry Hive.
For example:
- A physical or virtual computer.
Prerequisites
To deploy a Compatibility Package to a Machine, you need:
- An account with Administrator access to the target computer.
- A valid Licensing Token within the Compatibility Package.
Process to Deploy a Compatibility Package to a Machine
- Start a Command Prompt as the Administrator.
- Run the following command:
<path_to_package>\Cloudhouse.Container.Deployment.Exe /deploydir <target_path> /accepteula /<switches>
where:
- <path_to_package> is the path to the source Compatibility Package you want to deploy.
- <target_path> is the path to the folder on the destination computer you want to deploy the Compatibility Package to.
- <switches> are any optional command-line switches you wish to specify.
For example:
C:\Packages\ERP-v2\Cloudhouse.Container.Deployment.Exe /deploydir "C:\Program Files" /accepteula
What happens during a Machine Deployment?
When a Compatibility Package is deployed to a Machine, the following occurs:
- Any file type associations specified in FileAssociations.xml are created in the HKLM registry hive, to be accessible to all users of that computer.
- Any shortcuts specified in Shortcuts.xml are registered for all users of the computer. Any shortcuts with a path pointing to the user's desktop or Start menu, are translated to the equivalent of the All Users folder so they are accessible to all users on the computer.
- Any services specified in Services.xml will be registered to the Windows Services, to be accessible by all users on the computer.
- Any Com servers specified in ComDeployment.xml will be registered in the HKLM registry hive, to be accessible by all users on the computer.
Validation
When a Compatibility Package is deployed in the Machine context, validations are performed to ensure that:
- A valid licensing token exists at the top level of the Compatibility Package.
- The AAV binaries exist within the Compatibility Package and all have the same version.
- The Compatibility Package binaries exist within the Compatibility Package and all have the same version.
- All required components exist in the Compatibility package.
- All XML files are valid.