FlexApp DIA Office 2013 and 2016 on Windows 10

FlexApp DIA Office 2013 and 2016 on Windows 10


Product: ProfileUnity-FlexApp

Product Version: 6.5.9

Updated: April 3, 2016



How do I create a DIA package of Office 2013 or 2016 on Windows 10

You must be on ProfileUnity 6.5.9 or later.



  • ProfileUnity version 6.5.9
  • Windows 10 (32-bit or 64-bit) with FlexApp Packaging Console (FPC) installed.  
  • The FPC machine must follow FPC best practices. (see KB)
  • Office 2013 or 2016 (32-bit or 64-bit, KMS versions only)
  • KMS Server with valid working licensing
  • FlexApp Office Script Bundle (1 zip file that contains 3 scripts)
  • Windows 10 LTSB when using Office 2016 not supported at this time.
  • If you are looking to use Outlook indexing the Windows search service should be started on the FPC (FlexApp Packaging Console) during office capture.  Then use the template "Outlook Search Index for Windows 7, Windows 10 and 2016 as a Desktop" in ProfileUnity 6.7.


Part I – Updating The Office-PostCapture Script For Your Environment

Since successful playback and capture of Office is dependent on KMS, the post capture script needs to be updated with your KMS server information. 

  1. Extract the scripts located in the FlexApp Office Script Bundle to a network location that will be accessible to the FPC machine. 
  2. Right click on each script and select Properties to confirm it is not blocked on the General tab. If it is, select the option to Unblock the file and click OK.  
  3. Edit the post capture script called FA0_W10-Office2013-2016-PostCapture.cmd.

  4. Within the script, find and replace all instances of KMSNAME with the IP or FQDN of your KMS server.

  5. Save the changes and close out of the script.

  6. Now Edit the post playback script called FA2_W10-Office2013-2016-PostPlay.cmd.

  7. Once more, find and replace all instances of KMSNAME with the IP or FQDN of your KMS server.

  8. Before closing, ensure that the proper KMS key for both the version of Windows and Office are set. By default the script is set to cover Windows 10 Enterprise and Office 2013 and 2016 Professional Plus. (KMS keys are included at the bottom of the script for reference)

  9. Save the changes and close out of the script.

  10. You are now ready to create a DIA package of Office with FPC. 

Part II – Packaging Office With FPC 

  1. Login to the FPC machine and connect/mount the Office installation iso to the FPC machine. (Close the AutoPlay prompt, if shown.)

  2. Open and log into the FlexApp Packaging Console.

  3. Click ‘Create’ to create a new package.

  4. Fill in all the required fields. For the Installer Location, browse and select the setup.exe file located at the root of the Office installation iso you mounted in step 1. 

  5. Once all required fields are filled in, click ‘Create’ to begin the packaging process.

  6. FPC will launch the Office setup wizard.

  7. After accepting the User Agreement, the Office setup wizard asks for type of installation, choose ‘Customize’. 

  8. This will present the Installation Options tab.  Select the root ‘Microsoft Office’ option dropdown and choose ‘Run all from My Computer’.
  9. Click the ‘Install Now’ button.

  10. The Office setup wizard will continue and finish the installation.

  11. !!CRITICAL STEP!! – before clicking the ‘Close’ button on the Office Setup Wizard, go to the network location were the 3 office scripts were saved.

  12. Run the one titled: FA0_W10-Office2013-2016-PostCapture.cmd
  13. Confirm that Office was activated successfully. There will be a line that indicates that 'Product activation successful'.
  14. Once confirmed, press any key to exit the command window.

  15. Now click ‘Close’ on the Office Setup Wizard window.

  16. Once the Office Setup Wizard closes, click the ‘Finish’ button in the FPC window.

  17. After the package creation process has finished, click the ‘Save’ button to finish saving the package.

  18. Since Office contains several icons for programs, FPC will likely prompt you to select an icon to use as the main one to display within FPC and ProfileUnity

  19. The Office DIA package has now been created and saved successfully.

Part III – Preparing The Office DIA Package For Playback

In order for Office to playback successfully, some additional configuration is required. 

  1. From the main FPC window, press the ‘Play’ button to playback the Office package with it’s current configuration.

  2. Once played back successfully, the ‘Play’ icon will change to a ‘Stop’ icon, indicating that the package is active and configuration can now be edited.
  3. Two icons to the left is the edit package icon, click the dropdown arrow to view all options. 
  4. Select the ‘abc’ icon at the very bottom, to add scripts to the package.

  5. The Package Scripts window will appear, click 'Add Script'. This will reveal additional dropdown options.

  6. The first dropdown option should list only appdir-1, select it.

  7. The second dropdown will allow you to specify when a specific script should run. The first office script requires ‘Pre Activation’. Select 'Pre Activation' and move to the next field.

  8. Click the browse icon to the right of this field and browse to the network location where the Office scripts were saved to in Part I. 

  9. Select the script named: FA1_W10-Office2013-2016-PrePlay.cmd

  10. Press ‘OK’ to add this script to the package.

  11. Click Add Script again.

  12. Select appdir-1 in the first dropdown.

  13. In the second dropdown select ‘Post Activation’ this time and move to the next field.

  14. Click the browse icon to the right of this field and browse again to the network location where the Office scripts were saved.

  15. Select the script named: FA2_W10-Office2013-2016-PostPlay.cmd

  16. Press ‘OK’ to add this script to the package.
  17. Click 'OK'. The Office DIA package is now complete and can be selected for playback within the ProfileUnity web console or FPC.



Additional Related KBs:


If after DIA deployment you see this error...


Possible solution:

Repackage office using the above steps and add the following before closing the package.

with this command.

  • PatchRegCleanup-x64 {90160000-0116-0409-1000-0000000FF1CE}

You could also try and run as an extend to the package. 




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


Article is closed for comments.