Updating the Application in a Container

The following options are available when using the Auto Packager

Option 1 - Reuse Existing Container

  1. Double click the Cloudhouse Auto Packager shortcut
  2. From  the Capture screen, click “Select Package Folder”, select the folder  containing the Container you want to update, the screen will now display  a message “Press Next to load the previously completed capture”
  3. Click Next, Files and Registry changes which occurred during the capture process will be displayed, and split into two columns; Files in Package & Files Requested at Runtime
  4. Right-clicking  on a folder or file captured during the installation (in the Files in  Package column) provides a context menu from which an action can be  selected such as ‘Remove’.
  5. Additionally, if the  user needs to add files or folders which were not captured during the  Installation process, the user can click on either a File or Folder from  the Files requested at runtime column, and then use the left arrow  (indicated above) to move them into the Files in package column
  6. When all the necessary changes have been made, click Next, this will now present the Registry screen split into two columns; Registry keys in package & Registry keys requested at runtime
  7. Registry keys can be removed as well with ‘Remove’.
  8. Additional  registry entries which were not captured during the Installation  process or captured at runtime can be added with the left arrow  (indicated above) to move them into the registry entries in package  column
  9. Click Next
  10. Complete the packaging  process by providing the App Name, again this will automatically create a  GUID, however, users will need to edit this, to reflect the SAME GUID  as was used to previously package the application.
  11. Enter the description of the application and select the desired executable.
  12. This screen will allow users to make updates to their existing package. There are three ways to do this 
    • If the destination folder field is left blank, this will update to the root of the GUID folder. This will OVERWRITE all previous content, without ANY warning – and there is no way to reverse this!
    • Specifying a folder which does not exist, will result in a new folder being created and used for creating the Container.
    • If the folder already exists, the content of the Container will be OVERWRITTEN without ANY warning and there is no way to reverse this
    • Creating nested folders: use the Upload Destination Folder field to enter the required nested path, for example Package\NewPackage\Draft (NOTE: Spaces and special characters are NOT accepted)

 13.  From the New Package Files box users can select the desired files to be added to the defined location

Option 2 - Create a New Container

Run Auto Packager and open existing Container folder, follow the instructions Creating Containers with the Auto Packager to perform the install capture to package the latest version of the application.

Update Deployed Instances of the Container

Once  the Application files have been updated in the Container, the changes  in the Container need to be pushed out to servers and desktops using the  Cloudhouse.Container.Deployment /update command.

Was this article helpful?

Can't find what you're looking for?

Contact Support