SOTI Pulse Logo

Automating .pcg

P
PCallaw
Versatrans School Transportation Software - Tyler Technologies

Good morning everyone!

I know this question has been asked over the years, but I thought I would revive the topic. I am currently working on automating the process of building and deploying .pcg files to our server. I am currently on MobiControl 15.4 and all of the devices are Samsung Tab active 2's and 3s. OS versions running from 9 up to OS version 13. I have automated certain parts of the process, i.e leveraging the API to post profiles and packages to the server and setting up pipeline for deployment. The issue I am running into is the actual building of the .pcg. I have researched this form through and through, I have tried using the PkgUtil command line tool. That works fine, however, I need to be able to set certain parameters while building the .pcg file. For example, I need to set the location of where the file is saved and to set the option of 'Do not uninstall the file'. Has anyone had any luck with such a process? I have 10 of thousands of devices to make profiles and packages for. I am looking to automate this process as much as possible. Any and all information and help is greatly appreciated.

mobicontrol android automation
a year ago
SOTI MobiControl
ANSWERS
RC
Raymond Chan Diamond Contributor
a year ago

Most of the options included for a .pcg package generated with PkgUtil command line tool are stored in .mcp file corresponding to the .pcg package.  This is an ASCII file that can be edited and then reused to run PkgUtil in batch mode using command line argument

     PkgUtil -b <mcp_file>

There are field such as  "File1Path=" in the "Files" section to specify the destination on device file system for corresponding file defined by the field "File1Src".

P
PCallaw
a year ago

Raymond,

Thank you for your response. Is there any formal documentation that you know of that has all this information? The README.txt file that came with the CMD tool only contains basic information such as using the switches -b and -e. When I ran the CMD file to create a package, a '.mdp' file does not seem to generate. Any more information would be greatly appreciated. Thank you!

P
PCallaw
a year ago

Update:

Figured out that .mdp was supposed to be .mcp file. I have found those and have begun digging thought them. I see certain flags and parameters in there. My only question now is the numeric values assigned to those flags when created. Again Raymond, thank you for pointing out the filepath parameter. I have figured out how to set that. The only thing I need to make sure is set when creating the .pcg now is that the 'do not uninstall file' box is ticked.

A
ABMOD@SOTI
a year ago

Hi PCallaw,

 

Thanks for posting on SOTI Pulse. Thanks, Raymond for responding to the post, your expertise and willingness to help are greatly appreciated!

Has your query been resolved? If not, or if you have any additional concerns, please don't hesitate to reach out. We are dedicated to providing assistance and support.

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

 

Kind Regards,

P
PCallaw
a year ago

ABMOD,

Thank you for reaching out. I am still working on trying to set parameters in the .mcp file and building the packages on the command line. Is there any official documentation on this subject? Webinars? GitHub repositories? Any and all information would be helpful. I have been able to write PowerShell scripts for creating profiles and POSTing packages that are already made in Package Studio. The API works great for that! However, The actual building of the .pcg package in Package Studio is making it troublesome to fully automate the process. Thank you again for reaching out and thank you Raymond for all the adivice and information you have provided in this community.

A
ABMOD@SOTI
a year ago

Hi PCallaw,

 

Apologies from our side, for this particular issue we need to investigate further.

We request you to please raise a support case at log a case so that our agent can work on your query as quickly as possible.

Similar Discussions