Base Image Script Framework (BIS-F) 6.1

Base Image Script Framework (BIS-F) 6.1.0

Base Image Script Framework (BIS-F)
Author: Matthias Schlimm
Version: 6.1.0 build 01.100
Dated: 26 Nov 2017

1.Introduction

The Base Image Script Framework (BIS-F) is the perfect way to seal your Base Image. Whatever your environment has run Citrix XenApp, Citrix XenDesktop with PVS or MCS,  Citrix AppLayering, VMware Horizon View, you must prepare your Base Image before you can distribute this Image to multiple devices. If you install your Base Image from scratch or update them with new software, for the sealing process of your Base Image run this framework (preparation), it makes it also unique if you booting up your cloned device (personalization)

Out of the Box, BIS-F 6.1.0 optimize the following Products, if the Product is not installed in your environment, BIS-F do nothing with that (Ignore Mode):

Microsoft Optimizations

  • Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016
  • Windows 7, 8, 8.1, 10
  • Delete WSUS Client-ID
  • Delete WSUS SoftwareDistribution folder
  • Reset Performance Counters
  • Delete temp files with CCleaner (3rd Party CCleaner must be installed first)
  • Delete local profiles that are not required (3rd Party DelProf2)
  • Delete Windows event logs
  • Reclaim storage space on PVS WriteCache Disk (3rd Party SDelete needed)
  • Rearm Operating System once
  • Rearm Microsoft Office (2010, 2013, 2016) once
  • Delete DHCP Client information in registry
  • Defrag system disk
  • Delete AllUsers StartMenu
  • Disable IPv6 (3rd Party nvpsbind needed)
  • Add delay between time sync and GPO processing
  • Disable unneeded scheduled tasks
  • Pending Reboot detection
  • Grace Period Fix for RDS
  • .NET Optimizations
  • Delete Ghost devices
  • Detect UEFI or legacy boot
  • BIS-F logfie retention configured via ADMX
  • BIS-F control: the preparation is started after personalization first (POSH loop)

 

AntiVirus

  • Trend Micro
  • Symantec Endpoint Protection (3rd party vietool needed)
  • McAfee VirusScan Enterprise
  • Microsoft EndPoint Security Client
  • Kaspersky AntiVirus
  • Sophos AntiVirus
  • Microsoft Defender
  • F-Secure

 

Electronic Software Deployment (ESD)

  • Microsoft SCCM Agent
  • Novell ZCM Agent
  • Altiris Deployment Agent
  • Matrix42 Agent
  • Heat DSM (prev. NetInstall)

 

Application Virtualization

  • FSLogix
  • Microsoft App-V Client
  • Ivanti AppSense
  • Ivanti / RES Automation Agent
  • Ivanti / RES ONE Automation Console
  • Ivanti / RES ONE Automation
  • Ivanti / RES ONE Service Store Client Service
  • Turbo.net

 

System Monitoring

  • Microsoft System Center Operations Manager Agent
  • Splunk Universal Forwarder
  • uberAgent

 

Citrix

  • Citrix XenApp 6.x (IMA)
  • Citrix XenApp/XenDesktop 7.x (FMA)
  • Citrix Machine Creation Service (MCS) 7.x
  • Citrix Provisioning Server Target Device Driver (PVS) 5.6 – 7.x
  • Convert direct attached vDisk
  • Convert to UNC-Path
  • Offline Defrag, mount vDisk from UNC-Path
  • Select ImagingWizard or P2PVS in ADMX
  • Select vDisk Type VHD or VHDX in ADMX
  • Format automatically the Citrix WriteCache Disk once
  • XenDesktop Personal vDisk (PvD) Inventory Update (Windows 7, 8.x, 10 only)
  • Fix for MSMQ Service (required for Session Recording)
  • Reset Citrix Application Streaming offline database
  • Delete Citrix Streaming Cache (RadeCache)
  • Delete Citrix Profile Management cache
  • Delete Citrix EdgeSight client data
  • Citrix Environment Management Agent (WEM) configure Cache
  • Citrix System Optimizer
  • Delay Citrix Desktop Service
  • Citrix AppLayering Support
    • Detect different Layer (OS-Layer / Platform & Application Layer)
    • Detect if Image is running outside ELM
    • Windows Update Service running in OS –Layer only

 

VMware

  • VMware Horizon View detection
  • VMware OS Optimization Tool (vmOSOT)
  • ADMX: Inatallation path and custom Template can changed in ADMX
Yes No
Last updated on November 26, 2017
4 of 4 users found this section helpful

1.1.Authors and Developers

Matthias Schlimm | IT-Architect | Citrix CTA | Founder BIS-F | Login Consultants Germany GmbH
Mike Bijl | Senior Consultant | Login Consultants Nederland B.V
Florian Frank | Junior Consultant | Login Consultants Germany GmbH
Jonathan Pitre | Consultant | Citrix CTA | Morgan Stanley
Trentent Tye | Senior Virtualization Administrator | Citrix CTA | Microsoft MVP for AppV/RDS | Alberta Health Service

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

1.2.Developer Slack Channel

For BIS-F it’s also a Slack Channel available, you can join it by sending us a mail to register in the BIS-F Developer Channel. click here to send us a Mail to register in the slack channel

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

2.License terms

Copyright (c) 2017 eucweb.com & Login Consultants

 

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Yes No
Last updated on November 26, 2017
1 of 1 users found this section helpful

3.What's new

  • For each 3rd Party Tool you can specify a custom path in the ADMX
  • IF Citrix Optimizer (CTXO) or VMware OS Optimization Tool (vmOSOT) is executed and configured with the ADMX, opimizations as describes here are not executed
  • .NET Optimization can be enabled/disable in ADMX
  • P2PVS Tool P2PVS or ImagingWizard can be selected in ADMX
  • vDisk Extension vhd or vhdx can be selected in ADMX
  • specify the Name for the spool and Eventlog Folder in ADMX
  • Custom UNC Path for PVS vDisk can be entered in ADMX
  • Citrix AppLayering: The Layer will be detected and control the service like WSUS in OS-Layer only
  • Offline Defrag of the PVS vDisk on the custom UNC-Path
  • Detect UEFI or Legacy BIOS to select the right commandline Switches for P2PVS/ImagingWizard
  • IF BIS-F is starting remotly, the right POSH Version from the remote Session will be detected
  • Ivanti Automation: Stop the Service can be controlled in ADMX
  • BIS-F Preparation waiting for the personalization if finished before continue
  • Redirect all Windows Eventlogs to the PVS WriteCacheDisk
  • Clear all Windows EventLogs during preparation
  • Citrix Desktop Service Delay can be controlled in ADMX
  • Custom Arguments for P2PVS / ImagingWizard can be enabled and configured in ADMX
  • Log Retention Period can be configured in ADMX
  • Ghost Devices can be controlled and configured to remove in ADMX
  • Support for PrinterLogic PrinterInstaller Client
  • BIS-F personalization can be controlled and skipped in ADMX
  • Support for F-Secure Anti-Virus
  • VMware OS Optimization Tool, specify template to use in ADMX
  • Support for Citrix Optimizer (CTXO)
  • Trend Micro OfficeScan: OfficeScan (OSCE) Agent or WFBS-SVC (Worry-Free Business Security Services icon will be removed in the system tray. Updated ini file and delete run value as per https://success.trendmicro.com/solution/1102736
  • Support for Windows Defender
  • Office and Operating System Rearm State will be logged in BIS-F log
  • With BIS-F uninstaller, the BIS-F schedule Task will be removed also

 

 

Yes No
Last updated on November 26, 2017
6 of 6 users found this section helpful

4.Known Issues

The complete List for all Bugs, Issues or Features official available on Github https://github.com/EUCweb/BIS-F/issues. If you identify a Bug, Issue or will send us a Feature Request, let us known here

 

Yes No
Last updated on March 13, 2018
5 of 5 users found this section helpful

5.Release Notes

Release Notes from Version 6.1.0 (all Stages)

The complete Release Notes are available in the Installation root Folder of BIS-F

Version 6.1.0 build 01.100 — 26.11.2017 22:34:40 :
26.11.2017 MS: ADMX: change Category Ivanti Automation to Ivanti
24.11.2017 MS: 10_PrepBISF_AV-SEP.ps1 – Change Name in Log and Display from VIEtool.exe to Symantec Virtual Image Exception (VIE) Tool
22.11.2017 JP: Fixed spelling and grammar errors in AMDX, AMDL files
22.11.2017 JP: Added XML tag in ADMX, ADML files
21.11.2017 MS: If Error appears, exit script with Exit 1
15.11.2017 MS: Bugfix: on the Mounted Disk, the same UniqueID must be set to fix boot record issues (https://blogs.technet.microsoft.com/markrussinovich/2011/11/06/fixing-disk-signature-collisions/)
15.11.2017 MS: Feature 216: during uninstall of BIS-F, the schedule task is deleted also
11.11.2017 MS: Bugfix: show the right Eventlog during move to the WCD
11.11.2017 MS: Bugfix: Retry 30 times if Logshare on network path is not found with fallback after max. is reached
10.11.2017 MS: Feature: .NET Optimization controled in ADMX, Category Microsoft
09.11.2017 MS: Feature: support now for Office x64 and x86, Read Office Installationpath from regisrty instead of hardcoded Filepath
07.11.2017 MS: add $LIC_BISF_3RD_OPT = $false, if vmOSOT or CTXO is enabled and found, $LIC_BISF_3RD_OPT = $true and disable BIS-F own optimizations
03.11.2017 MS: Feature: Function Use-BISFPVSConfig –  if PVS Target Device Driver not installed, write info to BIS-F log and set the value $Global:Redirection=$true; $Global:RedirectionCode=”NoPVS”
03.11.2017 MS: Feature: Function Get-BISFBootMode – writing BootMode (UEFI or Legacy) in Function to BISF log
02.11.2017 MS: Bugfix: if booting up in private Mode the vhdx and custom unc-path for P2V is configured, defrag runs on the UNC-Path and not on the BaseDisk itself.
01.11.2017 MS: Feature Preparation: get detailed OS License Information and write them to the BIS-F Log
01.11.2017 MS: Feature Preparation: Office Rearm state writes to BIS-F Log
01.11.2017 MS: Feature Personalization – get Office activation state and License state back to the BIS-F log
01.11.2017 MS: check if Defrag Service is running, thx to Lejkin Dmitrij
29.10.2017 MS: Bugfix: IF $DiskNameExtension -eq “noVirtualDisk” and custom UNC-Path is enabled, runnig OfflineDefrag on custom UNC-Path
29.10.2017 MS: Replacing DiskMode MCS with VDA value
29.10.2017 MS: Bugfix AppLayering, Outside ELM no UniService must be running
29.10.2017 MS: Bugfix: Custom UNC-Path get the wrong value back and does not perform a defrag on the vhd(x) and set the right value now $Global:TestDiskMode
———————————
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
———————————
Version 6.1.0 build 02.101 — 22.09.2017 14:05:59 :
22.09.2017 MS: bugfix 00_PersBISF_WriteCacheDisk.ps1 – change reboot command to use shutdown /r instead of restart-computer
———————————
Version 6.1.0 build 02.100 — 22.09.2017 10:14:04 :
21.09.2017 MS: Bugfix – Central logshare enabled for preparation also
21.09.2017 MS: fix some typos
21.09.2017 MS: Feature: RES Automation Agent Service could be controlled from ADMX
21.09.2017 MS: Feature: CMTrace – using custom searchfolder from ADMX if enabled
14.09.2017 MS: bugfix 212 – if personlity.ini not exist, run Set-PVSTool otherwise check vDiskMode
14.09.2017 MS: after WriteCacheDisk would formatted during personlization, wait after reboot
12.09.2017 MS: Invoke-CDS Changing to $servicename = “BrokerAgent” to control the delay of the Service
———————————
Version 6.1.0 build 03.106 — 12.09.2017 16:39:00 :
12.09.2017 MS: using progressbar during wait for the personlization is finished
12.09.2017 MS: Using Array in Initialize-BISFConfiguration $Global:TaskStates= @(“AfterInst”,”AfterPrep”,”Active”,”Finished”) instaed of hardcoded values
———————————
Version 6.1.0 build 03.105 — 11.09.2017 23:34:37 :
11.09.2017 MS: Feature: Controlflag for preparation to run it after the personalization is finished first
11.09.2017 MS: change sleep timer from 5 to 20 seconds after time sync on startup
11.09.2017 MS: Bugfix – Delay Citrix Desktop Service must be stopped also
11.09.2017 MS: WEM AgentCacheRefresh can be using without the WEM Brokername specified from WEM ADMX
———————————
Version 6.1.0 build 03.104 — 11.09.2017 14:24:41 :
11.09.2017 FF: add missing function name for Invoke-Service
———————————
Version 6.1.0 build 03.103 — 10.09.2017 21:46:34 :
10.09.2017 MS: Feature 211 – VDA Configuration (ADMX) – Delay Citrix Desktop Service, start this Service after personalization is finished
08.09.2017 FF: Feature 182 – Windows Defender Signature will only be updated if Defender is enabled to run
01.08.2017 JS: Bugfix 205 – 10_PersBISF_AV-TM.ps1 – Added the TmPfw (OfficeScan NT Firewall) service to the array
01.08.2017 JS: Bugfix 205 – 10_PrepBISF_AV-TM.ps1 – Updated ini file and delete run value as per https://success.trendmicro.com/solution/1102736
This should be implemented for both RDS and VDI workloads, especially if using published
applications, as it prevents the PccNTMon.exe process from running in user sessions, which
means that the OfficeScan (OSCE) Agent or WFBS-SVC (Worry-Free Business Security Services)
icon is unavailable in the system tray.
Added the TmPfw (OfficeScan NT Firewall) service to the array.
20.08.2017 JS: Bugfix 205- 10_PrepBISF_AV-TM.ps1 – I found that the services were not being stopped and set to manual, so added a new TerminateProcess
function and modified the StopService function to make it reliable.
———————————
Version 6.1.0 build 03.102 — 06.09.2017 15:05:26 :
06.09.2017 MS: Feature 204 – replacing AdminGuide.pdf with Online eDocs http://edocs.eucweb.com
06.09.2017 MS: Feature 203 – ADMX – Custom Arguments for P2PVS / ImagingWizard
05.09.2017 TT: bugfix 201  – enable maximumExecutionTime in Write-BISFProgressBar, if not specified the default value of 60 minutes would be set
04.09.2017 MS: bugfix – Eventlogs would be moved for both States (Prep and Pers) now, after changing it in V6.1.0 build 03.101
31.08.2017 MS: POSH Progressbar, sleep time during preparation only, change it from 10 to 5 seconds
31.08.2017 MS: change sleep timer from 60 to 5 seconds after time sync on startup
———————————
Version 6.1.0 build 03.101 — 31.08.2017 19:00:00 :
31.08.2017 MS: Bugfix – Eventlogs would be moved during Preparation only, this saved time during personalization
31.08.2017 MS: Clear all Eventlogs
25.08.2017 MS: Bugfix – P2V with UNC Path failed with space is in UNC Path
25.08.2017 MS: Bugfix – VHDX on UNC-Path would be created with double .vhdx extension
———————————
Version 6.1.0 build 03.100 — 24.08.2017 13:55:53 :
24.08.2017 MS: If AppLayering is installed and running not inside ELM, the VM is build first time, run defrag on systemdrive
24.08.2017 MS: if OS and Platform/Appliaction Layer not detected, VM is not running inside ELM, give back $GLobal:CTXAppLayerName=”No-ELM”
24.08.2017 MS: Bugfix: after restart WEM Agentservice, Netlogon must be started also
23.08.2017 JP: Fixed typos in the ADMX/AMDL file, optimized folder structure, removed duplicated definition (WindowsVista)
22.08.2017 MS: Feature Request – 97_PrepBISF_PRE_BaseImage.ps1 – cleanup various directories, like temp, thx to Trentent Tye
22.08.2017 MS: BugFix – create or update BIS-F schedule Task to run with highest privileges
22.08.2017 MS: If defrag not run, write-out the DiskMode to the BIS-F log for further anlaysis if possible to run
———————————
Version 6.1.0 build 04.113 — 18.08.2017 16:38:46 :
18.08.2017 FF: (PERS Sophos) Use $ServiceNameS instead of $ServiceName for first Test-BISFService
18.08.2017 FF: Fix for Bug 200: Popup shouldn’t show up if Central Logshare is enabled OR disabled
17.08.2017 FF: Program is named “Windows Defender”, not “Microsoft Windows Defender”, fixed typos
———————————
Version 6.1.0 build 04.112 — 16.08.2017 13:47:45 :
Last Change: 16.08.2017 MS: Skip Device Personalization, based on Diskmode selected in ADMX
Last Change: 15.08.2017 MS: Feature – DiskMode: extend Diskmode with AppLayering, ReadOnlyAppLayering, ReadWriteAppLayering, etc.
Last Change: 15.08.2017 MS: Bugfix – Personalization: If Citrix AppLayering is installed, skip reboot
Last Change: 15.08.2017 MS: move all BIS-F logs to the BISF logfolder, local and UNC-Path, previous only personalization logs would be moved to the UNC-Path
Last Change: 06.08.2017 MS: from every P2V convertion, the logfile would be included into the BIS-F log, instead of error only
Last Change: 06.08.2017 MS: Bugfix – ADMX: in some textbox fields, they starting with empty spaces
Last Change: 06.08.2017 MS: Bugfix – if Custom UNC-Path in ADMX is enabled, during “Personalization” the wrong $returnvalue like MCSPrivate is given back, instead of “UNC-Path”
———————————
Version 6.1.0 build 04.111 — 04.08.2017 21:23:17 :
04.08.2017 MS: Feature Request 150 : – Function Get-BISFDiskMode: If Custom UNC-Path in ADMX is enabled, get back ‘UNC-Path’ as $returnvalue
03.08.2017 MS: Change BIS-F Icon on Admin Desktop, thx to Marco Zimmermann
03.08.2017 MS: Feature – P2V : Get-BISFBootMode get back UEFI or Legacy to using different command line switches for ImagingWizard or P2PVS
03.08.2017 MS: Feature – P2V : Automatic fallback to ImagingWizard with UEFI BootMode, if P2PVS in ADMX is selected
02.08.2017 MS: Feature – System Startup : In AppLayering OS-Layer only, do not Resync Time with Domain and do not Reapply Computer GPO, Computer is mostly not domain joined
02.08.2017 MS: Feature – System Startup : With DiskMode AppLayering in OS-Layer the WSUS Update Service would be start
02.08.2017 MS: Feature Request 150 : IF ADMX for custom VHDX UNC-Path is enabled, Defrag can’t performed
02.08.2017 MS: Feature Request 150 : IF ADMX for custom VHDX UNC-Path is enabled, the arguments for the P2V Tool must be changed, this vDisk Mode must not being checked
02.08.2017 MS: Feature – Removing XenConvert completly and using settings from new ADMX to choose ImagingWizard or P2PVS
02.08.2017 MS: Feature Request 152 : ADMX – Set Logfile Retention via ADMX
02.08.2017 MS: Feature Request 193 : ADMX – Eventlog and Log Configuration, change POSH Code to use new reg values
02.08.2017 MS: Feature Request 196 : ADMX – delprof2 edit custom arguments
02.08.2017 MS: Feature : change ADMX to new structure, each vendor has his own folder
02.08.2017 MS: Bugfix – Windows Defender Script: to much ” at the end of Line 44, breaks defender script to fail
———————————
Version 6.1.0 build 04.110 — 01.08.2017 19:13:38 :
01.08.2017 MS: Feature Request 197 : add Progressbar for .NET Optimization
01.08.2017 MS: Feature Request 159 : ADMX – specifiy VMware OS Optimization Template
01.08.2017 MS: Feature Request 196 : ADMX – specifiy custom searchfolder for Citrix System Optimizer (CTXOE)
01.08.2017 MS: Feature Request 196 : ADMX – specifiy custom searchfolder for each 3rd Party Tool
01.08.2017 MS: Feature Request 193 : ADMX – specifiy custom eventlog and spool foldername
01.08.2017 JP: Fix some typos
———————————
Version 6.1.0 build 04.109 — 01.08.2017 05:38:40 :
01.08.2017 MS: Bugfix Test-AppLayeringSoftware, to much more bracket.. complete execution of BISF failed !
———————————
Version 6.1.0 build 04.108 — 31.07.2017 20:10:25 :
31.07.2017 MS: Bugfix: if Citirx PVS Target Device Driver and Citrix AppLayering is installed, PostCommand would not executed
31.07.2017 MS: Bugfix: If Citrix AppLayering is installed, in the Platform Layer the wrong Driveletter would give it back.
31.07.2017 MS: Bugfix: 10_PrepBISF_AV-SEP.ps1 – typo in search folders for the SEP vietool.exe
31.07.2017 MS: Show ConsoleMessage during prepare Citrix AppLayering if installed
———————————
Version 6.1.0 build 04.107 — 29.07.2017 13:10:21:
29.07.2017 MS: add schedule Task “ServerCeipAssistant” to disable, thx to Trentent Tye
29.07.2017 MS: Feature Request 173: add Support for F-Secure Anti-Virus, thx to Thorsten Witsch
29.07.2017 MS: Feature Request 174: on systemstartup with MCS/PVS and installed WEM Agent – refresh WEM Cache
29.07.2017 MS: Feature Request 168: add Support for PrinterLogic PrinterInstaller Client to remove all files in C:WindowsTempPPP
29.07.2017 MS: Feature Request 179: Enable all Eventlog and move Eventlogs to the PVS WriteCacheDisk if Redirection is enabled in function Use-BISFPVSConfig , thx to Bernd Braun
29.07.2017 MS: Bugfix 187: Wrong search folders for the SEP vietool.exe
29.07.2017 MS: Feature Request 192: support GPT WriteCacheDisk
———————————
Version 6.1.0 build 04.106 — 28.07.2017 21:12:09:
28.07.2017 MS: Bugfix 195: If Citrix AppLayerLayering is installed get back DiskMode $returnValue = “AppLayering”
———————————
Version 6.1.0 build 04.105 — 27.07.2017 21:51:23:
27.07.2017 MS: If Citrix AppLayering and PVS Target Device Driver installed, skip vDisk Operations
27.07.2017 MS: replace redirection of spool and evt-logs with central function Use-BISFPVSConfig, if using Citrix AppLayering with PVS it’s a complex matrix to redirect or not.
27.07.2017 MS: add new Function Use-BISFPVSConfig for Checking Redirection of Files is needed in combination with PVS and Citrix AppLayering
26.07.2017 MS: Bugfix Citrix Applayering: check Universervice ProcessID instead of ProcessName
———————————
Version 6.1.0 build 04.104 — 25.07.2017 20:14:08:
25.07.2017 MS: Bugfix: Create central Function Test-BISFAppLayeringSoftware to give back $Global:CTXAppLayeringSW true or false value
25.07.2017 MS: Feature Request: with new Installerbuild (incremental version) in each DTAP Stage the build number also written to the log and the Windows Title, replace the manual change of the $ReleaseType in BISF.psm1
———————————
Version 6.1.0 DEV:
12.07.2017 FF: Prep_Altiris: Create $RegKeys as an array (was a hashtable before)
12.07.2017 FF: Prep_RES: BugFix for Redirecting RES Cache (Setting Cache Path to WCD)
03.07.2017 FF: CTXOE can be executed on every device (if “installed” + not disabled by GPO/skipped by user)
01.07.2017 MS: add Script to remove ghost devices, thx to Trentent Tye
28.06.2017 MS: Feature Request 169 – add AppLayering Support in PrepBISF_CTX.ps1
16.06.2017 FF: Feature Request 181 – add support for Citrix System Optimizer Engine (CTXOE)
28.06.2017 MS: Bugfix 186 – AppSense Product Path – thx to Matthias Kowalkowski
14.06.2017 MS: Feature Request 176 – Running ImagingWizard instead of P2PVS to support UEFI Boot on Hyper-V
14.06.2017 MS: Feature Request 172 – Stopping Shell Hardware Detection Service before ImagingWizard/XenConvert is starting, messagebox to format the disk supressed now
01.06.2017 FF: Feature Request 182 – Add 10_PrepBISF_AV-WindowsDefender.ps1 to support Windows Defender

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

6.Download BIS-F

To get a copy of BIS-F please do it as follows:

  • Up to the BETA Release (DEV build 04.nnn, TEST build 03.nnn, BETA build 02.nnn) go to http://eucweb.com
  • every public Release (build 01.nnn) of BIS-F available here
Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

7.Installation

Beginning with version 6.0.0 BIS-F can be installed with a Setup Installer – even silently. You must remove any previous Installation of BIS-F (Version 5.1.2 and earlier) manually, if installed on the system.

Note: BIS-F does not distribute any 3rd Party tools like CMtrace, sdelete, CCleaner, delprof2, VMware OS Optimization Tool, Symantec VIE tool, nvpsbind. BIS-F detect this tools automatically in the following folders and subfolders C:\program files, c:\program files (x86), c:\windows\system32 on your Base-Image or you can enter a custom searchpath for each 3rd Party Tool in the BIS-F ADMX.

Yes No
Last updated on November 26, 2017
1 of 1 users found this section helpful

7.1.Update from earlier Versions

Update from BIS-F 5.x

IF you update BIS-F from earlier Version, prior V.6.x you must manually remove the older Version (e.g. C:Scripts), keep a backup of your custom scripts and copy them back to the new custom folder of the new BIS-F Version.

Update from BIS-F 6.x

If you have V.6.x or later installed, you can simplify run the installer, it keeps automatically your custom scripts during update. It’s necassary the ADMX match to the BIS-F Version.

 

Yes No
Last updated on November 26, 2017
1 of 1 users found this section helpful

7.2.Silent Installation

The installer can be run in silent mode also, just execute the following command:

Setup-BIS-F-*.exe /SILENT /log=”C:WindowsLogfilesBIS-F.log”

the complete command line switches that can be used, can you see here

Yes No
Last updated on November 26, 2017
2 of 2 users found this section helpful

7.3.Manual Installation

Run the setup-BIS-F-*.exe

The manual installation is very simple, accept the EULA and click next through the installer.

 

Yes No
Last updated on November 26, 2017
1 of 1 users found this section helpful

8.Configure

If you run the Base Image Script Framework and does not configure it with the ADMX the following message appears.

 

 

 

 

 

 

Yes No
Last updated on November 26, 2017
2 of 2 users found this section helpful

8.1.ADMX Configuration

For full automation, please copy the content of the ADMX Folder from the Base Imae Script Framework Installation to the central store of the PolicyDefinitions. It’s necassary the ADMX match to the BIS-F Version.

e.g. <YourDomain> sysvol<YourDomain>PoliciesPolicyDefinitions

Now you can configure the BIS-F automation with Group Policies.

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

8.1.1.3rd Party Tools

To use any of this 3rd Party Tools, this must be installed on your Base Image first

Policy Description
Run CCLeanerRun CCleaner on Base Image

If you enable this policy setting, CCleaner will be executed.
If you disable this policy setting, CCleaner won't be executed.
If you do not configure this policy setting, you'll be prompted during the sealing process.

Prerequisites: CCleaner must be installed on the Base Image first

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 would be used.
Enable CMTraaceCMTrace Logfile viewer

If you enable this policy setting, CMTrace will be registered as the default Logfile viewer for the BIS-F LogFiles.
If you disable or do not configure this policy setting, CMTrace will not be registered as the default Logfile viewer for the BIS-F LogFiles.

Prerequisites: CMTrace.exe must be copied to the Base Image first

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 would be used.
Run DelProf2.exeRun DelProf2.exe

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

Prerequisites: delprof2.exe must be installed on the Base Image first

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 would be used.

Custom Arguments:
You can specify custom arguments for delprof.

If you enable this policy setting, you can specify your own arguments.
If you do not configure this policy setting, delprof2 will executed with default arguments /u /r
Disable IPv6Disable IPv6 in registry and on network adapter

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

Prerequisites: nvpsbind.exe must be installed on the Base Image first

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 would be used.
Run SdeleteRun SDelete on PVS WriteCacheDisk if vDisk is in shared mode only

If you enable this policy setting, SDelete will be executed. for the PVS WriteCache disk in shared mode.
If you disable this policy setting, SDelete won't be executed.
If you do not configure this policy setting, you'll be prompted during the sealing process.

Prerequisites: SDelete must be installed on the Base Image first

WARNING: sdelete 2.0 has an vendor bug and can run a very long time without finalize the sdelete process, please use the older sdelete version 1.6.1 or a newer one above 2.0

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 would be used.
Vmware OS Optimization ToolRun VMware OS Optimization Tool

If you enable this policy setting, VMware OS Optimization Tool will be executed. with the default OS template.
If you disable this policy setting, VMware OS Optimization Tool will not be executed.
If you do not configure this policy setting, you will be prompted during the sealing process.

Prerequisites: VMware OS Optimization Toool must be installed on the Base Image first

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 would 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 would be used.

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

8.1.2.Anti-Virus

Policy Description
Run AntiVirus full scanRun AntiVirus full scan

If you enable this policy setting, an Antivirus full scan will be executed.
If you disable this policy setting, an AntiVirus full scan won't be executed.
If you do not configure this policy setting, you'll be prompted during the sealing process.
Run Symantec VIETool Run Symantec VIETool to flagged out the scanned files

If you enable this policy setting, Symantec VIEtool will be executed.
If you disable this policy setting, Symantec VIEtool won't be executed.
If you do not configure this policy setting, you'll be prompted during the sealing process.

Prerequisites: VIEtool.exe 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
Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

8.1.3.Citrix

Policy Description
Configure Citrix OptimizerRun Citrix Optimizer

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
Configure Citrix Personal vDiskRun Citrix Personal vDisk inventory on VDI Clients only

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.
Configure Citrix PVS Target DeviceWriteCacheDisk drive letter

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.
VDA Configurationhis policy settings allows you to manage the Citrix VDA Configuration

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.
XA 6.x only: remove the current server from the Farm and clear the local database informationXA 6.x only: During XenApp preparation for PVS you can remove the current server from the Farm and clear the local database information

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.
Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

8.1.4.FSLogix

PolicyDescription
Configure FSLogix Central Rules ShareCopy FSLogix rules (*.frx) and assignemts (*.fxa) from central share during Device Personalization on System Startup

If you enable this policy setting, you must enter a valid central share location \\Server\Share.
If you disable this policy setting, a center share location won't be used.
If you do not configure this policy setting, you'll be prompted during the sealing process.
Delete Rules on Base ImageDelete FSLogix rules

If you enable this policy setting, FSLogix rules will be deleted.
If you disable this policy setting, FSLogix rules won't be deleted.
If you do not configure this policy setting, you'll be prompted during the sealing process.
Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

8.1.5.Global

PolicyDescription
Configure Very SilentConfigure VerySilent to suppress any BIS-F message boxes

If you enable this policy setting, BIS-F message boxes will be suppresed.
If you disable this policy setting, BIS-F message boxes won't be suppresed.
If you do not configure this policy setting, BIS-F message boxes won't be suppresed.
Shared ConfigurationThis policy settings allows you to 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.

If you enable this policy setting, you can enter an UNC-Path 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 \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
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.

If you disable do not configure this policy setting, the export can't be run.

Note: mostly you need this one time, to create the xml files, afterthat you can edit it manualy !!
You can also find the needed xml templates in the installation folder

Configure FoldersIf Citrix PVS Target Device Driver is installed, the some folders must be redirected to the WriteCacheDisk. You can specified this folders here:

Eventlogs:
If you enable this policy setting, you must enter an custom Eventlog foldername, e.g. "EventLogs"
If you disable this policy setting or if you do not configure this policy setting, the BIS-F standard folder would be used.

NOTE: Please specify the Name of the folder only, without any Driveletter !!

Spool:
If you enable this policy setting, you must enter an custom Spool foldername, e.g. "Spool"
If you disable this policy setting or if you do not configure this policy setting, the BIS-F standard folder would be used.

NOTE: Please specify the Name of the folder only, without any Driveletter !!
Configure LoggingLog Share:
Configure a central log share during Device Personalization on System Startup. Authenticated Users must have read/write access to this folder

If you enable this policy setting, you must enter a valid log share location \\Server\Share.
If you disable this policy setting, logs will be written to the Write Cache disk and you will not be prompted during the sealing process.
If you do not configure this policy setting, you will be prompted during the sealing process.

Log Retention (Default = 5):
specify a value between 0 -20, means the number of logfiles being kept.

0 = keep all logfiles
Configure Device PersonalizationConfigure the Device Personalization


Skip Personalization based on DiskMode
If you enable this policy setting, 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

If you disable or dor not configure this policy settings, the Device Personalization would not being skipped.
Supress Pending RebootSuppress Pending Reboot

If you enable this policy setting, pending reboot will be suppressed.
If you disable this policy setting, pending reboot won't be suppressed.
If you do not configure this policy setting and a pending reboot exist, the scripts will stop working!
Shutdown Base Image after sealingShutdown Base Image after successfully sealing. If running from an MDT or SCCM Task Sequence the Base Image will not be shutting down.

If you enable this policy setting, the Base Image will be shutdown after the sealing process.
If you disable this policy setting, the Base Image won't be shutdown after the sealing process.
If you do not configure this policy setting, the Base Image will be shutdown after the sealing process.
Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

8.1.6.Ivanti

PolicyDescription
Disable the RES ONE Automation AgentThis policy setting allows you to disable the RES ONE Automation Agent on the Base Image only to prevent RES ONE license usage.

If you enable this policy setting, RES ONE Automation Agent will be disabled.
If you disable this policy setting, RES ONE Automation Agent will not be disabled.
If you do not configure this policy setting, you will be prompted during the sealing process.
Disable RES ONE Automation Agent ServiceThis policy setting allows you to disable the RES ONE Automation Agent Service during preparation of the execution of BIS-F.

If you enable this policy setting, RES ONE Automation Agent Service will be disabled
If you disable or do not configure this policy setting, RES ONE Automation Agent Service will not be disabled..
Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

8.1.7.Microsoft

PolicyDescription
Ghost Devices: Classes to exclude from removalSpecifies 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 removalhis 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 ModeDefines 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 PackagesDelete 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 DefragThis 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 SupportEnable 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 OptimizationRun .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 onceRun 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 onceRun 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 countersRebuild 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 SysprepIf 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 AllUsersStartMenuDelete 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.
Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

8.1.8.Novell

PolicyDescription
Configure Novell ZCM Agent web based URLConfigure Novell ZCM Agent web based URL
Enter the URL in the following format:
reg https://ZCM-Server.domain.net -k CTX-XA65 -u XAuser -p XAuserPassword

If you enable this policy setting and the cloned device is starting, it will use the configured registration URL to get the configuration.
If you disable or do not configure this policy setting, the client device does not get their ZCM configuration.
Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

8.1.9.Turbo.net

PolicyDescription
Run Turbo UpateConfigure Turbo Update Device Personalization on System Startup

If you enable this policy setting, Turbo update will be executed. on System Startup.
If you disable this policy setting, Turbo update will not be executed. on System Startup.
If you do not configure this policy setting, you will be prompted during the sealing process.
Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

9.Custom Scipts

To extend the Base Image Script Framework with your own custom powershell scripts, simply put them in the right folder. If updated BIS-F with the installer, the content of this 2 folders are kept during installation.

StatePath
PreparationC:\Program Files (x86)\Base Image Script Framework (BIS-F)\Framework\SubCall\Preparation\Custom
PersonlizationC:\Program Files (x86)\Base Image Script Framework (BIS-F)\Framework\SubCall\Personlization\Custom

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.Run BIS-F

After the BIS-F Installation you can start it in 2 different ways

  1. From the Startmenu

 

2. From the Installation Folder

PrepareBaseImage.cmd > Run as administrator

After the script runs the first time it creates a shortcut on your personal Desktop, you can start BIS-F from this shortcut.

 

The Script checking if the personalization task of BIS-F is running, to prevent running preparation and personalization as the same time. IF BIS-F stucks at this point and the personalization running in a endless loop, read here to step over to the preparation state.

Note: The BIS-F scheduled task is created during first BIS-F execution

In the Mainscreen you can control all the steps running through.

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.1.Central Log share

You can store the BIS-F logs (preparation and personalization) on a central share. Authenticated users must have Read/Write Access

 

 

 

 

 

You can suppress this message box, see chapter ADMX Configuration

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.2.Pending Reboot

If a System Reboot was pending the stops their execution and show the following message.

 

 

 

 

You can configure a pending reboot by usage chapter ADMX Configuration

 

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.3.Operation System Rearm for KMS/MAK Activation

In the most customer environments, there is a KMS installed. If you are running the script for the first time on the Base-Image the following message box appears:

 

If you have a running KMS Server and would like to rearm your operating system, please check the license settings of your vDisk on the PVS-Server, see http://support.citrix.com/article/CTX128276 for further information.

IF you select “NO” the script will execute “slmgr.vbs /ream” once.

You can suppress this message box, see chapter ADMX Configuration

 

 

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.4.Office Rearm for KMS/MAK Activation

If an Office 32 Installation is detected by the Script, the following message box appears once:

If you have a running KMS Server and would like to rearm your Office Installation, please check the license settings of your vDisk on the PVS-Server, see http://support.citrix.com/article/CTX128276 for further information’s.

IF you select “NO” the script will execute “….microsoft sharedOfficeSoftwareProtectionPlatformOSPPREARM.EXE” once.

You can suppress this message box, see chapter ADMX Configuration

 

 

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.5.Citrix Workspace Environment Agent

If you have installed WEM Agent and does not configure them with the WEM Agent ADMX, the following Warning Message appears.

 

 

 

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.6.Delete AllUserStartmenu

The script asks you to delete AllUserStartmenu

 

 

 

 

 

 

You can suppress this message box, see chapter ADMX Configuration

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.7.Reset Performance Counters

The script asks you to reset the Performance Counters, see http://support.citrix.com/article/CTX129350 or http://support.citrix.com/article/CTX127151 for further information’s

 

 

 

 

 

 

You can suppress this message box, see chapter ADMX Configuration

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.8.Zero Out Free Space

You can use Zero our Free Space (if sdelete is installed) to securely delete existing files, as well as to securely erase any file data that exists in the unallocated portions of a disk (including files that you have already deleted or encrypted)

The script asks you to run sdelelte on your PVS WriteCacheDisk if the Image is in Read-Mode only.

 

 

 

 

 

You can suppress this message box, see chapter ADMX Configuration

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.9.fsLogix Apps

If fsLogix Apps https://fslogix.com/ is installed, the Base Image Script Framework automatic detects the Software and ask you to delete the fsLogix Rules on the Base-Image.

 

 

 

 

 

After that, you can define an fsLogix Central Rules share, where the script copies the fsLogix Rules and Assignment files on each startup to the Target Device.

 

 

 

 

 

 

You can suppress this message box, see chapter ADMX Configuration.

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.10.Citrix AppLayering

If Citrix AppLayering Agent is installed on the Image, BIS-F does something different describes in this chapter.

Depending on the current Layer (OS, Platform, Application Layer) and if BIS-F runs inside / or outside the ELM,
BIS-F detects the current Layer or ELM Mode and handles it accordingly.

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.

OS-Layer:
OS Layer is detected if path “HKLM:SYSTEMCurrentControlSetServicesUniService” Value “OSLayerEdit” exists

Platform/Application Layer:
Currently BIS-F can’t detect the difference between Platform/Application Layers
Platform/Application Layers are detected if path “HKLM:SYSTEMCurrentControlSetServicesUniService” Value “VolumeSerialNumber” exists

No-ELM:
If OS-Layer and Platform/Application Layers, are not detected
in “HKLM:SYSTEMCurrentControlSetServicesUniService” Value “MachineState” = 1

and 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

Yes No
Last updated on November 26, 2017
1 of 1 users found this section helpful

10.11.Citrix Personal vDisk

If you installed the XenDesktop VDA the script ask you to run Personal vDisk Update on Client-OS (Windows 7, Windows 8.x and Windows 10) only.

 

You can suppress this message box, see chapter ADMX Configuration

The Script waits for the process CtxPvd to end and check the Pvdlog for successful result.

In the next BIS-F Release we will support Citrix AppLayering also, the Citrix UserLayer will replace PvD in the future.

 

 

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.12.System Optimizations

BIS-F has own system optimizations (97_PrepBISF_PRE_BaseImage.ps1) for the Operating System, as describes here. In addition you can also trigger VMware OS Optimization Tool (vmOSOT) or Citrix Optimizer (CTXO) from BIS-F, configured in the BIS-F ADMX.

Note: If vmOSOT and/or CTXO is configured, some BIS-F system optimization will not be executed.

Global Optimizations:

  • Delete Citrix Cache C:\Program Files (x86)\Citrix\System32\Cache\*
  • Delete Software Distribution C:\Windows\SoftwareDistribution\Download\*
  • Delete Windows Update Log C:\Windows\WindowsUpdate.log
  • Purge DNS resolver Cache > ipconfig /flushdns
  • Purge IP-to-Physical address translation tables Cache (ARP Table) > arp -d *
  • Clear all event logs
  • Disable Receive Side Scaling (RSS) > netsh.exe int tcp set global rss=disable
  • Disable Data Execution Prevention > bcdedit.exe /set nx AlwaysOff
  • Disable Startup Repair option > bcdedit.exe /set {default} bootstatuspolicy ignoreallfailures
  • Disable New Network dialog
    • Set-ItemProperty -Name NewNetworkWindowOff -Path ‘HKLM:\SYSTEM\CurrentControlSet\ControlNetwork’ -Type String -Value 0″
  • Set Power Saving Scheme to High Performance > powercfg.exe -s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c
  • Reset Microsoft Distributed Transaction Service > msdtc.exe -reset
  • Hide Vmware Tools icon in systray (If installed)
    • Set-ItemProperty -Path ‘HKLM:\SOFTWARE\VMware, Inc.VMware Tools’ -Name ‘ShowTray’ -Value ‘0’ -Type DWORD
  • Disable VMware debug driver (If installed)
    • Set-ItemProperty -Path ‘HKLM:\SYSTEM\CurrentControlSet\services\vmdebug’ -Name ‘Start’ -Value ‘4’ -Type DWORD
  • Hide PVS Status icon in systray (If installed)
    • New-Item -Path ‘HKLM:\SOFTWARE\CITRIX\ProvisioningServices\Status’ -Force | out-null; Set-ItemProperty -Path ‘HKLM:\SOFTWARE\CITRIX\ProvisioningServices\Status’ -Name ‘ShowIcon’ -Value ‘0’ -Type DWORD
  • Delete WSUS – SusClientId (IF WSUS TargetGroup is enabled)
    • Remove-ItemProperty -Path ‘HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate’ -Name ‘SusClientId’
  • Delete WSUS – SusClientIdValidation  (IF WSUS TargetGroup is enabled)
    • Remove-ItemProperty -Path ‘HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate’ -Name ‘SusClientIdValidation’
  • Set Windows Update Service to Disabled
    • Set-Service -Name wuauserv -StartupType Disabled
  • Cleaning directory $env:windirTemp and $env:temp

 

Controlled with BIS-F ADMX:

  • Delete AllUsers Start Menu C:\ProgramData\Microsoft\Windows\Start Menu*
  • Run Delprof2 to deletes inactive user profiles (If installed)
  • Run CCleaner to clean temp files (If installed) > CCleaner.exe /Auto
  • Reset Performance Counters during preparation and also on personliaztaion > lodctr.exe /r
  • Disable IPv6 in registry
    • Set-ItemProperty -Path ‘HKLM:\SYSTEM\CurrentControlSet\Services\TcpIp6\Parameters’ -Name ‘DisabledComponents’ -Value ‘0x000000FF’ -Type DWORD”
  • Executing all queued .NET compilation jobs > ngen.exe ExecuteQueuedItems
  • Running sdelete (If installed, version 1.6.1 supported only) on PVS WriteCacheDisk or on local Disk (if Image is in shared Mode only)
    • PVS: sdelete.exe -accepteula -z <WriteCacheDrive>
    • MCS/vmWare/ Microsoft: sdelete.exe -accepteula -z %SystemDrive%
  • Disable IPv6 on AdapterGUID > nvspbind.exe /d “<AdapterGUID>” ms_tcpip6

 

Executed only, if 3rd Party Optimizer (vmOSOT and/or CTXO) are not enabled in BIS-F ADMX:

  • Disabling TCP/IP task offloading
    • Set-ItemProperty -Path ‘HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters’ -Name ‘DisableTaskOffload’ -Value ‘1’ -Type DWORD”
  • Increases the UDP packet size to 1500 bytes for FastSend
    • Set-ItemProperty -Path ‘HKLM:\SYSTEM\CurrentControlSet\Services\afd\Parameters’ -Name ‘FastSendDatagramThreshold’ -Value ‘1500’ -Type DWORD”
  • Set multiplication factor to the default UDP scavenge value (MaxEndpointCountMult)
    • Set-ItemProperty -Path ‘HKLM:\SYSTEM\CurrentControlSet\Services\BFE\Parameters’ -Name ‘MaxEndpointCountMult’ -Value ‘0x10’ -Type DWORD”
  • ARP Cache Changes Adapter > netsh interface ipv4 set interface <AdapterName> basereachable=600000
  • Stop DHCP Client Service > Stop-Service -Name dhcp
  • Clear NameServer in Registry TCPIP Parameters
    • Set-ItemProperty -Path ‘HKLM:\ SYSTEM\CurrentControlSet\Services\Tcpip\Parameters’ -Name ‘NameServer’ -value ”
    • Set-ItemProperty -Path ‘HKLM:SYSTEMCurrentControlSetServicesTcpipParametersInterfaces<AdapterGUID>’ -Name ‘NameServer’ -value ”
  • Clear Domain in Registry TCPIPParameters
    • Set-ItemProperty -Path ‘HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<AdapterGUID>’ -Name ‘Domain’ -value ”
  • Clear DhcpIPAddress in Registry TCPIPParameters
    • Set-ItemProperty -Path ‘HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<AdapterGUID>’ -Name ‘DhcpIPAddress’ -value ”
  • Clear DhcpSubnetmask in Registry TCPIPParameters
    • Set-ItemProperty -Path ‘HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<AdapterGUID>’ -Name ‘DhcpSubnetmask’ -value ”
  • Clear DhcpServer in Registry TCPIPParameters
    • Set-ItemProperty -Path ‘HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<AdapterGUID>’ -Name ‘DhcpServer’ -value ”
  • Clear DhcpNameServer in Registry TCPIPParameters
    • Set-ItemProperty -Path ‘HKLM:SYSTEMCurrentControlSetServicesTcpipParametersInterfaces<AdapterGUID>’ -Name ‘DhcpNameServer’ -value ”
  • Clear DhcpDefaultGateway in Registry TCPIPParameters
    • Set-ItemProperty -Path ‘HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<AdapterGUID>’ -Name ‘DhcpDefaultGateway’ -value ‘
  • Disable IPv6 on AdapterGUID > nvspbind.exe /d “<AdapterGUID>” ms_tcpip6
  • Disable Scheduled Tasks
    • “AitAgent”,”ProgramDataUpdater”,”StartupAppTask”,”Proxy”,”UninstallDeviceTask”,”BthSQM”,”Consolidator”,”KernelCeipTask”,”Uploader”,”UsbCeip”,”Scheduled”,”Microsoft-Windows-DiskDiagnosticDataCollector”,”Microsoft-Windows-DiskDiagnosticResolver”,”WinSAT”,”HotStart”,”AnalyzeSystem”,”RacTask”,”MobilityManager”,”RegIdleBackup”,”FamilySafetyMonitor”,”FamilySafetyRefresh”,”AutoWake”,”GadgetManager”,”SessionAgent”,”SystemDataProviders”,”UPnPHostConfig”,”ResolutionHost”,”BfeOnServiceStartTypeChange”,”UpdateLibrary”,”ServerManager”,”Proxy”,”UninstallDeviceTask”,”Scheduled”,”Microsoft-Windows-DiskDiagnosticDataCollector”,”Microsoft-Windows-DiskDiagnosticResolver”,”WinSAT”,”MapsToastTask”,”MapsUpdateTask”,”ProcessMemoryDiagnosticEvents”,”RunFullMemoryDiagnostic”,”MNO Metadata Parser”,”AnalyzeSystem”,”MobilityManager”,”RegIdleBackup”,”CleanupOfflineContent”,”FamilySafetyMonitor”,”FamilySafetyRefresh”,”SR”,”UPnPHostConfig”,”ResolutionHost”,”UpdateLibrary”,”WIM-Hash-Management”,”WIM-Hash-Validation”,”ServerCeipAssistant”
  • Disable Cortana
    • New-ItemProperty -Path ‘HKLM:\SOFTWARE\Policies\Microsoft\Windows\Windows Search’ -Name ‘AllowCortana’ -PropertyType DWORD -Value ‘0’

 

Yes No
Last updated on November 26, 2017
2 of 2 users found this section helpful

10.13.System defragmentation

The script asks you to run a vDisk defragmentation, after vDisk Build.

 

NOTE: defrag is running on vdh /vhdx base disk only.

You can suppress this message box, see chapter ADMX Configuration

 

 

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.13.1.Offline defragmentation

Offline Defragmentation is running only, if the defrag in the BIS-F ADMX is enabled 

If the Citrix PVS vDisk is created during BIS-F preparation on the Custom UNC-Path (enabled and configured in the ADMX),

after the vDisk is succesfull created on the UNC-Path it will be mounted to the BaseImage, bring the disk online and run defrag on this mounted driveletter.

If the vDisk is online and mounted on the Base Image, the uniqueID of the vDisk is changed, see https://blogs.technet.microsoft.com/markrussinovich/2011/11/06/fixing-disk-signature-collisions/ 

IF you booting up the vDisk you run in a Boot-Error, because the uniqueID of the Disk does not match to the BDM

BIS-F change the uniqueID on the mounted vDisk to the same as the Base-Image, as you can see in the BIS-F logfile.

Before  you booting up your Base Image with this created vDisk, please detach the origin local Disk from the Base Image on your Hypervisor. The Image is not able to boot and hangs on the Windows screen, because the VM has 2 Disk’s with the same UniqueID attached

These steps are required if you using the Custom UNC-Path to create the vDisk and the Defrag is enabled also in the BIS-F ADMX.

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

10.14.Shared Configuration

The BIS-F Shared Configuration can be used if the BIS-F ADMX can not deployed, this can have the following reasons

  • Citrix AppLayering: Domain Mode is in Platform Layer available only
  • Computer running in Workgroup Mode
  • Microsoft Azure: No GPO’s can be deployed
  • SCCM Tasksequence Deploymnent: Durring TS Deployment GPO’s not processed, read very good Blog from my CTA colleague Dennis Span here
  • New GPO’s / ADMX can not be easliy integrated in your enterprise environment

Install BIS-F on your Admin Workstation and copy the ADMX as describes here  to your local Admin Workstation C:WindowsPolicyDefinitions, after it  run > cmd > as administrator > gpedit.msc to open up the local policy and configure BIS-F on your requirements.

All settings are written to the local registry “HKEY_LOCAL_MACHINESOFTWAREPoliciesLogin ConsultantsBISF

Configure also the BIS-F Shared Configuration, you can use a local path, e.g. C:Program Files (x86)Base Image Script Framework (BIS-F) to save the registry export there.

Open the Powershell as administrator and point it to the BIS-F Folder

cd “C:Program Files (x86)Base Image Script Framework (BIS-F)Framework”

> . PrepBISF_Start.ps1 -ExportSharedConfiguration

All the BIS-F registry Settings are exported to the XML File in the Path that you have entered in the Shared Configuration above

The Export creates 2 XML Files:

BISFSharedConfig.xml: Store the Path to the BISFconfig_…xml, where BIS-F can find the XML Config

BISFconfig_…xml: Store all the BIS-F Settings, there are imported if you run BIS-F during preparation and personalization

Note: You can also store the BISFconfig on a UNC-Path on the network, but if your computer is not in the Domain, everybody must have read access to this path.

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

11.Preparation

The preparation phase is running to seal your image, optimize them based on your ADMX configuration and remove the Unique Identifiers (GUIDS) on vendor best practices and someone else. BIS-F automatic detect installed software and the current Diskstate as well and run it in the right way. This Chapter shows different options that you have

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

11.1.Citrix PVS: Boot from Hard Disk

With the BIS-F ADMX Configuration > Citrix > Configure Citrix PVS Target Device

you can select the P2v Tool P2PVS or ImagingWizard. In all ways BIS-F will using the right commandline switches to convert to Base-Image to the vDisk. IF you using UEFI Boot and has P2PVS configured in the ADMX, BIS-F runs a automatic fallback to ImagingWizard, it will be run with UEFI only.

 

The following arguments will be used to convert the HardDisk to the PVS vDisk. The P2V Tool is triggered only, if you run the right DiskMode as you can see here

P2V ToolvDisk FormatBootModeEnable P2V Custom UNC-PathP2V Custom UNC-PathEnable custom argumentsArgumentsCommand
P2PVSVHDX/VHDLegacy BIOSP2PVS C: /Autofit /L
P2PVSVHDX/VHDLegacy BIOS yesC: /LP2PVS C: /L
P2PVSVHDX Legacy BIOS yes\\Server\ShareP2VHDX %Computername%-yyyyMMdd-HHmm \\Server\Share C:
P2PVSVHDLegacy BIOS yes\\Server\ShareP2VHD %Computername%-yyyyMMdd-HHmm \\Server\Share C:
P2PVSUEFIFallback to ImagingWizard
ImagingWizardVHDX/VHDLegacy BIOSP2PVS C: /QuitWhenDone
ImagingWizardVHDX/VHDLegacy BIOS yes /QuitWhenDoneP2PVS /QuitWhenDone
ImagingWizardVHDX Legacy BIOS yes\\Server\ShareP2VHDX %Computername%-yyyyMMdd-HHmm \\Server\Share C: /QuitWhenDone
ImagingWizardVHDLegacy BIOS yes\\Server\ShareP2VHD %Computername%-yyyyMMdd-HHmm \\Server\Share C: /QuitWhenDone
ImagingWizardVHDX/VHDUEFIP2PVS /QuitWhenDone
ImagingWizardVHDX/VHDUEFI yes /QuitWhenDoneP2PVS /QuitWhenDone
ImagingWizardVHDX UEFI yes\\Server\ShareP2VHDX %Computername%-yyyyMMdd-HHmm \\Server\Share /QuitWhenDone
ImagingWizardVHDUEFI yes\\Server\ShareP2VHD %Computername%-yyyyMMdd-HHmm \\Server\Share /QuitWhenDone

If you using UEFI, the CLIcmd for ImagingWizard are not able to deselect any Driveletter, the ImagingWizard might be failed to run. If you deselect the WriteCahceDrive for example in the ImagingWizard GUI, it works without any issues !!

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

11.2.Citrix PVS: Boot from vDisk (vDisk Version)

If you creating a new vDisk Version, parent Disk – ahvd(x) and booting up your Base Image with that Version (PVS: boot from vDisk), it’s also possible to run BIS-F after your changes. BIS-F detect the BootMode and do not run P2PVS / ImagingWizard to convert the Disk (not necassary in this stage).

BIS-F run’s all the other needed preparation steps 

For avhd(x) also a defrag will not performed, if you have it enabled in the ADMX. Further informations about defrag can be getting here.

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

11.3.Citrix MCS: Booting up your Base Image

If you using Citrix MCS, BIS-F run all the same preparation steps based on ADMX configuration, but skipped the complete convertion process. It’s also necassary to run BIS-F everytime to seal your MCS Base Image, before update the Machine Catalog.

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

11.4.Citrix PVS with Applayering: Booting up your Image

With Citrix AppLayering, BIS-F do it differrent, so the convertion of the vDisk is not necassary, the complete AppLayring BIS-F description can be read here. also if the convertion need to be run or not, here.

Clonfiguration Note:  In the Platorm Layer you have to installed the Citrix PVS Target Device Driver, you can add an extra disk (WriteCacheDisk) to the system as describes in the following CTX Article – section Platform Layer and configure the BIS-F Policy Citrix > Configure Citrix PVS Target Device with the right Driveletter (e.g. D:).

If you do not add a extra Disk you can also use the command subst D: C:_AppLayeringWCDTemp

All the other steps from the CTX Article – section Platform Layer will bo done by BIS-F.

If you do not add a extra disk, please check and remove the Driveletter from the Policy (Disable the Policy)

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

12.Personalize

During the preparation of the Base Image a schedule Task “LIC_BISF_Device_Personlize” on the Image itself is created. This schedule Task running on computer startup to personalize the system.

The Script is running with SYSTEM Account

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

12.1.Citrix PVS: Booting up from vDisk

If you create a new PVS Target Device, you can add a fresh new hard disk without formatting it, still being able to use it as write cache disk. If the device boots from the vDisk and you have prepared the Base-Image with this BIS-F, the schedule task “LIC_BISF_Personalize_Device” checks for the persistent drive, formats it and reboots the device automatically once.

After the reboot the persistent drive is be used for pagefile (pagefile.sys), write cache (.vdiskcache), BIS-F Logs and other configuration items that you might redirect like EventLogs, spooler directory, etc.

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

12.2.Citrix MCS: Booting up your Image

IF you booting up your Image,  the scheduled Task start BIS-F personalization

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

13.Short names

Before we explain the Folder Structure, please read the following table to understand the short names that we used:

ValueDescription
PREPPreparation Phase: All Scripts conatins this Name (e.g. 90_PrepBISF_CTX.ps1) running during sealing your Base Image
PERSPersonalization Phase: All Scripts contains this Name (e.g. 02_PersBISF_CTX.ps1) running during Computer Startup, triggered from scheduled Task to make your Image Unique

 

 

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

14.Folder Structure

After installing BIS-F you can go into the folder structure, to understand what happens in each folder, let us explain here:

FolderDescription
Base Image Script Framework (BIS-F)Root Installation folder, that can be selected during installation
Base Image Script Framework (BIS-F)\FrameworkStart Scripts for the preparation or personlization phase
Base Image Script Framework (BIS-F)\Framework\SubCallAll necassary scripts for BIS-F to run
Base Image Script Framework (BIS-F)\Framework\SubCall\GlobalGlobal Scripts for BIS-F [DON'T TOUCH]
Base Image Script Framework (BIS-F)\Framework\SubCall\PersonalizationBIS-F Personalization Scripts running Computer Startup [DON'T TOUCH]
Base Image Script Framework (BIS-F)\Framework\SubCall\Personalization\Customcopy your custom scripts here, tu run during computer startup to make your Image Unique
C:\Program Files (x86)\Base Image Script Framework (BIS-F)\Framework\SubCall\PreparationBIS-F Preparation Scripts running during sealing [DON'T TOUCH]
Base Image Script Framework (BIS-F)\Framework\SubCall\Preparation\Customcopy your custom scripts here, to run it during sealing to optimize your Base Image and extend it with your own scripts
C:\Program Files (x86)\Base Image Script Framework (BIS-F)\Framework\SubCall\TemplateBIS-F Template for your own scripts to start simple
Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

15.Flow Diagram

The following flow diagram’s shows the details of each steps

  • Preparation: Running from administrator or from Automation
  • Personalization: triggered on computer startup from scheduled task
Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

15.1.Preparation Base Image

Yes No
Last updated on November 26, 2017
1 of 1 users found this section helpful

15.2.Personalize System

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

16.Troubleshooting

If  you have some trouble or develop own scripts to extend BIS-F, you can help your trouble with some easy steps.

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

16.1.Enable DebugMode

If you working with our Base Image Script Framework (BIS-F) and you have some trouble or develop own scripts to extend BIS-F, you can help your trouble with some easy steps.

Enable debugmode

one CLI comand are also available, if you start BIS-F in debugmode you must press any key after an logentry is written.

  • Open Powershell in AdminMode

         >cd ‘C:Program Files (x86)Base Image Script Framework (BIS-F)Framework

>.PrepBISF_Start.ps1 debugMode

Note: -debugMode is CaSeSeNsItIvE

Run single scripts for testing

If you run single BIS-F scripts that you have been developed or will test single BIS-F scripts

Open Powershell in AdminMode

>cd ‘C:Program Files (x86)Base Image Script Framework (BIS-F)FrameworkSubCallGlobal

>Import-Module .BISF.psd1

>$logfile = “C:windowsLogsBISFtmp.log“

>Initialize-BISFConfiguration

>Get-BISFOSinfo

this are necassary steps to get BIS-F initializes and now you have access to all BIS-F functions with command:

Get-Command -Module BISF

.. or run a single BIS-F script for testing..

now you can have a look into the logfile

one additional CLI comand are also available, if you start BIS-F in debugmode you must press any key after an logentrie is written.
> Open Powershell in AdminMode

>cd ‘C:Program Files (x86)Base Image Script Framework (BIS-F)Framework‘

>.PrepBISF_Start.ps1 –debugMode

Note: -debugMode is CaSeSeNsItIvE

 

If you working with our Base Image Script Framework (BIS-F) and you have some trouble or develop own scripts to extend BIS-F, you can help your trouble with some easy steps.

Enable debugmode

one CLI comand are also available, if you start BIS-F in debugmode you must press any key after an logentry is written.

  • Open Powershell in AdminMode

         >cd ‘C:Program Files (x86)Base Image Script Framework (BIS-F)Framework

>.PrepBISF_Start.ps1 debugMode

Note: -debugMode is CaSeSeNsItIvE

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

16.2.Run single scripts for testing

If you run single BIS-F scripts that you have been developed or will test single BIS-F scripts

Open Powershell in AdminMode

>cd ‘C:Program Files (x86)Base Image Script Framework (BIS-F)FrameworkSubCallGlobal‘

>Import-Module .BISF.psd1

>$logfile = “C:windowsLogsBISFtmp.log“

>Initialize-BISFConfiguration

>Get-BISFOSinfo

this are necassary steps to get BIS-F initializes and now you have access to all BIS-F functions with command:

Get-Command -Module BISF

.. or run a single BIS-F script for testing..

now you can have a look into the logfile

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

16.3.Personalization is in Active state...

If you starting the Base Image preparation, it checks if the personalization is running, to prevent run both phase at the same time.

In some circumstances the scheduled Task will not ended by itself, you can stop the schedule Task manually, but this will not help to proceed with the preparation of the Base Image.

Note: It’s necasaary to find out the underlying issue, why BIS-F personalization dos not run without issues !!

Open up the registry editor with the path “HKEY_LOCAL_MACHINE\SOFTWARE\Login Consultants\BISF” and check the value “LIC_BISF_PersState“. If the scheduled Task is running or you will have stopped it manually the value shows “Active” state.

Change the value from Active to Finished state and BIS-F proceed with the preparation task immediately.

In the following table, the valid values are described:

ValueDescription
AfterInstAfter the BIS-F Installation, the preparation can be started
ActiveThe personalization is running and waiting for the end to run preparation
Finishedif the personalization is ending, the preparation can be run now
AfterPrepAfter the Preparation is finsihed, the State will be changed, so the preparation can't be run again until the value is set to "Finished"
Yes No
Last updated on November 30, 2017
1 of 1 users found this section helpful

17.Appendix

In this chapter you can get additional informations about BIS-F and how it works. Feel free to send us your additional informations that you need around BIS-F here.

We are also working to documented each scripts that we are using

Yes No
Last updated on November 26, 2017
0 of 0 users found this section helpful

17.1.DiskModes

BIS-F detect the DisMode depend on your environment and select the right action, this Table show’s the overview of the used DiskMode

DiskModePVS Target Device DriverPVS WriteCacheType 2)VDAAppLayeringC:\Personality.iniP2V Custom UNC-Pathconvert to vDisk
ReadWrite yesWriteCacheType = 0file not existyes
ReadOnly yesWriteCacheType <> 0error
VDAPrivate w/o yesDiskMode=Private1)
VDAShared w/o yesDiskMode=Shared
VDAPrivateUNC-Path w/o yesDiskMode=Private yes1)
VDASharedUNC-Path w/o yesDiskMode=Shared yes
UnmanagedUNC-Path yes yesfile not exist yesyes
ReadWriteAppLayering yesWriteCacheType = 0 yes
ReadOnlyAppLayering yesWriteCacheType <> 0 yes
VDAPrivateAppLayering w/o yes yesDiskMode=Private
VDASharedAppLayeringw/o yes yesDiskMode=Shared
VDAPrivateUNC-PathAppLayeringw/o yes yesDiskMode=Private yes
VDASharedUNC-PathAppLayeringw/o yes yesDiskMode=Shared yes
UnmanagedUNC-PathAppLayeringw/ow/o yes yes
Unmanagedfile not exist

Legend:

1)      Yes, if PVS Target Device Driver is installed
2)      WriteCacheType exist only, if a vDisk is attached to the Target Device
w/o   with or without

Yes No
Last updated on November 26, 2017
1 of 1 users found this section helpful

17.2.ADMX: Registry Values

This table gives you a overview of all values that been used with the BIS-F ADMX and set to “HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Login Consultants\BISF

          
BIS-F TypeShortnameCategoryProductdescriptionREG HiveREG NameREG TypeREG DataLong Description
POLSD3rd Party ToolssDeleteRun SdeleteHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_SDDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLISD3rd Party ToolssDeleteRun SdeleteHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_SDREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLISD_SF3rd Party ToolssDeleteenable Custom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_SD_SFDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLISD_SF_CUS3rd Party ToolssDeleteCustom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_SD_SF_CUSREG_SZc:\windows\system32 or custom valueEnter custom searchpath or use default value c:\windows\system32
POLCC3rd Party ToolsCCleanerRun CCleanerHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_CCDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLICC3rd Party ToolsCCleanerRun CCleanerHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CCREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLICC_SF3rd Party ToolsCCleanerenable Custom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CC_SFDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLICC_SF_CUS3rd Party ToolsCCleanerCustom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CC_SF_CUSREG_SZc:\windows\system32 or custom valueEnter custom searchpath or use default value c:\windows\system32
POLCM3rd Party ToolsCMTraceEnable CMTraceHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_CMDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLICM3rd Party ToolsCMTraceEnable CMTraceHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CMREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLICM_SF3rd Party ToolsCMTraceenable Custom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CM_SFDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLICM_SF_CUS3rd Party ToolsCMTraceCustom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CM_SF_CUSREG_SZc:\windows\system32 or custom valueEnter custom searchpath or use default value c:\windows\system32
POLDP3rd Party ToolsDelProf2Run DelProf2HKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_DPDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIDP3rd Party ToolsDelProf2Run DelProf2HKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_DPREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLIDP_SF3rd Party ToolsDelProf2enable Custom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_DP_SFDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLIDP_SF_CUS3rd Party ToolsDelProf2Custom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_DP_SF_CUSREG_SZc:\windows\system32 or custom valueEnter custom searchpath or use default value c:\windows\system32
POLV63rd Party ToolsIPv6Disable IPv6HKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_V6DWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIV63rd Party ToolsIPv6Disable IPv6HKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_V6REG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLIV6_SF3rd Party ToolsIPv6enable Custom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_V6_SFDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLIV6_SF_CUS3rd Party ToolsIPv6Custom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_V6_SF_CUSREG_SZc:\windows\system32 or custom valueEnter custom searchpath or use default value c:\windows\system32
POLOT3rd Party ToolsvmOSOTVMware OS Optimization ToolHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_OTDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIOT3rd Party ToolsvmOSOTVMware OS Optimization ToolHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_OTREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLIOT_SF3rd Party ToolsvmOSOTenable Custom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_OT_SFDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLIOT_SF_CUS3rd Party ToolsvmOSOTCustom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_OT_SF_CUSREG_SZc:\windows\system32 or custom valueEnter custom searchpath or use default value c:\windows\system32
POLTBTurboTurboRun Turbo UpdateHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_TBDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLITBTurboTurboRun Turbo UpdateHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_TBREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLZCMbNovellNovell ZCMConfigure Novell ZCM Agent web based URLHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_ZCMbDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIZCMbNovellNovell ZCMConfigure Novell ZCM Agent web based URLHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_ZCMbREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLIZCMNovellNovell ZCMZCM Registration URLHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_ZCMREG_SZreg https://ZCM-Server.domain.net -k CTX-XA65 -u XAuser -p XAuserPasswordConfigure Novell ZCM Agent web based URL
Enter the URL in the following format:
reg https://ZCM-Server.domain.net -k CTX-XA65 -u XAuser -p XAuserPassword
POLAVAnti-VirusRun AntiVirus full scanHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_AVDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIAVAnti-VirusRun AntiVirus full scanHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_AVREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLAV_VIEAnti-VirusSymantecRun Symantec VIE ToolHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_AV_VIEDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIAV_VIEAnti-VirusSymantecRun Symantec VIE ToolHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_AV_VIEREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLIAV_VIE_SFAnti-VirusSymantecenable Custom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_AV_VIE_SFDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLIAV_VIE_SF_CUSAnti-VirusSymantecCustom SearchfolderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_AV_VIE_SF_CUSREG_SZc:\windows\system32 or custom valueEnter custom searchpath or use default value c:\windows\system32
POLRAIvantiRES ONEDisable RES ONE Automation AgentHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_RADWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIRAIvantiRES ONEDisable RES ONE Automation AgentHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_RAREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLRA_SVCIvantiRES ONEDisable RES ONE Automation Agent ServiceHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_RA_SVCDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIRA_SVCIvantiRES ONEDisable RES ONE Automation Agent ServiceHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_RA_SVCREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLFSFslogixFslogixDelete Rules on Base ImageHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_FSDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIFSFslogixFslogixDelete Rules on Base ImageHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_FSREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLRSbFslogixFslogixConfigure FSLogix central rules shareHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_RSbDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIRSbFslogixFslogixConfigure FSLogix central rules shareHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_RSbREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLIRS FslogixFslogixFS Logix Rules ShareHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_RS REG_SZ\\Server\Shareenter a valid central share location \\Server\Share
POLDFMicrosoftDefragRun DefragHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_DFDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIDFMicrosoftDefragRun DefragHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_DFREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLOSMicrosoftOSRearm Microsoft Windows onceHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_OSDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIOSMicrosoftOSRearm Microsoft Windows onceHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_OSREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLOFMicrosoftOfficeRearm Microsoft Office onceHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_OFDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIOFMicrosoftOfficeRearm Microsoft Office onceHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_OFREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLGDMicrosoftGhost DevicesGhost Devices: Operation modeHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_GDDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIGDMicrosoftGhost DevicesGhost Devices: Operation modeHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_GDREG_SZRemove,ListAllDevices,ListOnlyGhostDevicesRemove 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.
CLIGD_ExCLMicrosoftGhost DevicesGhost Devices: Classes to exclude from removalHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_GD_ExCLREG_SZFreeTextSpecifies 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, separated by a semicolon ";". For example: LegacyDriver;Net;SCSIAdapter. Text is case sensitive
CLIGD_ExFNMicrosoftGhost DevicesGhost Devices: Friendly named devices to exclude from removalHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_GD_ExFNREG_SZFreeTextThis 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, separated by a semicolon ";". For example: Citrix;Intel(R) HD Graphics 5500;Generic USB Hub.
POLPFMicrosoftPerformance CountersRebuild Performance CountersHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_PFDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIPFMicrosoftPerformance CountersRebuild Performance CountersHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_PFREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLSMMicrosoftStartMenuDelete AllUsersStartMenu contentHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_SMDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLISMMicrosoftStartMenuDelete AllUsersStartMenu contentHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_SMREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLSPMicrosoftSysprepRun SysprepHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_SPDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLISPMicrosoftSysprepRun SysprepHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_SPREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLSTMicrosoftRDP SupportEnable RDP Session supportHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_STDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLISTMicrosoftRDP SupportEnable RDP Session supportHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_STREG_SZYESIF Policy is enabled Registry Data is set to YES, if disabled or not configured it does not exist.
POLARMicrosoftApp-VRemove App-V packagesHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_ARDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIARMicrosoftApp-VRemove App-V packagesHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_ARREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLDotNETMicrosoft.NET.NET OptimizationHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_DotNETDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIDotNETMicrosoft.NET.NET OptimizationHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_DotNETREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLSBGlobalBIS-FShutdown Base Image after sealingHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_SBDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLISBGlobalBIS-FShutdown Base Image after sealingHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_SBREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLSRGlobalBIS-FSuppress Pending RebootHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_SRDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLISRGlobalBIS-FSuppress Pending RebootHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_SRREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLVSGlobalBIS-FConfigure VerySilentHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_VSDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIVSGlobalBIS-FConfigure VerySilentHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_VSREG_SZYESIF Policy is enabled Registry Data is set to YES, if disabled or not configured it does not exist.
POLLogCfgGlobalBIS-FConfigure LoggingHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_LogCfgDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLILogCfgGlobalBIS-FConfigure LoggingHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_LogCfgREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLILSbGlobalBIS-FEnable Central Log ShareHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_LSbDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLILSGlobalBIS-FLog ShareHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_LSREG_SZ\\Server\Shareenter a valid central share location \\Server\Share
CLILF_RTGlobalBIS-FLog RetentionHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_LF_RTDWORD0-20Log rentention perid, defeault = 5, 0 = unlimited
POLFldCfgGlobalBIS-FConfigure FoldersHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_FldCfgDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIFldCfgGlobalBIS-FConfigure FoldersHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_FldCfgREG_SZYESIF Policy is enabled Registry Data is set to YES, if disabled or not configured it does not exist.
CLIEVTbGlobalBIS-FEnable custom event log folder nameHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_EVTbDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLIEvtFolderGlobalBIS-FEvent log folder nameHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_EvtFolderREG_SZEventLogsEnter the name of the Eventlog Folder (take affect if PVS redirection is enabled only)
CLISPbGlobalBIS-FEnable Custom Spool folder nameHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_SPbDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLISpoolFolderGlobalBIS-FSpool folder nameHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_SpoolFolderREG_SZSpoolEnter the Name of the Spool Folder (take affect if PVS redirection is enabled only)
POLPersCfgGlobalBIS-FConfigure PersonalizationHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_PersCfgDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIPersCfgGlobalBIS-FConfigure PersonalizationHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_PersCfgREG_SZYESIF Policy is enabled Registry Data is set to YES, if disabled or not configured it does not exist.
CLIDMGlobalBIS-FSkip Personalization based on DiskModeHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_DMREG_SZAll, ReadWrite, NeverThe Diskmode to skip personalization
POLEXGlobalBIS-FShared ConfigurationHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_EXDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIEXGlobalBIS-FShared ConfigurationHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_EXREG_SZYESIF Policy is enabled Registry Data is set to YES, if disabled or not configured it does not exist.
CLIEX_PTGlobalBIS-FShared ConfigurationHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_EX_PTREG_SZ\\Server\Share or loal PathEnter the path to save the Shared Configuration
POLCTXOECitrixCitirx OptimizerConfigure Citrix OptimizerHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_CTXOEDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLICTXOECitrixCitirx OptimizerConfigure Citrix OptimizerHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CTXOEREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLICTXOE_TPCitrixCitirx Optimizer(Optional) Template:HKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CTXOE_TPREG_SZFreeTextEnter the Name of the Template
CLICTXOE_GROUPSCitrixCitirx Optimizer(Optional) List of enabled Groups:HKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CTXOE_GROUPSREG_SZFreeTextEnter the Name of the processed groups
CLICTXOE_AnalyzeCitrixCitirx OptimizerMode: Analyze onlyHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CTXOE_AnalyzeDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLICTXOE_SFCitrixCitirx OptimizerEnable custom search folderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CTXOE_SFDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLICTXOE_SF_CUSCitrixCitirx OptimizerCustom search folderHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CTXOE_SF_CUSREG_SZc:\windows\system32 or custom valueEnter custom searchpath or use default value c:\windows\system32
POLPDCitrixPvDConfigure Citrix Personal vDiskHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_PDDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIPDCitrixPvDConfigure Citrix Personal vDiskHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_PDREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLRMCitrixXA 6.5XA 6.x only - Remove current XenApp server from the Farm and clear local database informationHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_RMDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIRMCitrixXA 6.5XA 6.x only - Remove current XenApp server from the Farm and clear local database informationHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_RMREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
POLPVSCfgCitrixPVS Configure Citrix PVS Target DeviceHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_PVSCfgDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIPVSCfgCitrixPVS Configure Citrix PVS Target DeviceHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_PVSCfgREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLIWCDCitrixPVS WriteCacheDisk drive letterHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_WCDREG_SZB-Zselect the Driveletter of the PVS WriteCacheDrive
CLIPTCitrixPVS P2V ToolHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_PTREG_SZImagingWizard,P2PVSselect the P2V Tool to use (default = ImagingWizard)
CLIPT_FTCitrixPVS vDisk FormatHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_PT_FTREG_SZVHD, VHDXselect the vDisk extension to use (default = VHDX)
CLIP2V_PTCitrixPVS Enable P2V Custom UNC-PathHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_P2V_PTDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLIP2V_PT_CUSCitrixPVS P2V Custom UNC-PathHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_P2V_PT_CUSREG_SZ\\Server\ShareThe Path to create the vDisk on it
CLIP2V_CUS_ARGSCitrixPVS Enable custom argumentsHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_P2V_CUS_ARGSDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist
CLIP2V_ARGSCitrixPVS ArguemntsHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_P2V_ARGSREG_SZFreeTextUsing Custom P2V Arguments
POLVDACfgCitrix VDAVDA ConfigurationHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_POL_VDACfgDWORD1If Policy is enabled Registry Data is set to 1, otherwise it not exist
CLIVDACfgCitrixVDAVDA ConfigurationHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_VDACfgREG_SZYES, NOIF Policy is enabled Registry Data is set to YES, if disabled set to NO; otherwise not exist.
CLICDSCitrixVDADelay Citrix Desktop ServiceHKLM:\SOFTWARE\Policies\Login Consultants\BISFLIC_BISF_CLI_CDSDWORD1If CheckBox is enabled, registry Data is set to 1, otherwise not exist

 

Yes No
Last updated on November 26, 2017
2 of 2 users found this section helpful
Help Guide Powered by Documentor
Suggest Edit