[HOW TO] Citrix AppLayering in a dynamic Environment

Preparation:
BIS-F replaces need to run “Layer Finalize” running the following commands
Prepare AppLayering – List and remove unused network devices > UniService.exe -G
Prepare AppLayering – Check System Layer integrity > UniService.exe -L

BIS-F checks the results of the Layer integrity from the UniService Logfile, containing “Layer finalize is allowed”
before proceeding, otherwise BIS-F stops with an error message and you must check the log for further information, mostly a reboot is necessary to fix the issue.

The following table Shows the AppLayering Matrix.

With this above combinations, BIS-F can hande App- and Platform Layer different if needed

Outside ELM:
This reference to the following KB Article Citrix App Layering 4.x: PVS Connector (BootPrivate) 

DiskMode:
The DiskMode is a BIS-F own Feature, that are describes here

RunMode:
The App-Layering RunMode is getting from the Registry:
KEY_NAME=”HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\unifltr”
VALUE_NAME=RunMode

If both AppLayering & PVS Target Device driver are installed, BIS-F skips the conversion to PVS vDisk with P2PVS / ImagingWizard.

Personalization:
During BIS-F Personalization, triggered from BIS-F scheduled task created during Preparation, the current Layer will be detected:
In the OS-Layer the Windows Update Service will be started

Redirection Matrix:
The Return Code below will be written also to the BIS-F Logfile