Add option to the "Enable BitLocker" Task Sequence step to escrow the Recovery key directly to MEMCM DB
Many of us used the Invoke-MbamClientDeployment.ps1 to enable and escrow the BitLocker recovery key to MBAM even after MBAM was integrated into MEMCM to be able to skip saving the Recovery Key to AD during OSD,
After 2103 this is no longer supported as per the link below
Adding an option to the "enable Bitlocker" step to Escrow the recovery key to MEMCM direclty during the Task Sequence would be a great additon as we can skip storing it in AD during OSD to have it Escrowed after OSD is complete.
the other option is to skip encrypting the device during OSD which is not a good option.