This looks to be resolved with Windows 10 1809.
Silent BitLocker and Windows RE status remains enabled.
When you enable BitLocker it will present the following message: "You will no longer be able to use Windows Recovery Environment if you enable Bitlocker".
At this point the recovery partition is no longer available. If you manually try to reset the machine via: Settings > Update & Security > Recovery > Get Started > Remove everything
You will get the message:
Could not find the recovery environment.
However, it looks like if you run:
reagentc /enable (deploy via GPO or SCCM, needs to be run as admin)
It will create a recovery partition after you have enabled BitLocker. Tested this with 1709 and has worked on one machine.
You could run into trouble with the sizing of the partition as per:
Will test this with additional machines and will provide an update
Can you please advise on this?
We are using 1809 with hybrid join and as per the problem statement, this is confusing for deployment.
The keys are stored in local AD rather than AAD or the user AAD profile.
Can Quick Assist also be locked down to specific users? I find it out that anyone in the world can connect to corporate devices via Quick Assist
An update on this – this feature in flight but we are going to take a bit more time before we make it publicly available. Should be early in 2020. Thanks for your patience!
Windows 10 devices as well please. Also when using the DEM account, I should then be able to assign this to the end-user
Yep concur with this... the only workaround is to change the name of the OMA-URI from .../Office16ADMX to .../Office16ADMX2.
This will then apply new settings added to the string... however, it does not remove existing settings if they are no longer listed. Not sure what is does to existing settings that remain, which might have had GPO settings changed.
Also, what are the implications with the new Administrative Templates features which was discussed at Ignite: https://oliverkieselbach.com/2018/09/29/ignite-2018-my-wrap-up/
If I implement the Office 2016 ADMX ingestion, will the settings clash with the new feature update?
Seems very beta all of this... the only way I can truly update an ADMX policy today is to delete the keys listed under:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\AdmxDefault and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\Admxinstalled
Is there any update on this? There is an unnecessary additional cost to the business to allow users to administer Intune when using RBAC.
6 votesbally shared this idea ·