Base Image Script Framework (BIS-F) 6.1

What's new

593 views January 28, 2019 July 12, 2019 Matthias Schlimm 2

6.1.2

  • [ENH 112] CTX optimizer: Multiple Templates with AutoSelect for OS Template
  • [ENH 117] WinSxS hide DISM process and get logfile
  • [HF 116] During Preparation, BIS-F Shows Versionnumber instead of OSName
  • [HF 82] RES ONE Automation Agent – Action is missing
  • [FRQ 115] ADMX: Control of WinSxS Optimization

6.1.1 build 01.105

  • [ENH 105] Keep Windows Administrative Tools in Startmenu – If you delete the AllUserStartmenu with BIS-F this will keep now the Administrative Tools Folder
  • [FRQ 92] Server 2019 Support – During preparation BIS-F sends out Server 2016 if OSServerbuild is greater than 10, BIS-F sending the OS Buildnumber now to the console back
  • [HF 24] reconfigure Citrix Broker Service if disabled / not configured in ADMX – If you have VDA Delayed operation configured in the ADMX, and set it back to not configured or disabled the Citrix Broker Service will reconfigured during preparation to Automatic
  • [FRQ 111] Support for multiple Citrix Optimizer Templates – In the ADMX you can enter multiple Templates with commaseperator and without any spaces to use multiple templates, e.g: Citrix_Windows_10_1809.xml,PVS_Target.xml
  • [HF 106] remove uneccesary out-null command function Optimize-WinSxs – fixes an ussue to run Optimize-WinSxs
  • [HF 87] Symantec Endpoint Protection 14.0 MP2 prevents graceful Citrix session logoff – Rename sqsvc.dll, sqscr.dll and symerr.exe files to: sqsvc.dll.old, sqscr.dll.old and symerr.exe.old to fix the issue as described

6.1.0 build 01.104

  • [FRQ 86] – Office 2019 (x86 and x64) is detected and rearmed during preparation and activated against KMS during personalization.

6.1.0 build 01.103:

  • [HF 80] Citrix Optimizer Templatenames are changed in order to support auto-selection

6.1.0  build 01.102:

  • 07.12.2018 MS: Bugfix 79: BIS-F Installer can be used on x86 systems
  • 21.10.2018 MS: Bugfix 75: CTXO: If template not exist, end BIS-F execution
  • 21.10.2028 MS: Bugfix 18: XA/ XD 7.x Cache folder will be created
  • 21.10.2028 MS: Bugfix 47: MSMQ windows services will fail to start in App Layering
  • 21.10.2018 MS: Bugfix 62: BIS-F AppLayering – Layer Finalized is blocked with MCS – Booting Layered Image
  • 20.10.2018 MS: Bugfix 74: The Version from the Service could not extracted
  • 20.10.2018 MS: Bugfix 66: vietool.exe – custom searchpath not working correctly
  • 20.10.2018 MS: Bugfix 55: Windows Defender -ArgumentList failing
  • 20.10.2018 MS: Hotfix 63: Citrix AppLayering – Create C:\Windows\Logs folder automatically if it doesn’t exist
  • 20.10.2018 MS: Bugfix 56: Office C2R or other AppX issue after BIS-F seal
  • 20.10.2018 MS: Bugfix 73: MCS Image in Private Mode does not start the Windows Update Service
  • 19.10.2018 MS: Bugfix 71: not to process ANY scheduled task disable actions
  • 19.10.2018 MS: Bugfix 72: MCS Deployment: SCOM Agent – creates OpsStateDir in C: drive
  • 19.10.2018 MS: Bugfix 58: Mc Afee – remove hardcoded maconfig.exe path
  • 12.07.2018 MS: Bugfix 40: PendingReboot – give a empty value back
  • 09.07.2018 MS: Bugfix 48: AppLayering RunMode + Get-DiskMode from PVS / MCS Deployment needed, to get the right layer
  • 02.07.2018 MS: Bugfix 50: set Global Variable after Registry is set (After LogShare is changed in ADMX, the old path will also be checked and skips execution)
  • 01.07.2018 MS: Bugfix 44: Pickup the right Citrix Optimizer Default Template, like Citrix_Windows10_1803.xml, also prepared for Server 2019 Template, like Citrix_WindowsServer2019_1803.xml
  • 01.07.2018 MS: Bugfix 49: After SEP is started with smc.exe, sometimes the service will not be started. Controlled and logged now with Test-BISFServiceState in Line 58
  • 01.07.2018 MS: Bugfix 49: running Test-BISFServiceState after changing Service to get the right Status back
  • 01.07.2018 MS: Bugfix 48: Using RunMode to detect the right AppLayer, persistent between AppLayering updates
  • 28.05.2018 MS: Bugfix 41: Set SplunkForwarder to StartType Automatic
  • 27.05.2018 MS: Bugfix 40: new Script to get pending reboot state
  • 30.03.2018 MS: Bugfix 38: MachineState 3 not detected, Pre-ELM State, Layer finalized must not run
  • 29.03.2018 MS: Bugfix 37: SCOM 2016, uses new certificate store Microsoft Monitoring Agent

Was this helpful?

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

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

Close