Use the User option when you need to deploy a Cloudhouse Alchemy Compatibility Package to a specific folder for a single user, which copies all of the files to the specified directory and installs each component.
For example, a physical or virtual desktop/laptop.
Prerequisites
To deploy a Compatibility Package to a user, you need:
- An account with access to the target computer.
- A valid Licensing Token within the Compatibility Package.
Process to Deploy a Compatibility Package to a User
- Start a Command Prompt.
- Run the following command:
<path_to_package>\Cloudhouse.Container.Deployment.Exe /deploydir <target_path> /accepteula /deploytype user
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 (x86)" /accepteula /deploytype user
What happens during a User Deployment?
When a Compatibility Package is deployed to a User, the following occur:
- The application is installed without Administrator rights and the Compatibility Package is registered for only a single user.
- Any file associations specified in FileAssociations.xml are created in the HKCU registry hive, to be accessible by a single user on the machine.
- Any shortcuts specified in Shortcuts.xml are registered for a single user on the machine. Any shortcuts with a path pointing to the All Users Desktop are translated to the Users Desktop and any shortcuts with a path pointing to the All Users Start Menu are translated to the Users Start Menu, to be accessible by a single user on the machine.
- Any Com servers specified in ComDeployment.xml are registered in the HKCU registry hive, to be accessible by only a single user.
Validation
When a Compatibility Package is deployed in the User context, validations are performed to ensure that:
- A valid licensing token exists at the top level of the Compatibility Package.
- The AAV binaries exist in 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.