FlexApp Packaging Guidance (AS2 Shared Image Option)

Amazon AppStream has released a new feature called Shared Images. These shared images are intended to increase efficiencies within the AppStream management process by building out repeatable processes or templates.

Liquidware is excited to create a shared image as part of this workflow based on our FlexApp Packaging Console. Enterprises can now use the Liquidware shared Image for packaging applications. Liquidware has created a fully configured FlexApp Packaging Console image with all the best practices already applied.

1. To get access to this shared image with your AWS account, email
   AS2FPCImage@liquidware.com with the following information:
   • Name
   • Company
   • AWS Account number. If you do not know your AWS account number, refer to this article to locate it: 
https://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html
   • AWS AppStream Region 
2. After you receive confirmation that the image was shared with your AWS account in the requested region, you can start the process of building a fleet from this image.
   1. Go to your AppStream console in the correct region.
   2. Go to Images and Image Registry.
   3. Change the filter drop-down from All Images to Shared with Me.
      • You should see this image: Liquidware_FlexApp_Packaging_Console_Base_OSversion_v6.8.x_v1.x.x.
      • The OS version should match your fleet. All OS versions will show under all images shared with me.
      • v6.8.x will show the version of the FlexApp packaging console shared with you; this should match the version of your ProfileUnity Install.
      • v1.x.x is the version based on any new changes to the image itself.
   4. After you see this image, move to image builder and launch image builder.
   5. Change All images to Shared with Me.
   6. Pick Liquidware_FlexApp_Packaging_Console_Base_OSversion_v6.8.x_v1.x.x from the list.
   7. Build your image as normal.

   8. Note: For the image builder steps this part does not have to be part of the domain.

   8. After your image is running, log in to the FlexApp Packaging Console to make sure it is connecting to the ProfileUnity Console.
   9. Close the FlexApp Packaging Console and edit the following XML file so that the URL and username are pre-filled: 
   10. C:\Program Files (x86)\Liquidware Labs\FlexApp Packaging Console\FlexApp Packaging Console.exe.config.xml
   11. Change:
   12. PackageManagementUsernameRaw>jason</PackageManagement
       UsernameRaw>
   13. To:
   14. <PackageManagementUsernameRaw>%username%</PackageManagementUsernameRaw>

   10. Build your Packaging fleet from this new image with Domain join.

       1. Click Images.

       2. Click Image Builder and look for the image you just created based on the FlexApp Packaging Console image.

       3. Create a fleet from your new image. Note that the user must be an administrator over the fleet VMs to package applications.

          • Platform: The OS version you picked from
          • Instance Family: General Purpose, Compute Optimized, Memory Optimized
          • Apps Included: FlexApp Packaging Console, Explorer, and Firefox
          • Instance type should be a minimum of 8 GB of RAM
          • Active Directory is required
          • Finish out the rest of the settings to create your fleet from your version of the Liquidware shared image.
   After you receive confirmation that the image was shared with your AWS account in the requested region, you can start the process of building a fleet from this image.
   1. Go to your AppStream console in the correct region.
   2. Go to Images and Image Registry.
   3. Change the filter drop-down from All Images to Shared with Me.
      • You should see this image: Liquidware_FlexApp_Packaging_Console_Base_OSversion_v6.8.x_v1.x.x.
      • The OS version should match your fleet. All OS versions will show under all images shared with me.
      • v6.8.x will show the version of the FlexApp packaging console shared with you; this should match the version of your ProfileUnity Install.
      • v1.x.x is the version based on any new changes to the image itself.
   4. After you see this image, move to image builder and launch image builder.
   5. Change All images to Shared with Me.
   6. Pick Liquidware_FlexApp_Packaging_Console_Base_OSversion_v6.8.x_v1.x.x from the list.
   7. Build your image as normal.

   8. Note: For the image builder steps this part does not have to be part of the domain.

   8. After your image is running, log in to the FlexApp Packaging Console to make sure it is connecting to the ProfileUnity Console.
   9. Close the FlexApp Packaging Console and edit the following XML file so that the URL and username are pre-filled: 
   10. C:\Program Files (x86)\Liquidware Labs\FlexApp Packaging Console\FlexApp Packaging Console.exe.config.xml
   11. Change:
   12. PackageManagementUsernameRaw>jason</PacageManagementUsernameRaw>
   13. To:
   14.  <PackageManagementUsernameRaw>%username%</PackageManagementUsernameRaw>

   10. Build your Packaging fleet from this new image with Domain join.

       1. Click Images.

       2. Click Image Builder and look for the image you just created based on our FlexApp Packaging Console image.

       3. Create a fleet from your new image. Note: The user must be an administrator over the fleet VMs to package applications.

          • Platform: The OS version you picked from
          • Instance Family: General Purpose, Compute Optimized, Memory Optimized
          • Apps Included: FlexApp Packaging Console, Explorer, and Firefox
          • Instance type should be a minimum of 8 GB of RAM
          • Active Directory is required
          • Finish out the rest of the settings to create your fleet from your version of the Liquidware shared image.