Issue involving OneDrive 2.0 Known folder move and Settings Catalog in Intune

-
Are you deploying OneDrive configuration including Known folder move using Settings Catalog and wondering why your known folders Documents and Pictures are not synching like Desktop, then you are not alone.

Ever since settings catalog was introduced, I have practically moved all my device policies over, where ever possible of course. Naturally, I moved OneDrive settings as well, but soon realized that this may not be such a good idea. At least not until Microsoft addresses the issue.

As of writing this blog, it is not possible to configure all known folder move configuration in settings catalog. Currently the following settings are available under Settings Catalog -


When you configure these settings and assign them, only the Desktop known folder will get enabled for sync, leaving the other 2 known folders Documents and Pictures un-managed.

To fix this natively in Intune, the only option is to use built Administrative template. This is because the built-in administrative templates has additional settings which you can configure to complete the configuration of KFM, which for some reason have not made it to Settings Catalog. These settings are available under OneDrive 2.0 for 'Silently move Windows known folders to OneDrive'




Once you configure them using Administrative templates, all your known folders should get configured for sync.



If you are looking for other relevant OD policies for configuration, then here is a set of settings that I normally configure.

Until next time..

Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){                 $KPID=$KP.KeyProtectorId                 break;             }         }        $o
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $Path1
Read more

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from starting pr
Read more