Did you use Package studio to create your .pcg package? Or used the automatic  pcg generation introduced in MobiControl v15.x?

To Raymond's point, there is an option within the Package builder to configure an APK contained within the package to not uninstall upon un-assignment. This could help you solve your specific problem, however I tend to avoid leveraging that particular configuration and to instead get used to the default behavior that SOTI has for Profile Assignment. There is a lot of power in the Assignment principal and the fact that SOTI will automatically remove or undo an operation that was performed when a device is moved from one group to another and the assignments change.

Selecting the parameter to leave an APK installed is a relatively hidden configuration that changes that default behavior. I don't think there would be any visual indicator of any kind that the particular package was designed in that way, and there is no evidence left behind that a package was once installed, but the contents were left behind. Therefore, you wouldn't have any console based visibility to which devices have had Surf installed, other than manually keeping track of them yourself through the various folder moves.

If Surf is being uninstalled right now because a device is moving between groups or assignments and you instead want it to remain installed then it sounds like you should instead readjust your Profiles and assignments so that does not happen. If you gave us more detail about your group and Profile assignment structure we could probably point you in the right direction. 

I downloaded soti surf to my drive then uploaded to the soti server.

Surf_15.2.1.6.apk

I guess the bad thing about going this route is:

If I accidently delete the package then it uninstalls on all my devices, yikes

or If I move a device to another group that has a profile without this package

it will also remove the package

the package shows up as: net.soti.surf

so since I didn't use package builder I don't have this option, maybe I should just build a package with my downloaded file and do it that way if I want this option to not remove if the device is moved to another group.

along with power comes with making a mistake, say I forgot and deleted the package, then it uninstalls from all my devices that that had it installed resulted in a lot of help desk calls, I'm just trying to put in a safe method where the package stays installed regardless, I can always create a package to uninstall the application if needed

I just created the package from the downloaded file for practice and saw this option:

"do not uninstall the file when profile is deleted"

Is this what you were referring to

thanks

Yes.

one more quick question

how about if the "package is deleted" will it uninstall on the devices that has it installed

thanks

having thought about what you said I do see some advantages in leaving set as default behavior

for example say I want the browser upgraded on these devices, I could move them to a profle

that doesn't have that package applied and it would remove, then I could move to profile that

has the newer version and it would install that

You could just have a profile containing the surf package only. Assign it to the folders that require surf to always be installed. 

If (like me), you require different Surf settings applied to different folders, then just create surf settings profiles and assign accordingly.

are you saying I can apply more than one profile to a group?

I'm thinking maybe I do this:

We have some mc9300 devices which all come with android and will need soti surf

so my group is called mc9300 which I assign the soti install profile

my subgroups might be by department and will have another profile for other settings

when ever anyone moves a device between profiles it will not remove surf

Each device group can have multiple profiles, and each such profile may have different, hopefully non-conflcting, configuration payload(s)/package(s) included.

How policies/packages shoud be broken down in one or more profiles depends very much on how the device group hiearchy is architected ,and also on the management use cases and business work-flow.

If  you have the same  .pcg package deployed with profile to both the source and destination device-groups of a device to be moved, then the package should not get uninstalled and then subsequently re-installed after the move.