spg123

Thank you very much for your response. I found that we had Authnmethodsreferences instead of authnmethodsreferences (case sensitive). By changing it to authnmethodsreferences, the auth loop stopped and we can see in the Entra ID log for this event "MFA requirement satisfied by claim provided by external provider". Cheers!

Hello, We’ve been experiencing an issue with Autopilot for the past month or so. Initially, authentication works fine, but when it comes to creating the Windows Hello for Business PIN, it redirects to our On-Premise Workspace ONE Access instance instead of the Microsoft side, where we used Microsoft Authenticator. I’m not sure why this change occurred, but Workspace ONE Access gets stuck in an authentication loop during PIN creation. After clicking “Skip for Now” following the error, I can still access the Desktop and authenticate to Intelligent Hub, Microsoft 365 via Edge, Office apps, etc. However, attempting to create the PIN through Settings > Accounts > Sign-in Options > PIN (Windows Hello) results in the same error. From an existing enrolled Windows device, if I click Settings > Accounts > PIN (Windows Hello) > “I forgot my PIN,” it does the same thing. Does anyone have any idea what could cause the Windows Hello for Business PIN to redirect to our Workspace ONE Access On-Prem (which is federated with M365)? I actually wanted this setup, and if it could work, that would be perfect. We have always had SSO for Microsoft 365 set up this way but it never did it for Windows Hello for Business PIN creation. Thanks!

Hello, Thanks for your response. I tried the keytool method but it required a password that I did find documented (before my time). However, after 3 days of our company not being able to set up any new devices, and much begging, Omnissa Support finally provided us with the full installer to be able to renew the AWCM certificate. Most likely will look for another MDM provider now for our company.

Hi Omnissa Team, This is good news to hear! Wondering if you would be able to advise when you will be able to give quotes for On-Premise Workspace ONE customers? We can't set up workstations and mobile devices for our employees now since AWCM certificate expired and I see there is a CVE now OMSA-2024-0001 (vmware.com). Support are not able to provide the installers since no active contract (and Omnissa can't do the renewals yet). Hope to hear from you soon. Thanks! spg123

As Antonio advice, you need to create a user profile for this with the Credentials payload. However, the disadvantage of using the Workspace ONE UEM API is that it does not support uploading previous S/MIME certificates. It is only support in the web-based administration portal. So if you have an S/MIME certificate that is valid for 1 year, and you send the new one to the Workspace ONE UEM API then all other certificates will be removed and only the latest one will be there. This is OK for new S/MIME encrypted email, but any other S/MIME encrypted email that is older than 1 year will not be able to be read on the device.

Hi everyone, I was wondering if anyone knows if there is a way to update the SSL certificate for the AWCM without the full installer? (On Prem UEM). We have been trying to renewal our support for I think 7 months now but no luck. It seems that they can't issue the renewal quotes. We have lost access to create support tickets and to the Workspace ONE full installer/patches. Since today, none of our devices check in, and we can't enrol devices. Seems no communication with Directory Services or Certificate Authority also. Anywho, I thought I would try my luck here (I also telephoned today and they created a ticket for me but issue not resolved yet). EDIT: Updated Site Bindings in IIS and devices are checking in again. Enrolments do not work for new employees (since it sync with AD - error message below). Can't get certificate for Wi-Fi or Ethernet/802.1x either since AWCM cert is expired too) Check Connection Failed, probably due to ACC settings misconfiguration(s). AirWatch.CloudMessaging.Client.AwcmClientException:The AWCM server's SSL certificate is not trusted.. Thanks! spg123