Hi Shannon,

even the video or this video tutorial seem to be somehow a bit outdated it looks like you don't need an agent on Windows modern (not sure if this has changed).

Hi Shannon,

Thank you for posting on SOTI Pulse!

Could you please tell us when the device gets enrolled into the system, does it show Agentless in the device details section? Also, could you please tell us which version of Mobicontrol are you currently running on?

Can you also try clicking the info of that device in Access Work or School as shown in the screenshots below and then click on sync and observe if the agent gets into the device?

Could you please also share the screenshot of the logs section when the ppkg is pushed to the device during enrollment?

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net l Discussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter 

Hi MNMod, the Version of Mobicontrol is 15.6.0.1018.

I'm not sure what you mean by "agentless" in the device details section, but every other device that I had enrolled 2 weeks prior did install the agent (same windows image, same ppkg file, same network)

When I press the sync button in the enrollment details it just shows "sync successful". I have tried re-imaging, removing the enrollment package and re-enrolling, nothing is successful and I have no way to see why.

I don't have any way of manually triggering the agent to install or triggering an attempt to pull it from the server, I have no visibility over why it failed, and all I can do is perform troubleshooting steps that are costly in time with not only no guarantee to succeed, but also no way to see why they failed.

There is nothing in the device logs in mobicontrol, the device shows up in the device group that the enrollment rule places them in, agent connect and disconnect time show "Unknown (NaN hours, NaN minutes ago)".

Essentially all I am looking for is a way to trigger the agent to install and be able to see why it did or did not succeed so that I'm not simply spinning my wheels with my fingers crossed hoping that i'm not just wasting my time with other steps that are likely to be futile seeing as I have absolutely no avenue of discerning the root cause of the issue.

Ok so SOTI support found the root cause. the issue was that the Windows Notification Service in Mobicontrol was not behaving correctly and once that was corrected the devices were able to pull down the agent.

So now my device issues are resolved and these two have the agent installed..

The problem still remains that I had no way for certain of knowing what the issue was and it wasn't even immediately obvious to my SOTI support agent that this was the root cause

Last week, I noticed some errors related to WNS, but as of today, they no longer appear.

I suspect the issue may be related to the WNS configuration, although I cannot yet confirm this with complete certainty.

This is the third time I've had such an issue and the first time we have found the potential root cause.

There needs to be more visibility when this occurs, not only for the end user, but also your own agents.

What is the version and build numbers of your MobiControl server?  Has there been any upgrade done recently?

How long have your MobiControl server and WNS been in production?  

Have Soti support team helped to check whether your WNS configuration had been done properly?

.