FlexApp Packaging Guidance (Traditional)

The FlexApp Packaging Console builds the individual application packages that can be layered into a user’s environment. The goal is to provide a clean packaging environment, so that when packages are layered in, they include everything the application needs to run including all file and/or application dependencies. We want to create a successful, repeatable installation process across all user’s desktops. Therefore, the FlexApp Packaging Console has a few system requirements including:

  • The packaging console should be installed on a Windows operating system that can be reset after each package is created. Using a non-persistent pool or a virtual machine with a snapshot that can be rolled back is fully acceptable.
  • Do not install the packaging console on the same machine where the ProfileUnity Management Console was installed.
  • The FlexApp Packaging Console has an additional bit-level requirement. The bit-level of the operating system on which you package applications with the FlexApp Packaging Console needs to match the operating system of the desktop to which you deploy applications. If you are packaging applications to be used in a 32-bit environment, you must use the Packaging Console on a 32-bit OS. If you are packaging applications to be used in a 64-bit environment, you must use the Packaging Console on a 64-bit OS.

FlexApp Packaging

Follow all traditional or enterprise application packaging best practices in combination with a few additional FlexApp based recommendations.

About the Packaging Virtual Machine

Following application packaging best practices is critical to your success. The main goal with the FlexApp Packaging VM is to keep it as clean as possible between capturing applications and the make sure the OS is free from noise. You do not want anything left behind from a previous application installation and capture. Merely uninstalling applications will not work; it must be as if the applications had never been installed.

  1. Disable Windows Updates.
  2. Disable Volume shadow copy.
  3. Disable any other service/software that might try and update themselves.
  4. Install All .Net runtimes.
  5. Install All C++ runtimes.
  6. Install the FlexApp Packing console.
  7. Log in to the FlexApp Packaging console.
  8. Power down.
  9. Snapshot the VM. This is the snapshot point we will roll back to after each capture.
  10. Power on.
  11. Log in to the FlexApp Packaging Console.
  12. Start and capture the app.

  13. Important: Not following the .NET and C++ steps can cause large CPU and RAM usage from our agent.

Target VMs/Pool/Fleet

  1. Disable Windows Updates.
  2. Disable Volume shadow copy.
  3. Disable any other service/software that might try and update themselves while packages are active.
  4. Install All .Net runtimes.
  5. Install All C++ runtimes.

  6. Important: Not following the .NET and C++ steps can cause large CPU and RAM usage from our agent.