We could use some assistance if anyone is doing any of this.

We have mobile laptops that are used out in the field:

They have SCCM client

Netmotion VPN

Chameleon Celluar Connections

Two things:

1) Is there a piece of SCCM 2007 currently that could manage these (we see SCCM Mobile--but that appears as like smart phones, iphones, ipads, etc).  These are toughbooks (panasonic laptops) and they need to utilize several applications) .  We need to manage these differently than laptops with Direct Access. 

2) We do not want these people receiving SCCM pushes or inventory or WSUS (this is done through our WSUS server) pushes while on cellular network.  When they come back from the field and hit our wireless or connect via network, we would like them to receive these types of pushing throughout the night.  Problem:  They set up and configured the laptops to make this cellular Chameleon appear as a fast network and doesn't appear as a device off these laptops.  Several pushes are reg advertisements; although we are moving to mostly task sequences.  Which most of you know a regular advertisement will allow us to stop on a slow network, but the task sequence advertisement does not have those capabilities.  So we are in a dilema.  Again that only took care of pushes and not all the other things SCCM related we do not want to happen.

How do others handle remote toughbooks in the field on cell connections where the techs want them to appear as fast connection, yet stop SCCM packages from delivering on them or anything like inventory being done on them.

Techs are investigating a rule on Netmotion that we might put in place, we have also thought if setting up a boundary on SCCM related to these Netmotion machines being as 10.0.0.x being slow, but we are unsure how to stop everything or write a correct rule to stop anything SCCM related while NOT connected via network or wireless? 

Ideas, thoughts, pieces of SCCM 2007 that we have no invesigated, etc?

Yes, I know this is an old post, but Im trying to clean them up.

Honestly, I would look at CM12 for this. CM12 added a number of features for the exact issue.

This is an old post, but it is effectively addressed in version 10.52 of NetMotion Mobility. Mobility now includes the ability to deploy and retract software as a built in feature of the core application suite.