No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
I'm not sure if anyone's able to assist and where I have gone wrong. I have been tasked with setting up an entirely new Soti Mobicontrol server instance, for the most part all seems to be going well, however Web Console and MobiControl Search Services are greyed out. I am unable to access a web console at all, despite the other services (barring a certificate issue related to iOS which we aren't interested in currently) all showing green. This is an On Premises version, running 15.4.1. Am I missing something? I checked over the help guide but there was nothing there illustrating whether this kind of scenario came up, unless there are more extensive help guides anywhere. Thank you
Hi, I want to move our only SotiMobicontrol server to another Windows server. Are all data, profiles and packages saved in the database?
Hi all, I currently have a single MobiControl server hosting both the deployment and management services. Due to our security departments concerns, we have to disable TLS 1.0 and 1.1 in the near term. I tested this with our current environment, and although it seems that the web console works fine, all of our Windows Mobile devices were unable to connect once disabled. Re-enabling TLS 1.0 allowed the devices to reconnect. Soti support confirmed that older versions of WM may not support TLS 1.2. So, as a way around this, I need to separate out the deployment server and management server into 2 servers so I can have the web console on it's own instance with TLS 1.0/1.1 disabled, and then the deployment server for the device communication will have them enabled. I can then whitelist the firewall for TCP/5494 for only the source device IPs which we will always know to make our security team happy for that and also https will not have TLS 1.0 enabled. Is there a best path to make this happen? I know that multiple deployment servers can be used in an environment, so does it make sense to setup another server as a "failover" and then can have a way to migrate into that new server permanently? Or, can I just build a new deployment server, stop the services on server 1, start the services on server 2, and then make a firewall NAT change to send traffic from our current public IP (and same URL) to send TCP/5494 to the new server? Thanks for any help or advice.
Hi everybody. We just set up our second Management Server next to the existing one. Search Index Service is now running on both of them. We experienced a situation where we couldn't see all of our devices in the device list (only 1.500 out of 4.500). Before this situation we shut down Management-Server 1 (for testing reasons).We then started Management-Server 1 again and 1 minute later we shut down Management-Server 2.After that the device list was not complete. Management-Server 2 had to be restarted for the device list being complete again. A forced Search-Index-Sync via console settings was not successful before. I think this behavior has something to do with the way the Search Indexes are working and communicating with each other. 1) Does anybody know how the sync is working? 2) What happens when we shut down one Management-Server? Regards,Simon
Hello. Does anybody have any experiences in loadbalancing Management Servers? Did anyone run into problems especially when using ERG servers pointing to LB-VIP? Are there any references in how to configure session stickyness on LB? And what about the Search Index service which is running on the first Management Server? Regards, Simon
Hi, Last Sunday, I upgraded MobiControl from 14.0 to 14.0.2 and it's been a nightmare since. I had no issues with 14.0, but the upgrade to 14.0.2 has been regretful. Apart from dealing with SSL certificate issues, the biggest problem is MobiControl services continuously stopping for no reason. Right now, the Management Service continuously crashes every 5 to 15 minutes or so. Event Viewer shows the following: Faulting application name: Soti.MobiControl.ManagementService.Host.exe, version: 14.0.2.264, time stamp: 0x5a20b632 Faulting module name: clr.dll, version: 4.7.2558.0, time stamp: 0x59d414b7 Exception code: 0xc00000fd Fault offset: 0x000000000001358b Faulting process id: 0x1190 Faulting application start time: 0x01d3938af831b940 Faulting application path: C:\Program Files\SOTI\MobiControl\Soti.MobiControl.ManagementService.Host.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: 51619607-ff7f-11e7-80ce-005056acfd5b Faulting package full name: Faulting package-relative application ID: MobiControl's Management Service log mentions the following failures: * Exception: A task was canceled. * [InternalLogicException: Failed to send HTTP request to proxy target] at Soti.MobiControl.Ngui.WebConsole.Handlers.ConsoleApiProxyHandler.d__4.MoveNext() * Exception: Cannot access a disposed object. Object name: 'System.Net.HttpListenerRequest'. * [ObjectDisposedException: Cannot access a disposed object. Object name: 'System.Net.HttpListenerRequest'.] Here's a new one I haven't seen before (yet more certificate errors): Exception: The message could not be processed. This is most likely because the action 'http://tempuri.org/ICacheProxyService/GetByKeys' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding. * I noticed this occurs when a technician loads the WebConsole on their first login/session (and then subsequently receives an HTTP 404 error). We then have to wait a few minutes for the service to restart, or restart it manually if the application crashed too many times. On average, the service crashes at least ten (10) times in an hour. I've tried upgrading the .NET Framework runtimes to 4.7.1 to no avail. I also upgraded Java to the latest 1.8u161 and saw no improvement. Searching the web for this type of error yields many results, including one about a Microsoft-supplied hotfix and another about switching .NET JIT compilation modes. Virtual machine specifications: Windows Server 2012 R2 Standard Microsoft SQL Server 2014 SP2 Express 2 vCPU cores with 8GB of memory 2-tier Enterprise PKI for certificates, trusted by all computers One thing I'd like to mention is that MobiControl's WebConsole is served via a NGINX reverse proxy with its own public SSL Certificate from Let's Encrypt (separate machine) while port 5494/5495 is NAT'ed directly to the MobiControl server. This setup worked flawlessly on 14.0. The only certificate I have overridden in MobiControl is the "Deployment Server Extensions and Web Console" while the insecure RSA1 1024-bit original MobiControl Root CA and related certificates still handle everything else. I'm more than eager to change them to our PKI certificates, however I'd like to sort out the current issues at hand first. Anyone else experiencing issues with the latest update or can provide some insight into the matter?
I have manually deleted MCAdmin.exe config file as I was constantly facing issue while starting MS and DS service [Error 1053]. Then while starting MCAdmin, it was giving me an error "A fatal error occurred...".
I'm curious to know what is the communication, data exchange happened between MS and DS on port 5495 in the segregated environment or even when both are in the same environment, what is the data exchange happened between them?
Not everyone can run MobiControl server components as Local System. Some may wish to run MobiControl Server components as a Service Account that is registered in a domain. What Permissions are needed for MobiControl to run as a Service Account?
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.
