Package studio: is there size limit for to upload the pcg to the server ?

Package studio: is there size limit for to upload the pcg to the server ?

Hello all,

we used soti mobicontrol on version : 13.3.0.3454 all works fine

 

Now, for a futur deployement I have a package studio WHO possibly make a size of 180 MB.

Until now, our package as never exceed 60 or 70 MB …

 

Is there a limit for to upload the package (*.pcg) to the server ?

Anyone have some experience with this ?

 

thanks

6 Answers

Order By:   Standard | Newest | Votes
Matt Dermody | posted this 07 March 2019

I routinely distribute Packages in the 1GB range (Zebra firmware updates) so I think you're certainly good with 180MB. With that said, the default DB size allocated to Package storage is relatively low and I have had SOTI recommend that I leverage File Sync rules for large package delivery in the future since File Sync files live outside of the DB and directly in the file system of the host server. 

  • 0
  • 0
christopheBERNARD | posted this 07 March 2019

Hello matt,

thanks for the return ..i had some doubt ..about the file size !

 

thanks for the time your spend here …

 

  • 0
  • 0
James Beeching | posted this 11 March 2019

Hi Christophe,

I usually send files in the 100s of MB in size to the device via FileSync Rule.

From previous discussions with SOTI Support, it is my understanding that when a package is sent to the device, the whole package has to be received for it do an action. Let me explain further. If a package of is sent to the device and for whatever reason the connection is severed at 50% of package transfer, the package will start transferring again at 0% when the device reconnects. You can imagine this may cause increased data usage over Mobile Data. I was advised to use FileSync for this reason as it will continuing transferring from whatever point the connection was lost.

This may have changed since the issue I had a couple of years ago, but may be worth investigating.

James

  • 1
  • 0
christopheBERNARD | posted this 11 March 2019

Hello all,

@james -> thanks a lot for having sharing your experience.

 

 

  • 1
  • 0
TJ Bukoski | posted this 11 March 2019

Hi James,

The issue to mentioned was an old bug with Package Deployment. It should have been fixed. Expected behaviour is that the Deployment Server should divide up the Package into blocks in the cache and send them to the device. The Server should also keep track of which blocks went to each device if the transmission was interrupted.

If this still is not the case please file a ticket with Support.

  • 1
  • 0
James Beeching | posted this 11 March 2019

Hi TJ, 

I will look into this. I fear my knowledge may be out-of-date on this!

James

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback