This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
Earlier there was information about that after installing 2103 and if there is "invoke-MbamClientDeployment.ps1" used in SCCM Task Sequence than it could cause policy storms in SQL database.
The official solution as i now i delete this step and leave just steps of turning on Bitlocker and after that PC starts up for the first time it will receive SCCM Bitlocker Policy that will send the key to SCCM SQL database.
Ok but is there some solution of leaving this script in SCCM TS, because now it's very good, because it's send bitlocker key during TS.
Using this script on SCCM database i receive 47 policies and after new PC installs with TS it's increase.
Could i delete this policies from SCCM SQL database?
Other Configuration Manager-related features and issues
Ok but is there some solution of leaving this script in SCCM TS
No, not today. The best you can do today is save the key to your on-prem AD or hard-code a recovery key (that will get rotated later).
With this in mind, does this cause you pain or become a blocker? If so, why (trying to phrase this is business impact terms and not technical ones)?
But could i remove those records in SCCM SQL database which are created during SCCM Task Sequence every time this "invoke-MbamClientDeployment.ps1" script is triggered?
You "can" do a lot of things but we wouldn't support you doing this and there would be unknown ramifications from doing so repeatedly. As usual, doing unsupported things leads to unsupported results.