Managed app configurations for Windows devices

AutoUpdateDeferredByDays

Defer automatic updates by one to thirteen days past the staggered release end date.

Integer from 1 through 13

NOT_SET

Hide the Device Health page, or hide specific health checks in Okta Verify on end-user devices.

NOT_SET: Displays all device health check functions in Okta Verify on end-user devices.

Disabled: Hides and stops all device health checks in Okta Verify on end-user devices.

HideOSUpdate: Hides the OS version check in Okta Verify on end-user devices. All other device assurance checks are enabled.

HideDiskEncryption: Hides the disk encryption check in Okta Verify on end-user devices. All other device assurance checks are enabled.

HideBiometrics: Hides the biometrics check in Okta Verify on end-user devices. All other device assurance checks are enabled.

You can select multiple values. Separate the values by using a semicolon. For example: HideOSUpdate;HideDiskEncryption

If the value contains Disabled, the Device Health page isn't displayed in Okta Verify.

NOT_SET

EnableZTAPlugin

Configure whether the CrowdStrike endpoint detection and response (EDR) manifest file is deployed to devices during Okta Verify installation.

See Manage endpoint security integration plugins for Windows.

TRUE: The manifest file is deployed to devices during Okta Verify installation.

FALSE

EnrollInBetaProgram

Configure whether users can enroll in the Okta Verify beta program on their Windows devices.

NOT_SET: Users aren't enrolled in the beta program. To enroll, users open Okta Verify and select Join our beta program on the Settings page.

FALSE: Users aren't enrolled in the beta program and can't enroll by selecting Join our beta program on the Okta Verify Settings page.

NOT_SET

EnrollmentOptions

Configure whether end users are prompted to enroll in Okta Verify. You can reduce the number of user prompts or control the rollout of Okta Verify and Okta FastPass in your org.

SilentEnrollmentDisabled: Default. Users are prompted to add an Okta Verify account only if they click Sign in with Okta Verify.

Enabled: Users are always prompted to add an Okta Verify account.

Disabled: Users are never prompted to enroll in Okta Verify unless they open the app and click Add an account.

SilentEnrollmentDisabled

LogLevel

Configure the log level for the event viewer.

None, Critical, Error, Warning, Info, or Debug

Warning

OrgUrl

When you configure this flag, the org URL is included in on the user's enrollment page and automatically deploys updates to Okta Verify when available. See Deploy Okta Verify to Windows devices for more information.

<Fully-qualified domain name> or <org URL>

Empty

Configure the PAC file path for the proxy server. When you set the PAC file location, the AutoUpdate Service is updated (C:\Program Files\Okta\UpdateService\Okta.Coordinator.Service.exe.config).

Proxy settings can be configured at installation time using a ProxyURL or ProxyPacLocation argument, depending on the customer's proxy setting.

A configuration is created:

During installation:

OktaVerifySetup-X.X.X.X-YYYYYYY.exe ProxyPacLocation=<pac-file-location>

If you use spaces in the password, enclose it with double quotes ("").

The password is encrypted before it’s stored in the service configuration file. The password is decrypted by the value set in the ProxyPasswordEntropy flag.

If you use this flag, the ProxyURL and ProxyUsername flags are also required.

For example, GhKan2a_ya12

If you use this flag, the ProxyUsername and ProxyPassword flags are also required.

A configuration is created:

For example, https://example.com:2035

During installation:

OktaVerifySetup-X.X.X.X-YYYYYYY.exe ProxyURL=https://proxy.sample.com:3888

If you use this flag, the ProxyURL and ProxyPassword flags are also required.

The Okta.Coordinator.Service.exe.config file is updated:

For example, proxyUsername