Best Practices How To Optimized FlexApp Packaging Console and Gold Image for DIA FlexApp creation/deployment

Product: ProfileUnity          

Product Version: 6.5+

Expires on: 365 days from publish date

Updated: July 19, 2018



What are the best practices to create DIA applications with the FlexApp Packaging Console?


Some of the processes found in this KB are also part of this simple training video:

Optimizing Windows 10 FlexApp Packaging Console

Step 1) The FlexApp Packaging Console should be installed on a vanilla Windows system which:

  • Does not have 3rd party applications installed (aside from VM tools)
  • Should not have ProfileUnity client installed
  • Should not have ProfileUnity Management Console installed
  • Is a VM which can revert snapshots
  • Does not have Anti-Virus software installed
  • Does have all windows updates installed matching Gold/Master Image of the desktop pool (Step 3)
  • System OS and bit level should match VM's in the vMware View/Citrix server pool where DIA will be deployed. (Step 3)
  • The system should not be member of a domain now or previously (avoids alternation of machine by GPO)

Note: FlexApp cannot capture .msu installations (Microsoft Update Standalone Packages).

Step 2)  Windows 10 and Windows 7 with FlexApp requires all C++ run-times in the base OS of FPC and Gold image: 

Follow the link below to get ALL Windows Prerequisites script to run on FPC and Gold image: 

Other examples:

  • Laser Jet 4 (RightFax)
  • Any other Microsoft .NET version other than listed in KB above
  • J#
  • Java
  • Other C++ Run-times
  • Printer Drivers

Step 3) Optimization of FPC image ONLY:

a) Windows image recommended optimization scripts:

b) The manual optimization process (which is more limited to what the above scripts do) should include:

Step 4) Install the FlexApp Packaging Console software.

Step 5) 4 Log in to the FlexApp Packaging Console, pointing it to the ProfileUnity web console:

Step 6) Close the FAPC software, shut the VM down, and take a snapshot. 

The console is ready to create DIA packages.

Note: When FPC is out of domain when authenticating to the UNC share with windows explorer, where packages are created, select. "remember my credentials" so the FPC console would have uninterrupted access to the UNC path. 

Note: After capturing every DIA package, revert to the initial snapshot. This will ensure that any testing is done with a clean system and that further packages will not be 'polluted' with leftover settings and software from previous packages. In AWS the machine must be refreshed back to the master image. 

Note: Bad candidates for DIA applications are System Level type of Software packages like Security software, Anti intrusion security software packages, Anti Virus software packages, Network Port Scanners, Drivers, Runtimes or frameworks etc. 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request


Article is closed for comments.