This article discusses the scenario in which one of the devices previously connecting to Okta as managed now appears to be an unmanaged device.
- Managed Windows Devices
- Okta Verify (OV)
Reviewing the Okta Verify (OV) logs indicated that a failed upgrade causes the issue. To check the Okta Verify logs:
-
Open the Windows Event Viewer:
Use to open the Run command and enter:
eventvwr.
-
Under Applications and Services Logs, click Okta.
|
Information |
02/09/2024 07:16:10 |
OktaUpdate |
8611 |
None |
ApplicationInstaller: Process Launched to upgrade from version: 5.1.3 to 5.3.0 message:CurrentInstalledVersion=5.1.3&AutoUpdateUrl=https://<MyDomain>.okta.com/&EventLogName=Okta&EventSourceName=OktaUpdate&ReleaseChannel=GA&ArtifactType=WINDOWS_OKTA_VERIFY&PipeName=Okta.etc.=. |
|
Error |
03/09/2024 08:18:33 |
Okta Verify |
8120 |
None |
WindowsMessageSender.InformAllInstances: Failed copying data from process 22692 from sender window 0x196760. |
|
Error |
03/09/2024 08:18:33 |
Okta Verify |
8120 |
None |
BindingsManager.HandleCustomUriActivation: Failed to signal the primary instance for URI activation. |
|
Error |
03/09/2024 13:25:04 |
OktaUpdate |
8900 |
None |
ApplicationInstaller: Auto Update will not happen due to exception: System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <ipAddress:Port> at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult) etc. |
|
Error |
04/09/2024 09:36:27 |
Okta Verify |
8120 |
None |
[PrimaryApplicationLaunch][CustomUriRequest][OktaWebRequest.SendMessageAsync]: Call to https://<domain>/idp/authenticators/<id>/transactions/ftjwN3TgqXXWHzr8rCnCw-eWT__kq3DzMEE/verify failed with Forbidden. Request Id: a99a99aa0123aaaaaa9999aa9a9a99aaa |
To ensure a device is correctly recognized as "Managed" by Okta, follow these steps:
- Redeploy Okta Verify:
-
- Deploy Okta Verify to Windows devices.
- Follow the instructions in the linked article to ensure Okta Verify is properly installed and configured on the affected device.
- Authenticate Using Okta FastPass to Establish Managed Status:
To trigger the process that updates the device's management status, the user needs to authenticate using Okta FastPass. Guide them through this initial authentication with a temporary policy:
-
-
Create a Temporary Bookmark Application:
- Navigate to the Okta Admin Dashboard: Applications > Applications > Browse App Catalogue.
- Search for and select Bookmark.
- Click Add Integration.
- Provide a name for this temporary bookmark (for example, "Managed Device Check").
- Enter any working URL (this is temporary and for policy enforcement).
- Click Assign and assign this bookmark app to the specific user whose device is not showing as managed.
-
Create an Authentication Policy Requiring Managed Status for the Bookmark App:
- Go to the Okta Admin Dashboard > Security > Authentication Policies.
- Click Add Policy.
- Enter a name for this temporary policy (for example, "Require Managed Device").
- Click Save.
- On the policy page, navigate to the Applications tab and click Add App.
- Select the Bookmark app created and click Done.
- Go back to the Rules tab for this new policy.
- Edit the Catch-All Rule:
- Click Actions > Edit next to the Catch-All Rule.
- Scroll down to THEN Access is and select Denied.
- Click Save.
- Add a new Rule:
- Click Add Rule.
- Give the rule a name (for example, "Managed Device Allowed").
- Under IF User is, leave the default (Any user assigned to the app).
- Under AND Device state is, select Registered.
- Under AND Device management is, select Managed.
- Under AND Authentication methods, ensure Okta Verify - FastPass is listed as an available option.
- Under When to prompt for authentication, choose Every time user signs in to resource.
- Click Save.
-
Have the user authenticate:
- Instruct the affected user to attempt to access the "Managed Device Check" bookmark from the device that is not showing as managed.
-
Interpret the results:
- Successful Authentication: If the user can authenticate using Okta Verify - FastPass, their device's status in Okta should now be updated to Managed.
- Authentication Failure (Denied by Catch-All): If the user is denied access by the Catch-All Rule, the logs generated by this authentication attempt will provide valuable information for further troubleshooting the underlying issue preventing the device from being recognized as managed. Please collect these logs for analysis: Collect Okta Verify Logs from Desktop (macOS / Windows).
-
