End User Elevation: Custom Branding

The user-facing screens for Evo End User Elevation can be customized and branded to feature either your MSP’s or your customer’s own branding, providing a professional and custom experience for users.

We believe this is an important capability - beyond simply being a premium-feeling experience - because users increasingly encounter generic “security warnings” that are in fact security threats. Displaying clearer specifics of brands and entities that they trust gives users improved cues for valid warnings versus those that are potentially misleading.

The items boxed in red can be customized:

The branding is accomplished by using custom registry settings described in this .reg file snippet:

Windows Registry Editor Version 5.00

; EvoConsentUI customization keys ; Import this file with elevated privileges (Administrator) ; HKLM path: SOFTWARE\EvoSecurity\EvoLogin-CP\Customization

[HKEY_LOCAL_MACHINE\SOFTWARE\EvoSecurity\EvoLogin-CP\Customization] "ConsentUI.BrandLogoPath"="C:\\ProgramData\\YourMSP\\brand.png" "ConsentUI.WindowTitle"="Privilege Request" "ConsentUI.HeaderText"="Administrator Privileges Required" "ConsentUI.IntroText"="This action requires administrator privileges:" "ConsentUI.GeneralPrompt"="Would you like to request administrator privileges for this action?" "ConsentUI.ReasonLine1"="This application needs special permissions to run." "ConsentUI.ReasonLine2"="Please tell us why you need to use it:" "ConsentUI.ProcessingText"="Validating request..."

Activating the branding parameters is accomplished by importing your customized version of this .reg file into the Windows Registry under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\EvoSecurity\EvoLogin-CP:

Additionally: You could have the.reg file saved locally (Example: "C:\Temp\EvoConsentUI.reg”) and then push the File via PowerShell with a one liner.

& "$env:WINDIR\regedit.exe" /s "C:\Temp\EvoConsentUI.reg"

This script invokes the “EvoConsentUI.ps1” we created and will need to be saved locally at your desired path when you plan to Deploy. Script:

[CmdletBinding()] param() #requires -RunAsAdministrator

$CustomizationParams = @{

#comment out a line with a # sign in front if you want to ignore... BrandLogoPath = "C:\ProgramData\YourMSP\brand.png" WindowTitle = "Privilege Request" HeaderText = "Administrator Privileges Required" GeneralPrompt = "Would you like to request administrator privileges for this action?" ReasonLine1 = "This application needs special permissions to run." ReasonLine2 = "Please tell us why you need to use it:" ProcessingText = "Validating request..."

}

$RootCustomizationPath = "hklm:\Software\EvoSecurity\EvoLogin-CP\Customization" if (-not (Test-Path $RootCustomizationPath)) { New-Item $RootCustomizationPath } foreach ($key in $CustomizationParams.Keys) { $value = $CustomizationParams[$key] Set-ItemProperty $RootCustomizationPath "ConsentUI.$Key" "$value" }

Example: Save “EvoConsentUI.ps1” to C:\Scripts Locally > CD C:\Scripts in Administrator PowerShell > Run Basic Install Script