ivan_531

Hi, I noticed that on my newly enrolled PCs none of the provisioned packages is not deployed on endpoints. This was working before, without any problem, but now I can only see the Status: "non-Compliant - In Progress" and Last job status is "Queued" and this is for every my Product, they all stuck in Progress. Also, everything was working few weeks ago and no one didn't make any changes on Airwatch. Does anyone have any idea what could be a problem?

Thanks, It started working now. It wasn't last week, but now I can create service client token.

Seems like this is supported only in cloud (SaaS) version of Access, not on premise.

No, there is no any audit log with type "RuleSet".

When I try to create OAuth Service Client token with my admin account in Workspace One Access Console I only get following error: Unable to retrieve rulesets for the tenant ACCESS My Access tenant is on-premise, but it is publicly accessible. Can anyone help me with this?

Hi, I have my Access up and running, but after I install the Access Connector, the Directory Sync and Auth Sync services are not running. There is only error "Service terminated unexpectedly" When I navigate to Access Admin console page, I cannot see the connectors details there, its empty like new. Connector version is 23.09 In log file for Directory Sync I found this error: com.vmware.vidm.eds.gateway.operations.EnterpriseServiceRegistrationManager - Unable to register EDS ScForbiddenException[Operation: POST -> https://my-access-appliance-hostname/SAAS/jersey/manager/api/enterpriseservices][Status:403] Can anyone help with this?

Hi, UEM is SaaS. Anyway, it was network problem by our ISP, we were able to solve it by rerouting the traffic from Access to UEM

Hi, Our users can't connect to WS One Intelligent Hub to access Apps and enrollment for new users is not working. We only receive "Error Code 500": Everything seems fine in UEM, but on Access (on-premise) I can see that we can't connect with Workspace ONE UEM API Server. We can normally access https://myinstance/API/help/#!/apis from our environment, but from some reason Access can't. Can someone point me where might be the problem?

Hi, I was able to fix this by selecting Device Type "Windows 10+" in Access policy. From some reason, it doesn't work with default "All types".

UPDATE: Here is log from Access for my test user:

Hi, I have a problem with WS One when enrolling new PCs. Problem is only during enrollment process, current users (that are already enrolled) can normally login in WS One Intelligent Hub with OKTA. So, we use OKTA as IDP and that part works fine and I'm able to login with OKTA and see message "Enrollment starts..." but only for few seconds. After that, it stops with Local login screen and message "Failed to validate user credentials." We have configured default Access policy (in Workspace One Access) which primary use "OKTA Auth method" and if OKTA fails, then it use failback which is Local login. The problem is that also local login doesn't work. Previously we used AD login, but now it is the same problem. So, none of authentication methods works from Access. So, I'm assuming that from some reason it doesn't validate OKTA login for enrollment, and then it switch to failback login. This is strange, because login in WS One Intelligent Hub for already enrolled users works fine with OKTA. If we bypass authentication, so the users authenticate directly on UEM (without Access) that works. On other hand, Access is fully connected with UEM, so I'm not sure where is the problem. Did anyone had same issue with WS One? Also, everything works just fine last week, no one didn't touch any configuration and now it doesn't working.