We have an issue with our SMC 5.1 product only processing tasks immediately after the SMCSVC service is restarted. This applies to all tasks including provisioning of new devices, pushing of profiles and packages. Tasks are received and appear in the task queue in the ‘Accepted’ state, they sit in that state without being actioned unless be restart the SMCSVC service. As soon as the service has been restarted and the application finished starting up the tasks begin processing as expected. If there are many tasks waiting some may move into the ‘delayed’ state and are not processed.
We have found that if we continuing issuing individual tasks one after another they process as expected. If we issue no new tasks for several minutes the server once again stops processing and all new tasks simply sit in the ‘accepted’ state.
Is this normal behavior, are tasks processed on a schedule that we simply have not waited long enough to see or can you suggest a reason why this might be occurring?
This thread was automatically locked due to age.