Base Image Script Framework (BIS-F) 6.1

Policy

Description

If you enable this policy setting, Citrix Optimizer (CtxOptimizerEngine.ps1) will be executed. Optional you can define the name of a template that should be used during execution. If there is no template specified, BIS-F will search for an OS-specific default template. If there is no appropriate template available, the execution of Citrix Optimizer will be skipped.

It is also possible to define a list of GroupIDs (defined in the template) of setting groups that should be executed. The value must be a comma-separated string; e.g. “DisableServices,OptionalServices”. If there are no GroupIDs specified, Citrix Optimizer will execute all available setting groups.

To run Citrix Optimizer in analyze-only mode, check “Mode: Analyze only”.

If you disable this policy setting, Citrix Optimizer won’t be executed.

If you do not configure this policy setting, you’ll be prompted during the sealing process.

Prerequisites: Citrix Optimizer must be installed on the Base Image first (BIS-F will check the following locations: C:\Program Files, C:\Program Files (x86), C:\Windows\system32) or you can enable and define an custom searchfolder within this policy. Example: Copy the complete extracted Folder of the Citrix Optimizer Download to C:\Program Files (x86)\Citrix Optimizer.

New with 6.1.1: You can enter multiple Optimizer Templates with Commasperator, eg:

Citrix_Windows_10_1809.xml,PVS_Target.xml

Note: Do no use any space between !

New with 6.1.2: AutoSelect with Multiple Templates Support, see https://eucweb.com/kba/0107190500

New with 6.1.3 : TemplatePreFix Support, see https://eucweb.com/kba/1208191514

If you enable this policy setting, Citrix Personal vDisk inventory will be executed on VDI Clients only.

If you disable this policy setting, Citrix Personal vDisk inventory won’t be executed.

If you do not configure this policy setting, you’ll be prompted during the sealing process.

If you enable this policy setting, you must select the drive letter for the PVS WriteCacheDisk

If you disable or do not configure this policy setting and have PVS Target Device Driver installed, an error during BIS-F execution occurs.

P2V Tool:

You can choose between ImagingWizard and P2PVS (default = ImagingWizard)

vDisk Format:

Select the right vDisk Format, P2PVS support vhd and vhdx only, If you has selected ImagingWizard automatic vhdx will be choosen.(default = vhdx)

P2V Custom UNC-Path:

If you enable this policy, you must enter an valid UNC path. The user account, who start BIS-F for the preparation must have read/write access for this UNC-Path. The convertion process is starting with the P2V Tool you selected above.

The vDisk would be created in the VHDX Format with the name %Computername%-DateTime.vhdx, for example VM-XA7MASTER01-020817-1045.vhdx

Custom Arguments:

If you enable this policy, depends on the above configuration you can enter custom arguments, like C: only, example. if you choosing P2PVS the default arguments would be set to C: /Autofit /L, with the custom arguments you overwritten thie arguments.

Note: If you entered incorrect arguments, the convertion of the PVS vDisk might be failed !

If you do not enable, the default arguments inside BIS-F will be used.

If you enable this policy setting, you can configure several items

If you disable or If you do not configure this policy setting, the vda configuration would not performed

Delay Citrix Desktop Service:

The Citrix Desktop Service controls the registration state through the Citrix Controller. In some circumstances, this service has successfull registered the VM and the user can logged on to this, through Receiver/StoreFront. In the Backend some depend actions like Workspace Environment Agent, Group Policies, App-V Client and someone else are not completed with their own task. If you enable this policy the Citrix Destop Service would be started first, if the BIS-F personalization is finished.

Note: If you has the Device personalization configured to skip it on all DiskModes or on private Mode only, the Citrix Desktop Service would also be started.

If you enable this policy setting, the current XenApp server will be removed from the Farm and the local database information will be cleared.

If you disable this policy setting, the current XenApp server will not be removed from the Farm and the local database information will not be cleared.

If you do not configure this policy setting, you will be prompted during the sealing process.