I'm trying to get Bitlocker set up in SCCM CB 1910.  When I got to Client Management though the "Allow Recovery Information to be stored in plain text" is greyed out. Does anyone know why this might be the case?  This is in a lab, first Bitlocker Policy. Many thanks

Hi All, We are experiencing a weird issue with BitLocker when re-installing existing Windows 10 1709 machines with Windows 10 1903. The machines are hybrid AD joined and the BitLocker recovery information is stored in Active Directory. During a new installation of the device with Windows 10 1903, the BitLocker key fails on storing the recovery information in Active Directory. After examining the Windows event log, it turns out the device is trying to store the recovery information in Azure

I want to make sure I understand this correctly. If I want to deploy Windows Updates to clients that are on the internet (part of our domain but never VPN in) and have those computers download the updates directly from Microsoft, I would only need to setup a Cloud Management Gateway and PKI (if not using AAD) or use Azure AD, correct?   If not, what would I need to setup to do this? 

We have some Dell Optiplex 7070 computers, and I'm trying to deploy a Windows 10 1909 image to them without changing the default bios configuration, which comes set to "Raid On" in Sata Operation.   The default dell image works fine, so I'm not sure why ours does not. I'm imported all of the drivers that I could find for this model and intel storage in general. The task applies the OS and works in winPE fine, but after rebooting just gets a blue screen.   How do I get this wo

Hello everybody, I need to create an application that has different msi parameters depending on the VLAN the server is in. I thought i would use different Deployment types and determine the subnet by using a custom Global Condition. I started with creating a global condition using a powershell command (Get-NetIPConfiguration | Where-Object {$_.IPv4DefaultGateway}).IPv4DefaultGateway.nexthop this returns the ip address of the gateway but found out that this would only work on windows

I just upgraded to 1906, everything passed, i did both Hot fixes and now when i try to edit the client policy i get the following error and then it crashes the console. I have googled around, looked all over the internet and found nothing on this error or how to fix it. I did find a couple things about editing the policy to true in the WMI powershell but i have no idea how to do that and Microsoft is absolutely trash on explaining this process, if anyone can help it would be greatly appreciated.

Hi gents. I'm pulling my hair out, whole of last week and this week I'm using OSD to deploy PC's for a new contract. Few hours ago all stopped working, any PC or laptop, intel, hp, lenovo. All fail with this error. Nothing on my environment changed. Some research takes me to the March 2019 CU update. It is not installed on my server. Both these registry keys were set back to default with no difference on the outcome. RamDiskTFTPBlockSize RamDiskTFTPWindowSize

Hello, Recently I had a Secondary site Server die. I deleted it out of SCCM, rebuilt it and recreated it back in to SCCM as a secondary site with the same name and IP Address. Everything will work fine expect the installing apps step in the Task sequence for clients on this site. I have rebuilt it several times to no avail. Interestingly enough if I rebuild the server but using a name that hasn't been used before all apps deploy successfully during the task sequence. So