Base Image Script Framework (BIS-F) 6.1

Microsoft

380 views January 28, 2019 June 29, 2019 Matthias Schlimm 0

Policy Description
Ghost Devices: Classes to exclude from removal Specifies the classes to be excluded from being removed by the ghost device removal tool.

To use this policy setting, click Enabled and enter the classes you want exlcuded, seperated by a semicolon “;”. For example: LegacyDriver;Net;SCSIAdapter.

The following is a list of classes:

1394

61883

1394Debug

Adapter

APMSupport

AVC

Battery

Biometric

Bluetooth

CDROM

Computer

Decoder

DiskDrive

Display

Dot4

Dot4Print

Enum1394

FDC

FloppyDisk

GPS

HDC

HIDClass

Image

Infrared

Keyboard

LegacyDriver

Media

MediumChanger

Modem

Monitor

Mouse

MTD

Multifunction

MultiportSerial

Net

NetClient

NetService

NetTrans

NoDriver

PCMCIA

PNPPrinters

Ports

Printer

PrinterUpgrade

Processor

SBP2

SCSIAdapter

SecurityAccelerator

Sensor

SideShow

SmartCardReader

Sound

System

TapeDrive

Unknown

USB

USBDevice

Volume

VolumeSnapshot

WCEUSBS

WPD

Important: Text is case sensitive.

This policy requires the Ghost device removal policy to be enabled in order to function.

If you disable this policy setting, or if you do not configure this policy setting, then the Ghost device removal will not filter by classes.

Ghost Devices: Friendly named devices to exclude from removal his policy allows you to specify devices by their friendly name to be excluded from being removed by the ghost device removal tool.

To use this policy setting, click Enabled and enter the friendly name of the devices you want exlcuded, seperated by a semicolon “;”. For example: Citrix;Intel(R) HD Graphics 5500;Generic USB Hub.

This policy works by doing a partial text search.  For instance, if you have the following devices:

Intel(R) USB 3.0 eXtensible Host Controller – 1.0 (Microsoft)

Mobile 5th Generation Intel(R) Core(TM) USB EHCI Controller – 9CA6

Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz

Then putting “Intel” will match all three of these devices.

This policy requires the Ghost device removal policy to be enabled in order to function.

If you disable this policy setting, or if you do not configure this policy setting, then the Ghost device removal will not filter by friendly name.

Ghost Device: Operation Mode Defines how the ghost device feature will operate.

This policy has three operation modes:

Remove ghost devices

List all devices without removal

List only ghost devices without removal

Remove ghost devices:

This option will enable the feature to execute device removal.  This function can be modified by enabling and configuring the two filter group policy options.  Enabling and configuring filtering by class or friendly name will exclude devices in those lists from being removed.

List all devices without removal:

This option will output all devices detected into the log without removing any devices.

List only ghost devices without removal:

This option will output ghost devices detected into the log without removing any devices.

   

If you enable this policy setting you must select a mode of operation.

If you disable or do not configure this policy setting then Ghost Device Removal won’t be executed.

Remove App-V Packages Delete AppV Pre-Cached packages on the Base Image

If you enable this policy setting, App-V Pre-Cached packages will be deleted .

If you disable this policy setting, App-V Pre-Cached packages will not be deleted.

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

Run Defrag This policy setting allows you to run a defrag on your base image disk (Citrix PVS or MCS) or your local system drive (VMware View or Microsoft Windows).

If you enable this policy setting, Defrag will be executed. If the Custom UNC-Path for the PVS Target Device is enabled and configured in BIS-F > Citrix > PVS Target Device Configurartion, defrag will be run on the vhd(x) on the custom unc-path (Offline Defrag Feature)

If you disable this policy setting, Defrag will not be executed.

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

Note: This setting affects the system drive only. It does not affect the write cache drive.

Enable RDP Session Support Enable Base Image Script Framework to be executed from an RDP Session

If you enable this policy setting, BIS-F can be executed from an RDP Session.

If you disable this policy setting, BIS-F can be executed in Console Session only.

If you do not configure this policy setting, BIS-F can be executed in Console Session only.

.NET Optimization Run .NET Optimization during sealing (preparation)

If you enable this policy setting, .NET Optimization is running during sealing

If you disable this policy setting, .NET Optimization is disabled during sealing

If you do not configure this policy setting, .NET Optimization is running during sealing

Rearm Microsoft Office once Run Microsoft Office rearm if needed

If you enable this policy setting, Microsoft Office rearm will be executed once if needed.

If you disable this policy setting, Microsoft Office rearm will not be executed.

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

Rearm Microsoft Windows once Run Microsoft Windows rearm if needed

If you enable this policy setting, Microsoft Windows rearm will be executed once if needed.

If you disable this policy setting, Microsoft Windows rearm will not be executed.

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

Rebuild performance counters Rebuild the Performance Counters. See CTX129350 or CTX127151 for further informations

If you enable this policy setting, Performance Counters will be rebuilded.

If you disable this policy setting, Performance Counters won’t be rebuilded.

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

Run Sysprep If No Image Management software such as Citrix VDA, Citrix PVS Target Device Driver, VMware View Agent, Citrix AppLayering Agent are detected, BIS-F will prompt to run Microsoft Sysprep at the end of the sealing process.

If you enable this policy setting, sysprep will be executed if no Image Management software is detected.

If you disable this policy setting, sysprep will not be executed.

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

Delete AllUsersStartMenu Delete AllUsersStartMenu content

If you enable this policy setting, AllUsersStartMenu content will be deleted.

If you disable this policy setting, AllUsersStartMenu content won’t be deleted.

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

WinSxS Optimization

 

Run WinSxS Optimization during sealing (preparation)

If you enable this policy setting, WinSxS Optimization is running during sealing
If you disable this policy setting, WinSxS Optimization is disabled during sealing
If you do not configure this policy setting, WinSxS Optimization is running during sealing

Execute WinSxS Optimization on BaseDisk only:
If you using Citrix PVS or MCS the WinSxS Optimization is running on the BaseDisk only, during a parent disk seal process the WinSxS Optimization is skipped.

Maximum Execution Timeout:
You can specifiy the maximum executio timeout for the WinSxS Optimization. default is det to 240 minutes, min. 60, max 480. you can increase/decrease the value in steps of 15 minutes. if this value is reached during the WinSxS Optimization the DISM Process is terminated.

About WinSxS:
The Windows component store (C:\Windows\winsxs) directory is used during servicing operations within Windows installations. Servicing operations include, but are not limited to, Windows Update, service pack, and hotfix installations.

The component store contains all the files that are required for a Windows installation. And, any updates to those files are also held within the component store as the updates are installed. This causes the component store to grow over time as more updates, features, or roles are added to the installation. The component store uses NTFS hard links between itself and other Windows directories to increase the robustness of the Windows platform.

Note: BIS-F 6.1.2 or higer required – ADMX must be replaced to use this feature !!

Was this helpful?

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close