Looking beyond CSP and using Settings Catalog to configure Time zone using Intune

-
Back in June, 2021, when I first blogged about using Settings Catalog, I knew that the addition of this device configuration profile by Microsoft was a step in the right direction. Fast forward to 2022 and my take on Settings Catalog has only been re-affirmed. Even though the feature is still in preview, it is clearly evident that a lot of development work has gone into it and kudos to Microsoft product group for keeping at it.

Even thought some CSPs are still missing, majority of them are actually added and supported now. To such an extent that I hardly find myself using CSPs anymore. One such use case is configuring time zone setting, a CSP that pretty much every organization have on their list of requirements for Windows devices that are being managed by Intune.

I recently used the Settings catalog to configure the time zone and if you want to know how to configure this then keep reading. :-)

First, get a list of available time zones. This can be done using the Powershell cmdlet Get-TimeZone -ListAvailable


Since the list is long, it is better to pipe the output using '>'. Resultant output will give you the list of available timezones.


Next step is to create the policy in Intune.

2. Browse to Devices – Windows – Configuration Profiles
3. Click Create Profile
4. Select Platform as Windows 10 and later
5. Select Profile as Settings catalog (Preview)
6. Provide a Name and hit next.
7. Click on Add settings.
8. Search for 'Configure Time' and select Configure Time Zone under Time Language Settings as shown below.


9. Enter the relevant value. In my case I needed the time zone to be set to 'GMT Standard Time'.
10. Once selected then assign the policy to a device or user based group.

End Result

Once the device syncs, the time zone will get configured. 


It can be checked in the MDMDiagReport as well.


Reporting compliance in Intune -



I am slowly moving other CSP and Device configuration policies to Settings Catalog and will be blogging about them in the coming weeks. Thanks for reading. 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