How can we help?

Auvik SaaS Management Deployment & Security Considerations

Follow

Auvik SaaS Management deploys its Windows Desktop Agent by running a PowerShell script, typically with administrator permissions, on the target device.

The deployment script configures the appropriate tenant under the Auvik SaaS Management Partner Hub, downloads the Auvik SaaS Management executable from the secured service, installs the Desktop Agent, configures it to run automatically, and installs the required Auvik SaaS Management browser extensions.

For deployment instructions, see Deploying Auvik SaaS Management on a Windows Device.

Software Collector Considerations

The Auvik SaaS Management Desktop Agent runs in the background on the Windows device and starts automatically.

The Desktop Agent:

  1. Monitors mouse and keyboard activity to determine whether the user is active so that application usage can be reported accurately.

    Auvik SaaS Management doesn't collect or report keystrokes, mouse movements, or the content entered by the user.

  2. Determines which window is currently active and reads application metadata to identify which application is being used.
  3. Periodically communicates with Auvik SaaS Management services. The transmitted data includes the user security token, application metadata, and usage information required by Auvik SaaS Management.
  4. Configures browser policies on the local Windows device to install the required Auvik SaaS Management browser extensions.
  5. Communicates with the browser extensions to receive user security tokens and configuration information required by Auvik SaaS Management.

Microsoft Edge extension installation

The Windows Desktop Agent automatically installs the Auvik SaaS Management Microsoft Edge extension using the Microsoft Edge ExtensionInstallForcelist policy.

Because the extension is force-installed using this policy, users aren't prompted to confirm or enable the Auvik SaaS Management extension.

If you're deploying the Windows Desktop Agent, you normally don't need to deploy the Microsoft Edge extension separately through Microsoft Intune, Group Policy, or another endpoint-management solution.

For environments where browser extensions must be managed separately, see Sideloading (installing) Browser Extensions, if required.

Network Considerations (SASE & SSL Proxies)

Auvik SaaS Management requires access to external resources during installation and to communicate with Auvik SaaS Management services.

Review your firewall, software VPN, SASE, SSL proxy, and other network-security configurations to ensure that required Auvik SaaS Management traffic is allowed.

HTTPS Access Rules

Allow HTTPS access to the following domains:

  • deploy.saaslio.com
  • application-dev.saaslio.com
  • application.saaslio.com
  • files.saaslio.com
  • agent-api.saaslio.com

Network SSL Proxies & SASE Tools

If you're using SSL inspection, SSL proxying, or a SASE solution, the security product may intercept or rewrite the Desktop Agent installer's connection to the secured Auvik SaaS Management environment.

Configure the appropriate allowlist or bypass rules for the required Auvik SaaS Management domains.

If SSL inspection prevents the installer or Desktop Agent from establishing the required secure connection, configure your security solution to bypass inspection for the applicable Auvik SaaS Management traffic.

Endpoint Security Considerations

Endpoint-security products such as SentinelOne, ThreatLocker, and similar tools may block the installer, PowerShell deployment process, Desktop Agent, or browser-extension policy changes.

Because Auvik SaaS Management is commonly deployed using a PowerShell command, your endpoint-security configuration must allow the deployment process to run.

You may also need to create allowlist rules for the Auvik SaaS Management installation paths and executable.

Centrally Managed Browser Environments

If your organization manages browser policies through Microsoft Intune, Group Policy, or another endpoint-management platform, review the existing browser-extension policies before deploying Auvik SaaS Management.

For Microsoft Edge in particular:

  • Don't deploy the previous extension ID fbgiiopidibajnhdbmfcbgjkdmehhjck for new installations.
  • The current Edge extension ID is edgejegejhhmhfhdacmmgmkaefkjkjlf.
  • The Windows Desktop Agent automatically installs the current Edge extension.
  • A separate Edge extension policy isn't normally required when using the Windows Desktop Agent.
  • If an existing policy deploys the previous Edge extension, remove or update that policy to prevent both extensions from appearing.
  • Users aren't prompted to confirm or enable the current Edge extension when it's force-installed.

Directory Structure & Important Paths for Auvik SaaS Management:

Paths For Auvik SaaS Management

C:/Saaslio

C:/Program Files/Saaslio/

Executable for Auvik SaaS Management C:/Program Files/Saaslio/win-latest/Saaslio-x64.exe
Executable Name for Auvik SaaS Management Saaslio-x64.exe
Startup Rule for Auvik SaaS Management C:/ProgramData/Microsoft/Windows/Start Menu/Programs/StartUp/Saaslio.bat
Service Name for Auvik SaaS Management Saaslio Windows Agent
Service Short Name for Auvik SaaS Management Saaslio-x64

Browser Extension & Registry Key Considerations

The Auvik SaaS Management Windows Desktop Agent automatically configures registry keys on Windows devices to force-install the required Auvik SaaS Management browser extensions.

Endpoint-security products may prevent the installer from creating or modifying these registry entries.

If browser policies are centrally managed through Microsoft Intune, Group Policy, or another endpoint-management solution, centrally configured browser policies may override locally configured registry values.

In these environments, configure the appropriate Auvik SaaS Management extension using your organization's browser-management policies if required.

Important: Don't deploy an additional Auvik SaaS Management Edge extension policy simply to avoid an expected user prompt. When the current Microsoft Edge extension is installed through ExtensionInstallForcelist, users aren't prompted to confirm or enable it.

For instructions on centrally deploying browser extensions, see Sideloading (installing) Browser Extensions, if required.

Installed Registry Keys for Auvik SaaS Management:

Brave

Key: 

HKLM\SOFTWARE\Policies\BraveSoftware\Brave\ExtensionInstallForcelist

Name: 

839797115

Value: kieikihnfebppciimgpalbdjkjiahnlk;https://clients2.google.com/service/update2/crx

Chrome

Key: 

HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist

Name: 

839797115

Value: kieikihnfebppciimgpalbdjkjiahnlk;https://clients2.google.com/service/update2/crx

Chromium

Key: 

HKLM\SOFTWARE\Policies\Chromium\ExtensionInstallForcelist

Name: 

839797115

Value: kieikihnfebppciimgpalbdjkjiahnlk;https://clients2.google.com/service/update2/crx

Vivaldi

Key: 

HKLM\SOFTWARE\Policies\Vivaldi\ExtensionInstallForcelist

Name: 

839797115

Value: kieikihnfebppciimgpalbdjkjiahnlk;https://clients2.google.com/service/update2/crx

Edge 

Key: 

HKLM\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist

Name: 

839797115

Value: 
fbgiiopidibajnhdbmfcbgjkdmehhjck

Firefox 

Key: 

HKLM\SOFTWARE\Policies\Mozilla\Firefox\

Name: 

ExtensionSettings

Value: 
{"saaslio@saaslio.com":{"installation_mode":"force_installed","install_url":"https://addons.mozilla.org/firefox/downloads/latest/saaslio/latest.xpi"}}

Related Articles

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request