There's a new home for Articles. Find Articles on Our Product Support Page.
Hi I've had a report that new XCover 4s's are failing to enroll. The evidence I have so far (I get a device in a day or so to verify) is that they are following standard procedure for a new build by entering afw#mobicontrol at the verification screen. When they get to the enrolment screen they enter the key, press enrol and it fails. There is nothing in the logs to show an attempt has been made. They have tried multiple WiFi connections (although how could they download if not) and no working SIM is installed yet. I have tried a 4S I have in the office and that enrols fine. Other devices (Samsung XCover 4) have enrolled in the last few days. server is 14.4.9 Does anyone have any suggestions of things to try?
please, is someone could help me find a solution to this error message that appears on my screen when trying to enroll a laptop with Windows10 professional 1909 os/version : 18363.900 to a Soti-MC cloud instance, knowing that LDAP is already successfully configured on Soti-MC settings, as well as a modern windows rule
Hi, We decommission old devices off the Soti server. We wipe, unenroll and delete them. We need to stop these devices from being enrolled again or with permission from an administrator. Is this possible. Regards,
Hello, I am receiving the following error when trying to enroll a Windows 10 device into our test MobiControl environement What should I do? MDM Enroll: Server Returned Fault/Code/Subcode/Value=(a:InternalServiceFault) Fault/Reason/Text=(The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.).
Hello, Im looking for guidance and input if an API can be created to create a device add rule for Android Enterprise devices. The reason for this is simply to automate our enrollment process. Using a Service manger too where the user request to enroll a device and after approval an Enrollment URL is created. I have some API's already to gather information from devices but nothing this advance.
Hi guys, When I enroll Samsung XCovers 4s with Android Enterprise agent - I cant browse them afterwards via USB from pc - or I can actually see the device under My Computer, but it's empty and I dont have the option on the device for "Use USB For: File transer" No restrictions are set. It work without enrollement Any good ideas?
My client has On Premise installation, and i use enrollment URL & their close network to enroll the device to MC. Their device is Honeywell CT50 and i enroll it to A+. one strange thing is, 2 device can't enroll to the MC after i wrote down the enrollment URL in MC apps (while use close network). So i change the network, i use the WiFi, and suddenly it works, the device enroll to MC. It make me confuse since it's on Prem, so i dont think the open network can read the server. is there any particular thing that i need to check? the device going well, nothing happened after the enrollment, but i just want to share it here to prevent some future problem. Thank!
I have followed the steps to enroll an apple BYOD device but get the following error when I try to connect using the url on the apple device. Including setting up the apple push notification service and setting up the rule appropriately. "Your device is not authorized to enroll using the specified enrollment details" Could you please tell me what I might be doing wrong
Hello all, We have mobicontrol on version v13.3.0.3454 we have a lot of device under Zebra TC75X (android 6) who are enrolled by android +. Last week, I've try to update OS android 6 to 7 with stage now and mobicontrol script. The result is ok, my OS is well updated to android 7 and the device STILL enrolled AGAIN (profile, rules, …). All seems to work fine. Nice nice nice :). Well,for to be quiet :) for a certain period of time, we think to migrate to android 8 oreo. But sorry, for me it's not clear I have some question about this. a) Is it possible to jump to android 6 to android 8 directly ? Or it's better to migrate to 7 and after migrate to 8 ? b) Is it possible to enroll an android 8 with android + ? Because, I've read that now for android 8 we must to used android entreprise !!!! c) Why it's not possible to enroll android 8 with android + ? Also, could you tell me if there are some big difference between android entreprise and android + ? All our rules will be work again with android entreprise or we need to review all ? All information is welcome. thanks for your time
Hey there, I am trying to move some devices to a new install of Mobicontrol on a different server. I have a new SSL cert in place and have had some success enrolling new Android+ devices to it. I had some keep giving me "Connection to server failed, an error occurred during the process". I was able to get some devices to work moving between servers if I choose the remove certificates when unenrolling. However, a customer site cannot re-enroll their devices without this error. I have a ticket open but wanted to see if others were able to freely move devices around servers as I think should be allowed. I wonder if it is a certificate issue? Also, it seems like if I enroll with one server I am locked in, and try to enroll elsewhere and get this error. Now I cannot enroll devices from the new server back to the old: 2019-10-29 14:06:59,714 (0x00001da8) [INFO] MessageQueue::<AddWorkerThread>b__49_0() [328] New worker started2019-10-29 14:07:10,633 (0x000012f8) [INFO] MessageProtocolHandler::<Start>b__33_0() [ 31] PulseChecker enter: Send: False, Check: True, Memory: 120382192, ThreadPool: 32767, 999, Queue: 0, Workers: 202019-10-29 14:07:10,633 (0x000012f8) [INFO] MessageProtocolHandler::<Start>b__33_0() [ 31] PulseChecker exit: Total: 28, Connected: 4, Dropped: 0, Retried: 0, finished in 0 ms2019-10-29 14:07:26,998 (0x00000e8c) [INFO] Client::Accept() < 75> Comm.Client.2042: Accepted a new connection from [::ffff:173.162.166.161]:26610.2019-10-29 14:07:27,154 (0x00002b94) [INFO] <OnReceived>d__44::MoveNext() <210> Comm.Client.2042: Client [::ffff:173.162.166.161]:26610 authenticated. Cipher: Aes256/2562019-10-29 14:07:27,295 (0x000030fc) [ERROR] CCommDeploymentSrvWorker::OnInstallStatusMsg() OnInstallStatus: Error 2 getting device info, connection 2042, device 87f4230b56ef7bdc2019-10-29 14:07:27,420 (0x00002fbc) [ERROR] <OnReceived>d__44::MoveNext() <405> Comm.Client.2042: Connection with [::ffff:173.162.166.161]:26610 has been reset.2019-10-29 14:07:27,420 (0x00002fbc) [INFO] MessageQueue::AddNewWorker() <405> MQ: Queue length 1, total threads 20, waiting threads 0, adding 1.2019-10-29 14:07:27,420 (0x00002e88) [INFO] MessageQueue::<AddWorkerThread>b__49_0() [403] New worker started Support is talking about doing a factory reset, which is a big issue for my distributed machines.
Hi,Using a device enrolled as Android Enterprise; When enrolling the device tries to get a Google Account but the kiosk is locking the device down before the device completes getting a Google Account.This means that when in the Kiosk there is a message at the top of the screen saying "user action pending" and I can't use the Application Catalog. Am I doing something wrong?
Hello Guys, has anyone encountered a Bug where you have to enter the Enrollment PIN exactly 2 Times? When i start the Agent i get a prompt for password, i then need to enable keyboard ( only numberfield on CN51). After that ill type in the PIN and i tested this multiple times, so PIN was 1000% correct, but after entering screen goes back to the "Enther Enrollment PIN". Entering the PIN again is then succesful.. Agent(A+): 13.6.0.1045 MobiVersion: 14.2.2.1170 Thanks in Advance.
Is there other variables that can be passed though the KME profile using the Custom JSON Data field that is being used for the enrollment ID to the MobiControl Agent? It would be helpful in my provisioning process to register a WIFI network or set timezones and other things supported by the QR codes or INI file. https://www.soti.net/mc/help/v14.1/en/console/devices/managing/enrolling/platforms/knox/knox_me_link.html
Hi everyone, i have some trouble enrolling my devices with LDAP on MC version 14.3 The server cant find my users or groups. It was working without anyproblems before i updated MC from 14.2 to 14.3. I noticed in the directory service connections the new pane "ID" atgroup attributes and user attributes. This pane seems to be new andit is used for the GUID ( Globally Unique Identifier). But our LDAP dont have this attribute. Do i need the GUID to get myenrollment with LDAP work again? Or has someone else the same issue?
Hi everyone, some customers asking me if its possible to enroll some interactive whiteboards.Their whiteboards are running with the android 7 and android 8 os. I thought that i could enroll them by using the android generic agent. But i had noluck. And the generic client is end of life. So my question is if it's somehow possible to enroll such devices? Does anyone have experience with it? Or is it impossible (at the moment?) to enroll interactive white boards based on android? Thank you.
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points.
Highly experienced members with valuable inputs. Should have more than 700 points.
Beginners taking the initiative. Should have more than 500 points.
New contributors starting their journey. Should have more than 250 points.