SOTI Pulse Logo

timebased profile assignment - profile scheduled actions

OA
Ozan Acikalin
JAMBO GmbH

Hey guys,

I am running a test environment with the newest version (14.4.0.4857) of mobicontrol.

The main reason for trying the new version are the enhanced options for profile schedule actions.

I created a simple profile which contains a whitelist for soti surf only. the profiel is also configured
for android plus devices.

Then at the assignment i added the option "restrict profile deployment...." and added
an schedule entry like "Weekday - 14:30-17:00".
After the assignment my devices get the profil informations but remain with the status
"pending install".
When they entering the defined time zone the devices remain with the status "pending install".

About the devices:
Im using three different devices -> Samsung Galaxy Tab A (SM-P580), Huawei Mate20 lite (SNE-LX1),
Huawei M5 lite (BAH2-L09). All three devices are configured as normal android plus devices and NOT as
android enterprse. all of them getting the "pending install" status.

Am i configuring something wrong? Or did i forgot one step to get the time schedule work?

Thanks for the help!

mobicontrol android-plus version14-4 time-schedule
6 years ago
Android
ANSWERS
AB
Aaron B
6 years ago

 I assume that you are also pushing the SOTI Surf APK as part of this or another profile?  I don't know that the configuration in your profile will actually install without the APK present.

RC
Raymond Chan Diamond Contributor
6 years ago (edited 6 years ago)

Have you deployed any non time-limited profile(s) successfully onto your three test devices?  If so, what kind of payloads are there in the profile(s)?

Had your three test devices been enrolled to the server before it was upgraded to v14.4?   If so, were the device agents upgraded after the server upgrade? 

OA
Ozan Acikalin
6 years ago

@Aaron: the soti surf app is already installed on all devices. i am just trying to push a whitelist

@Raymond: i tested with any non time-limited profiles (whitelist, lockdown, packages, etc.) and
i could successfully deploy them on all three devices.
They were enrolled after the upgrade to v14.4 and running with the current agent version for v14.4

OA
Ozan Acikalin
6 years ago

I found the solution.

I used the wrong timezone. I didnt noticed the UTC info...

After using the correct UTC time for my timezone it worked.

Similar Discussions