Configure the Enterprise Site List mode the modern way

-
I recently had to deal with a requirement where websites (mostly legacy web apps) designed and compatible to run on IE versions 10 and older, needed to be allowed to run on Edge Chromium. That is when I stumbled on Enterprise Mode which allows rendering websites using a modified browser configuration, designed to emulate legacy versions of Internet Explorer.

Using Intune, I am going to cover the process of creating an Enterprise Mode Site List Manager containing website URLs along with specific render modes and the configuration of Microsoft Edge browser.

Create the Enterprise Mode Site List XML

Download the EMIESiteListManager.msi and install it. Click on Add button which will allow you to add URLs along with relevant Compat Mode and Open In.

For Open in when you choose None, the URL is allowed to open in Internet Explorer and Edge. Choose IE11 to force the URL to open in IE or choose MSEdge to open the URL in Edge. Since my requirement is to allow URL to open in IE, I am choosing IE11.


If you are dealing with multiple URLs, then you can use a TXT file to import URLs in bulk. You can refer to the process over here to get an overview. After adding the URLs, save the XML, which should look something like the one below -


Storage location for the XML

Next up is to create a storage location for the XML. You have an option to store it on an on-premises network share, but the modern way would be to use an internet based location. There are multiple options for internet based locations as well, but the easiest would be to use an Azure Blob storage. I am using an existing Storage account, but if you want to create a new one, then you can refer to the process over here.

If you are using an existing Storage account like me then just follow the steps below -

1. Browse to the Containers tab & Click +Container
2. Give the container a Name
3. Choose Blob (Anonymous read access for blobs only) as Public access level
4. Click OK to create the container
5. Upload the previously created XML file.
6. Once uploaded, check the properties to access the URL.


7. Verify if the URL opens or not.


Intune Settings Catalog Policy

While you have the option to create a Configuration profile using Device Administrative Templates, why not consider using Settings Catalog instead? Microsoft is adding support for new configuration in Settings Catalog regularly and it makes easier to deploy multiple configuration settings, all found under a single hood.

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 the following settings and add them as shown below.


9. Assign to a Security group

User Experience & Policy in action

On accessing the URL from the previously created XML on Edge Chromium browser, user will see the following message.


Since I have enabled the policy of Allow access to the Enterprise Mode Site List Manager tool (User), user can navigate to edge://compat and see the list of Enterprise URLs and other configuration details as shown below.


You always have the option to remove access to edge://compat by disabling Allow access to the Enterprise Mode Site List Manager tool (User) or not configuring it at all.

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