Thank you for reply did you also have Cloud Connector pointed on the load-balancer of AWCM servers ? (and if so, was it 1 CC or 2 ?) We specifically have problem with the CC attaching itself only ...
See more...
Thank you for reply did you also have Cloud Connector pointed on the load-balancer of AWCM servers ? (and if so, was it 1 CC or 2 ?) We specifically have problem with the CC attaching itself only to one AWCM and leaving others without this function.
Hello we have changed our UEM on-premises environment from: single instance DS/AWCM (device services + AWCM) server single instance AC (AirWatch Console) server single instance CC (Cloud Connect...
See more...
Hello we have changed our UEM on-premises environment from: single instance DS/AWCM (device services + AWCM) server single instance AC (AirWatch Console) server single instance CC (Cloud Connector) server to having load-balanced 5x DS/AWCM, 5x AC but still only 1x CC CC is now being pointed to the load-balancer before DS/AWCM servers DS and AC seem to be working fine, but AWCM function is always only active on 1 DS/AWCM node, which means any queries to authenticate Active Directory users will fail four times out of five. It does not seem the load-balanced server are able to share Cloud Connector facilitated authentication service What is the correct way to fix this issue. Do we - for example: need as many CC servers as we have AWCM servers, each CC being directly pointed to partilucar AWCM, instead of Load Balancer? or just have as many CC servers as we have AWCM servers, but pointed to LB before AWCMS? or is there some other trick to it? Because VMWare support was telling us, that we can have just one CC pointed to LB before AWCM nodes, but that is clearly not working right, with only one AWCM at time being able to process auths. appreciate any help from ppl having experience with load-balanced on-prem scenarios
Hello Rafael indeet that is what we used to solve the issue, sorry not updating the thread. It is a pitty the 23.2.0.25 cummulative patch states, that it requires any 23.2.0 version, while it in fa...
See more...
Hello Rafael indeet that is what we used to solve the issue, sorry not updating the thread. It is a pitty the 23.2.0.25 cummulative patch states, that it requires any 23.2.0 version, while it in fact requires 23.2.0.23 full version to begin with. cheers Jan
Hello attmpting to upgrade on-premise WSONE UEM 23.2.0.17 to version 23.2.0.25 results in Windows application installer failing to initiate with error: " The upgrade patch cannot be installed by t...
See more...
Hello attmpting to upgrade on-premise WSONE UEM 23.2.0.17 to version 23.2.0.25 results in Windows application installer failing to initiate with error: " The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch " Going from 23.2.0.17 to 23.2.0.25 should be possible, so I do not understand why is the installer complaining or not recognizing the 23.2.0.17
Hello we need to migrate WSONE App server (Console+Device Services) but the App server is currently on "patch" version not "full" version. If I Install for example FULL version 21.11.0.3 will it al...
See more...
Hello we need to migrate WSONE App server (Console+Device Services) but the App server is currently on "patch" version not "full" version. If I Install for example FULL version 21.11.0.3 will it allow me to connect it to existing Database with version 21.11.0.24 and subsequently patch the Application to 21.11.0.24? Obviously, there is not FULL installer available for some patches.
Hi, have you migrated DB to new server recently? The reason I had the problem was, that after migrating server from SQL 2008 to 2012, I had made sure to re-create the DB owner so as not to have p...
See more...
Hi, have you migrated DB to new server recently? The reason I had the problem was, that after migrating server from SQL 2008 to 2012, I had made sure to re-create the DB owner so as not to have problem with right to database, but I forgot that the SQL DB jobs in scheduler also have owner - which was orginal owner from 2008 DB.. So for me it was failing because I was missing rights to manipulate database jobs - when I manually changed owner of all the AirWatch jobs to the new AirWatch DB owner, update succeeded.
We have strange behavior where console device inventory filters do not work on PCs in internal network but work in different network. When you try to aplly filter - like click device type Andr...
See more...
We have strange behavior where console device inventory filters do not work on PCs in internal network but work in different network. When you try to aplly filter - like click device type Android, it very shortly spins the wheel, but you can tell its not working - when it is working the wheel spins longer and then applies filter to inventory you see. We can't figure out why different networks affect console behaviour in this way, because you obviously have console access from both networks. PS: affects both IE and Chrome browser anyone seen this?
Hi Daniel, thanks for the tip, will try. PS: We seem to have somewhar similar issue with AirWatch Launcher - works on classicaly enrolled devices, but gives error in Launcher profile when in An...
See more...
Hi Daniel, thanks for the tip, will try. PS: We seem to have somewhar similar issue with AirWatch Launcher - works on classicaly enrolled devices, but gives error in Launcher profile when in Android for Enterprise.
Hello we cannot make VMWare Boxer work on work-managed (Android for Enterprise) devices. Boxer is pushed to device, but when it is configuring (after user inserted password) it will show message:...
See more...
Hello we cannot make VMWare Boxer work on work-managed (Android for Enterprise) devices. Boxer is pushed to device, but when it is configuring (after user inserted password) it will show message: ' Action is not allowed - This action is not allowed, contact you administrator.' On legacy-enrolled Androids it works fine. Even when we legacy-enroll the same device that was before not working under AndroidfE. We are on version 9.7.0.3. Anyone seen this?
Hello One of customers reported to us recently (29. Sept), that Boxer enabled androids exhausted limit of ActiveSync devices in their exchange. User devices were showing multiple times in Exch...
See more...
Hello One of customers reported to us recently (29. Sept), that Boxer enabled androids exhausted limit of ActiveSync devices in their exchange. User devices were showing multiple times in Exchange management (as ' BoxerManagedAndroid' ), so after limit of 10 was exhausted, that user could no longer connect to mail. I'm not sure why that started happening all of the sudden. Could be some issue with newest version from Playstore?
One thing that *might* be similar: One customer reported to us recently (29. Sept), that Boxer enabled androids exhausted limit of ActiveSync devices in their exchange. One device was showing mu...
See more...
One thing that *might* be similar: One customer reported to us recently (29. Sept), that Boxer enabled androids exhausted limit of ActiveSync devices in their exchange. One device was showing multiple times in Exchange management, so after limit of 10 was exhausted, that user could no longer connect to mail. I'm not sure why that started happening all of the sudden. What is the version of Boxer you are using? Could be some issue with newest version from Playstore.
We are on SQL 2012 as well. Originally, it was on SQL 2008 but was migrated about 1/2 year ago. Migration went without problem. This is the first upgrade after migration.
Hi Don, tried both 9.1.4 and 9.1.5 with the same error, the server was rolled back so cant get more logs, but will keep eye on what you suggested next time
Anyone seen on-premise DB upgrade error: ' AWRunSQLPackageCMD returned actual error code 1603' ? Can't figure out what causes it. Upgrading from on-premise AW 9.0.5.0
