search

EUCweb / BIS-F

Base Image Script Framework (BIS-F)
https://eucweb.com
GNU General Public License v3.0
96 stars 34 forks source link

BIS-F in SCCM Task Sequence brings TS to fail after successfull running #263

Open nexocon opened 4 years ago

nexocon commented 4 years ago

When we run BIS-F in an SCCM Task Sequence, the SCCM Agent after Sealing and PVS vDisk capture is done, looses the connection to SCCM MP and this will endup in a failed Task Sequence. The Task Sequence will hang in this state: image

It will take some time (approx. 60 min.) and the VM will be reboot. After the reboot the VM is in this state: image

matthias-schlimm commented 4 years ago

can you upload here the BIS-F preparation and personalization log

nexocon commented 4 years ago

PREP_BISF_xxx.log

An Pers.log is currently not available from this deployment.

matthias-schlimm commented 4 years ago

can you try a test with a copy from the developer branch here. In issue https://github.com/EUCweb/BIS-F/issues/269 we are fixing the Get-WMIObject tu use registry data instead

_The Win32Product class is not query optimized. Queries that use wildcard filters cause WMI to use the MSI provider to enumerate all installed products then parse the full list sequentially to handle the filter. This also initiates a consistency check of packages installed, verifying and repairing the install. The validation is a slow process and may result in errors in the event logs.

xenadmin commented 4 years ago

FYI @matthias-schlimm the second screen from @nexocon about Fehler bei der Initialisierung der Anmeldung I get (nearly) every time a MCS clone starts for the very first time after the cloning process. I then send a Force Reboot via Citrix Studio and the error is gone forever. I always thought that this might be a Citrix MCS issue, but maybe it's in regards to BIS-F? It doesn't hurt, I just Force Reboot every Clone once after it's born and I see it never again, but I thought you might want to know.

tschuegy commented 3 years ago

We start the BIS-F Steps outside the SCCM task sequence, but the preparation for that is inside the TS. The steps looks like this:

OSD TS --> BIS-F scheduled install task as last step in TS --> End TS and reboot --> Autologon with a Service Account --> Start BIS-F installation steps.

In our OSD, the TS completes successfully and boots automaticaly the vm aferwards. After the vm boots up, an autologon is processing. After that, the file PrepareBaseImage.cmd will be executed.

Any questions? In our case we do not manually interact in any step.