Simon Frankiewicz

There is no information in the troubleshooting about these profiles. Additionally, updating iOS did not solve the problem. Do you have any other ideas what these profiles could be?

Hello, my question about Workspace ONE Access without LB has been solved. In addition to the changes that needed to be made, I had an incorrect Root certificate from Workspace ONE Tunnel. I don't know if this could be the problem, but it worked for me almost immediately. When I downloaded the Root CA certificate from the Customer group, the problem was solved. Previously, it was downloaded from the Global group Tomorrow I will add an entry in the community of what I have set up, maybe it will be useful to others..

Hi, I'll try to update the devices. I can't download the profile because it's the production environment of one of my clients.

check in pool settings if current snap is visible. Because I don't know if you had the same problem I had when I deleted old snaps. And then when I upgraded snap version it actually didn't find snaps.

Hello everyone, I have a strange problem with Apple devices, on some devices I have profiles that are deleted but I can't see what these profiles are. Can someone tell me what this could be. The devices are added from the Apple Bussness Manager system, they were added to ABM using the Apple Configurator application from MAC OS, I have a theory that these are WiFi profiles, but I can't confirm it. I have console version 24.02.0.13 If it is not possible to determine what these devices are, maybe it will be possible to delete these entries? Sorry for the screenshot in Polish, but that's what I received from the client.

Hi, I talked to a friend who also had problems in version 23.12.1. From what he said, the version should be upgraded to 24.06. I am currently using this version and have not encountered this problem.

Hi @Sascha Warno I also struggled to understand the LB settings for Android Mobile SSO. Can you advise how to set up MobileSSO for a single-node server instance bypassing LB.

Hello What happened to the kb.omnissa.com website the website is down and redirects to salesforce. Will the website come back or is there any change?

I encountered this setup back in 2018 while implementing a system for a client who had the collation set to SQL_POLISH_CP1250_CS_AS, which was already problematic back then. At that time, we had to create a dedicated SQL Server cluster. While Googling this issue, I found a blog about Workspace ONE (Airwatch) where it’s mentioned that both the database and SQL Server are required to be in this collation. But I find it surprising that VMware, and now Omnissa, haven’t updated this in the documentation. Link to site: WS1 SQL Database :: Workspace ONE Knowledge Base This misleads both the engineer and the customer into thinking there’s a different requirement. With a dedicated SQL Server, it’s not an issue, but it becomes problematic when it's shared. Also, why doesn’t this issue appear in lower versions of UEM? Additionally, while updating two environments today, I noticed that clients have the collation set to Polish_CI_AS on their SQL Servers, which prevents me from updating the systems to higher versions. Could someone from Omnissa advise on how I can convince the client to make changes to the SQL Server instance and how we can promote continued use of Workspace ONE UEM products? At the moment, it looks doubtful that the client will want to stick with Workspace ONE UEM.

You looked at this article it will leave integration with EJBCA. Integrate EJBCA as a Certificate Authority in Workspace ONE UEM - vEUCaddict I also found a problem described on the EJBCA project's GITHub. Maybe something can be determined. https://github.com/Keyfactor/ejbca-ce/discussions/638

From what I managed to check, the problem during the update is due to the SQL Server settings, specifically the incorrect collation setting for SQL Server itself. However, I was able to change the SQL Server settings. I used this guide:How to Change Your SQL Collation Settings The biggest problem, which seems significant to me, is that most of the on-premise instances are running on a shared SQL Server. I’ll ask the engineers at Omnissa another question: why don’t older versions, such as version 24.02, show this issue, while version 24.06 reports this problem? Of course, I understand that the documentation specifies that the collation must be set to SQL_Latin1_General_CP1_CI_AS

Initial Tests of the New AMAPI Registration Method: Observations Pros: Enrollment process without downloading the Agent – this solves the issue of downloading the Agent, particularly if it cannot be downloaded from the Google Play Store or if a Google account is not present on the device. Simplified process – it only requires entering the Tenant Token, which is permanently assigned to the integrated account. Cons: Additional UEM authentication window – after entering the Tenant Token, an outdated authentication window opens, which does not scale properly and lacks automation, complicating the process. This issue does not occur in the version with the Hub Agent. Application status does not update in the UEM console – after completing the process, applications are installed on the device, but their status does not update in the UEM console. Summary For now, I consider this functionality an interesting feature that offers additional possibilities, but it still requires refinement.

I would like to join the question. I have a slightly different problem with Mobile SSO in the on-Premise environment. I have done SSO login to the MS365 portal. I want to do Mobile SSO for Android to the MSTeams application. What configuration options do we have. Should I use Cloud Certificates or would it be better to add Mobile SSO support? I once configured Mobile SSO for Android, but it never worked for me. I tried for SAAS and on-premise environments. Do you have any suggestions?

Thanks for the tip, uninstalling the packages solved the issue.

Let me know if you can and if the connector is now working properly.