Windows 10: Enable Bitlocker Windows 11 SCCM Task Sequence fails?

We are trying to enable Bitlocker on few different Dell laptops. Currently it fails with these generic errors. What am I am I missing here?We deployed bitlocker via intune and that works well but trying to deploy this for imaging from the get go is a pain. From TS when its running. Running module version 5.0.9122.1000 from location 'C:\WINDOWS\CCM\OSDBitLocker.exe' Command line: "OSDBitLocker.exe" /enable /drive:C: /wait:True /pwd:AD_CM /full:False /crypt:4 /ignoretpm:True Initialized COM Command line for extension .exe is "%1" %* Set command line: "OSDBitLocker.exe" /enable /drive:C: /wait:Tr

:)

 

Execute a command from SCCM Task sequence step "Run a Command line"

Hi,

Thanks for your suggestion.

That will work indeed, however I need to run it from the SCCM Task Sequence's Run Command Line Step and I am not able to figure out how to do that.

Can we change line while executing command from SCCM Task Sequence's Run Command Line Step?

Regards

 

SCCM - TsmBootstrap.exe - Application Error during Task Sequence

Hi All,

I have been getting this TsmBootrap.exe error in my SCCM Task Sequences for a while, and can't figure out how to eliminate it. It always pops up in the Task Sequence just before the first reboot after the OS has installed. I just click "OK" and the Task Sequence resumes and finishes successfully, all drivers and apps install successfully as well, this just seems to be a nuisance and doesn't cause the TS to crash or fail or anything.

I have tried creating brand new Task Sequences, disabling the driver installation step, using different boot images for different models of computers, but this keeps happening. I do have the smsts.log, but cannot attach it here. Any help would be appreciated! Thanks in advance!

 

SCCM 1606 and Failed Windows 10 1607 Upgrade

I created a SCCM task sequence using the 'Upgrade an operating system from an upgrade package' template and the task sequence works provided there is not an issue during the upgrade. If the upgrade fails Windows automatically reverts back to Windows 7. This
is great, but the task sequence never continues and the 'Rollback on Failure' group never executes.

I have post processing that needs to be executed after a rollback that installs applications which were uninstalled prior to the 'Upgrade Operating System' step being run.

I found after the rollback that the ccmexec service is disabled. Looking through the logs it is disabled by the 'Upgrade Operating System' step in the task sequence.

If I manually enable the ccmexec service and restart the machine, Software Center is empty. Forcing a Machine Policy Retrieval & Evaluation Cycle does not fix the problem. Reinstalling the client by running ccmsetup does not fix the problem. The only way
to get Software Center to show applications is to completely uninstall the SCCM client and then run ccmsetup again.

Any ideas on how to get the 'Rollback on Failure' group to execute?

Thanks,

Scott