SOTI Pulse Logo

Soti Hub / Content Library

WT
Warren T
Marston (Holdings) Limited

Hi all.

Need some advice and perhaps looking at this completely incorrectly.

Our on-prem instance of Mobicontrol is running version 2024.1.0.1052.

Samsung Tablets ranging from Android 9, through to Android 14.

Android agents 2024.0.1 through to 2025.1.3, enrolled as Android Classic.


It's to my understanding that the legacy Content Library policies were depracated and that the UI on newer versions of the server software could no longer access that element of the system, in favour of Soti Hub.

I am trying to experiment whether a transition to Soti Hub would impact our field workers, because they are contractors they do not have access to any cloud based corporate accounts as its not a requirement nor allowed, yet when I install Soti Hub and try to run it on a test device, only an error message is displayed with a Login button to say to contact an Administrator. I am entirely unsure why I assume its because we are still using the original Content Library policy and that there is a missing configuration somewhere (such as where the documents are located, I did add a configuration to the profile along with the package but kept its default settings).

My questions are as follows:

  1. Can we upload documentation via Hub but have the users continue to access the newly uploaded documents via the Content Library section of the agent on the device?

  2. If not, is there any way we can set up hub to not require the user login with credentials? 

  3. Can the documents be uploaded to the server they're sat on, in the same way as the deprecated Content Library policy? Without the need for the documents to sit on the cloud.

  4. If they can be, how would one go about this? As currently on a test device, I just get an error message and the Hub is inaccessible and I have no way to test beyond this to see how any of this can be achieved without disrupting our field workers.

There is really no clear indication about this deprecation of the Content Library policy, and what we would like to avoid when updating is creating further problems for ourselves. We have hundreds of documents being accessed daily and due to the nature of this and the number of users, we'd like to keep the system this way. 

Any assistance regarding this is appreciated as it feels unless I have missed it somewhere that any instructions to transition isn't well documented.

Thanks

mobicontrol hub Content Library
3 months ago
SOTI MobiControl
ANSWERS
RC
Raymond Chan Diamond Contributor
3 months ago (edited 3 months ago)

Has your MobiControl server recently been upgraded?  If so, what were the version and build numbers of your on-premises MobiControl server when using the content-library policy?  Or have you only upgraded the device agents on enrolled devices in the hope to deploy previous files defined in old content library policies for access using Soti Hub app?

 

Have you deployed profile with Soti-Hub payload to those device(s) that display error message about "contact an Administrator"?

 

WT
Warren T
3 months ago

Hi Raymond

Server version of Mobicontrol is 2024.1.0.1052

The Soti Hub version that was deployed was 2025.1.0

Soti Hub was deployed along with the confgiuration payload to the device, but when we open the app and it begins to load it just says an error has occurred and to contact an IT administrator.

I am unsure if this is because the Hub version is too new to operate alongside our server version or if I'm missing something. I am not entirely sure how the system works to begin with.

I have a support ticket open with Soti on the matter as what we don't want to happen is to lose access to all the hundreds of documents currently available to the field agents and if necessary transition over smoothly to the new sysem should we update the server as these documents are accessed daily and currently I have no way to test this without it working on the current server version before we consider the server update.

A
ASMOD@SOTI
2 months ago

Dear @Warren T 

 Thank you for posting on SOTI Pulse.

 SOTI MobiControl's Content Library automatic migration refers to the shift of its document repository feature from a legacy user interface to the modern SOTI Hub interface, with files now accessed and distributed via SOTI Hub profiles rather than Content Library Policies. This migration is part of updating the system to a new, integrated user experience where document management and distribution are handled through the SOTI Hub app on Android and iOS devices. There is no separate automatic migration process for the content itself; rather, the system for managing and accessing content undergoes a transition as part of SOTI MobiControl updates. 

 It involves reconfiguring your content distribution within a new SOTI Hub profile payload. Instead of using Content Library policies, you will add new content repositories to a SOTI Hub profile, mapping the files and folders you want to distribute from the legacy Content Library into the SOTI Hub app's interface. 

Steps to migrate Content Library policies to SOTI Hub:

  1. Access the SOTI Hub profile payload: 

In the SOTI MobiControl console, navigate to the SOTI Hub profile settings for your Android and iOS devices. 

  1. Create a new content repository: 

Within the profile, add a new content repository to link your content to the SOTI Hub app. 

  1. Configure the repository: 

Specify the details for the new content repository. This includes a repository URL and a path to the files you want to distribute, which will point to the same storage location as your legacy Content Library. 

  1. Add files and folders: 

Under the Files and Folders section of the content repository, add the specific mandatory or optional files and folders from your Content Library that you want users to access via the SOTI Hub app. 

  1. Set up an alias folder (optional but recommended): 

Assign an alias folder to the content repository. This organizes the content under a specific folder name within the SOTI Hub app's "My Library" section, preventing potential confusion if you have multiple content repositories. 

  1. Assign fetch intervals and other settings: 

Determine how often the SOTI Hub app should check for updates to the content repository by setting a Fetch Interval. You can also configure settings like mandatory file fetching and content transfer options. 

  1. Deploy the profile: 

Deploy the updated SOTI Hub profile to your devices to begin distributing content through the new interface. 

Key differences and benefits: 

  • Modern interface: 

The SOTI Hub profile replaces the legacy Content Library policies, offering access to the updated SOTI Hub app on Android and iOS devices.

  • User experience: 

Device users will access content through the SOTI Hub app, a modern interface designed for content access and management.

  • Configuration: 

You configure content distribution using SOTI Hub profiles and their payloads, rather than separate Content Library policies.

 If you have any additional questions or concerns, please don't hesitate to reach out. 

 We're dedicated to providing assistance and support.

Also, if this post has helped you in solving your inquiry, I would request you to mark the particular comment as "is solution", so others may benefit from this information.

 

 Kind regards,

     SOTI

Similar Discussions