Base Image Script Framework (BIS-F) 6.1.0 BETA available

Automation, BIS-F, Citrix, Citrix AppLayering, Powershell, Provisioning Server

Base Image Script Framework (BIS-F) 6.1.0 BETA available

Updated, 19.10.2017 Matthias Schlimm

Hi Folks,

after some long weeks with the BIS-F 6.1.0 TEST build 03.x and very great feedback from the community, we are happy to release the BETA 6.1.0 build 02.x today. Many new features in this release , please read and download below

What’s new in BIS-F 6.1.0


Version 6.1.0 build 02.103 — 19.10.2017 12:13:13 :
19.10.2017 MS: Bugifx: defrag select the the right vDisk on the custom UNC-Path or the direct convertion
19.10.2017 MS: MSMQ show in Console Front instead SubMsg
Version 6.1.0 build 02.102 — 19.10.2017 09:03:00 :
17.10.2017 MS: Feature Add Offline VHD Defrag on custom unc path, thx to Dennis Span
17.10.2017 MS: Bugfix Running Office ream first and second OS rerarm, thx to Bernd Baedermann
17.10.2017 MS: Feature: ADMX change RES to ivanti Automation, thx to Chris Twiest
17.10.2017 MS: Feature: ADM extension PVS Target Device: select vDisk Type VHDX/VHD that can be using for P2PVS only, thx to Christian Schuessler
16.10.2017 MS: Bugfix Errorhandling – script will stop now after -Type E for Write-BISFLog
16.10.2017 MS: Bugfix Applayering, check if the Layer finalize is allowed before continue, thx to Brandon Mitchell
16.10.2017 MS: Bugfix OS rearm never run, path to slmgr.vbs must be entered before, thx to Bernd Baedermann
16.10.2017 MS: Bugfix detecting wrong POSH Version if running BIS-F remotly, using $PSVersionTable.PSVersion.Major, thx to Fabian Danner
15.10.2017 MS: Feature – AV-SEP.ps1: VIETool – using custom searchfolder from ADMX if enabled
03.10.2017 MS: Bugfix 214: SCOM Preparation – Test path if $OpsStateDirOrigin before delete, instead of complete C: content if if $OpsStateDirOrigin is not available
03.10.2017 MS: Bugfix 215: Personalization – writing wrong PersState to registry, preparation does not run in that case, thx to Ewald Bracko

  • select vDisk Format (vdh or vhdx) 
    • With PVS LTSR 7.6 you can only use vhd format, this can be selected in the ADMX for the Citrix PVS Traget Device. NOTE: vhd/vhdx can only be used with P2PVS, with ImagingWizard using vhdx only and ignore the ADMX settings
  • Offline VHD(X) Defragmention
    • If Custom UNC Path for PVS vDisk is selected, the vhd(x) will be mounted after convertion (with cvhdmount.exe),defrag it and unmount it (defrrag must be enabled in ADMX first)
  • edocs online:
    • with Version 6.1.0 we has removed the inline PDF Admin Guide, the complete Documentation is available in the future through  Please Note: In the next weeks we prepare the documentation for the new release, this will be available with the BIS-F 6.1.0 PROD 01.x Release (planned end of october), in the meanwhile the online documentation is password protected and not public available.
  • Citrix AppLayering Support
    • BIS-F detect the different Layer like OS Layer and Application/Platform Layer and do sometimes different based on Layers.
    • General: with AppLayering the redirection to the WriteCacheDisk will be skipped, also the PVS ImagingWizard / P2PVS.
    • OS-Layer: Windows Update Service enabled only on this layer
  • Create PVS vDisk on UNC-Path
    • ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > Citrix > Configure Citrix PVS Target Device > Enable P2V Custom UNC-Path and enter it below (the path must be exist and accessible, BIS-F does not create the folder)
  • Windows Defender Support
    • Detect Windows Defender and running FullScan
  • F-Secure Support
    • Detect F-Secure AntiVirus and running FullScan
  • Citrix PVS: redirect and clear all Eventlogs
    • on preparation and personalization all Windows Eventlogs will be redirected to the PVS WriteCacheDisk, during preparation only the Eventlogs will b cleared
  • UEFI and Legacy Support
    • in the ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > Citrix > Configure Citrix PVS Target Device > P2P Tool
      • you can select ImagingWizard or P2PVS. If you has P2PVS selected and running UEFI an automatic failover to ImagingWizard will be executed from BIS-F
      • GPT Support for WriteCacheDisk
  • Citrix WEM AgentCache Refresh on startup
    • on personalization, the netlogon and WEM service will be stopped and the WEM AgentCache refresh runs, after that the Netlogon and WEM Agent service starts
  • PrinterLogic Support
    • Delete PrinterInstaller Logfile in path C:\Windows\Temp\PPP on preparation
  • vmOSOT – select Template
    • ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > 3rd Party Tools > VMware OS Optimization Tool.
      • Custom Search Folder: You can also enter an custom searchfolder, e.g. c:\windows\system32, if you do not configured or disable the custom searchfolder option, the standard BIS-F Folders will be used.
      • Template Name: Enter the complete path to the the Template that would be used during optimization, e.g. c:\temp\mytemplate.xml, if nothing is specified the template for the running OS will be used.
  • Citrix Optimizer Support.
    • ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > Citrix >Configure Citrix System Optimizer (CTXOE).
      • 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 CTXOE 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, CTXOE will execute all available setting groups.
        To run CTXOE in analyze-only mode, check “Mode: Analyze only”.
      • Prerequisites: CTXOE 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.
  •  Log Retention period
    • ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > Global > Configue Logging.
      • You can select the log retention period (default: keep the last 5 logs)
  • Delete or display Ghost devices
    • ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > Microsoft > Ghost Devices (you will find 3 policies to configure)
      • Operations 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.   .
  • Citrix Broker Service Delay
    • ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > Citrix >VDA Configuration
      • enable 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 Desktop Service will 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.
  • Personalization based on DiskMode
    • ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > Global > Configure Personalization
      • Skip Personalization based on DiskMode, you can select a DiskMode to skip the Device Personalization on computer startup.
        > None – never skip the Device Personalization
        > ReadWrite – if the Image is in Private Mode (PVS or MCS) skip the Device Personalization
        > All – ignore all DiskMode’s and skip the Device Personalization
  • 3rd Party Tools, custom install path
    • ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > 3rd Party Tools
      • enable and enter the custom install path, where the 3rd Party Tool is installed, you can configure individual for each 3rd Party Tool
  • Configure Folders
    • ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > Global > Configure Folders
      • You can enter a custom foldername for the redirection of the EventLogs and Spool, this will be happen, if the Citrix PVS Target Device Driver is installed and the redirection through BIS-F is active.
  • Shared Configuration
    • ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > Global >Shared Configuration
      • Export the BISF CLI commands, that would be set from the complete BIS-F policy to an xml file. This can be used for compiuters that’s running in workergroup (like Citrix AppLayering) or you have no access to modify the Active Directory Group Policies.You can enter an UNC or local path, that can be accessed from the computer (if it’s running in workgroup mode and you have entered an UNC-Path, please set NTFS Rights to Everyone Read to get the xml file without prompt)1. Running Powershell with administrative privileges
        2. cd <BIS-F Installation folder>\Framework
        3. .\PrepBISF_Start.ps1 -ExportSharedConfiguration
        4. the xml files would be created, in the path that you’ve entered in this policy
        5. Copy BISFSharedConfig.xml to the <BIS-F Installation folder>
        6. If BIS-F is running, it reads the XML BISFSharedConfig.xml and get the path to the shared configuration, import these settings into the local policy and load the values into BIS-F.
  • RES Automation Agent Service
    • ADMX Computer Configuration > Administrative Tools > Base Image Script Framework (BIS-F) > RES > Disable RES ONE Automation Agent Service
      • In preparation if BIS-F is executed from RES Automation Agent it’s not possible to stop the service itself, with this ADMX setting you can control the service during preparation


[Download not found]


Matthias Schlimm | | Founder Base Image Script Framework (BIS-F) | IT-Architect EUC | Automation Enthusiast

  • Avatar
    Ewald Bracko says:

    Please fix the “PersFinished” -> “Finished” issue. Actually the scripts aren’t continuing until I add “Finished” instead of “PersFinished” into the LIC_BISF_PersState value. I think you showed this in the Webinar about 2 weeks ago…

    October 2, 2017 at 02:26
    • Matthias Schlimm

      this would be fixed in the latest Beta, that’s now available here

      October 2, 2017 at 12:23
      • Avatar
        Ewald Bracko says:

        If you refer to BIS-F 6.1.0 BETA build 02.101: This one doesn’t have the fix – at least not on a Win 1012 R2 image. I tried that out earlier today.
        However, if you refer to a newer build that should become available soon I’ll be pleased to test it out as soon as it becomes available.

        October 2, 2017 at 14:19
      • Matthias Schlimm

        In BIS-F 6.1.0 BETA we using this 4 States $Global:TaskStates= @(“AfterInst”,”AfterPrep”,”Active”,”Finished”). The State Finished will be set in PersBISF_Start.ps1 line 131 – 133. Please send us the BISF Personalization log or the complete BISFLog Folder through the BIS-F Form on

        October 2, 2017 at 16:57
  • Avatar
    Ewald Bracko says:

    Unfortunately I have no log for PersBISF_Start.ps1.
    However, have a look at the lines 100 up to 110 there. It seems the script writes “PersFinished” instead of “Finished” into the registry value LIC_BISF_PersState.
    As the other script PrepBISF_Start.ps1 seems to expect “Finished” as condition to continue it stays in an endless waiting loop because it never gets that condition.

    October 3, 2017 at 01:40
    • Matthias Schlimm

      boah.. thank you, seen this now. Thanks for your great help, will fix that

      October 3, 2017 at 08:40
      • Avatar
        Ewald Bracko says:

        You’re always welcome.
        Maybe you will release another BETA version anytime soon?

        October 3, 2017 at 10:36
      • Matthias Schlimm

        We are working now on some fixes. In the menawhile I can send you a private fix for further testing, you must replace the single script only

        October 9, 2017 at 10:18
      • Matthias Schlimm

        Updated BIS-F Beta today to fix some issues

        October 19, 2017 at 10:51
  • Avatar

    Hi Matthias and all other BIS-F developers.

    Since BIS-F 4.x I noticed that the OS rearm is not working correctly. My PVS Target Devices have the same KMS CMID. Please check the script 96_Prep_BISF_Rearm.ps1 at line 98. When you run cscript.exe within Powershell, you need to specify the complete path of your .vbs-script. Due to the //B argument of cscript.exe you didn’t get any error messages. Add the path of the slmgr.vbs to line 98 like this an it will work:
    cscript.exe //B $ENV:SystemRoot\SysWOW64\slmgr.vbs /rearm

    There is also a problem with the order of the execution of the functions RearmOS and RearmOffice. First you need to rearm Office after that the OS. If you rearm OS fist, then you get a error when running rearm OSPPREARM.exe for Office.

    Would be great when this can be fixed till next release.


    October 10, 2017 at 10:12
  • Avatar
    Ewald Bracko says:

    Are there still some issues which need to be fixed or can we expect the public release quite soon?

    November 22, 2017 at 20:10
Leave A Comment

48 + = 50

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.