GPRS APN Removal


Audience

I have a customer that has provisioned MC65's with an APN from AT&T via MSP 3.3.1. They have now received a custom APN and would like to provision it to the devices; but we are finding out that MSP does not support removing the old APN even though there is an option for "Remove Existing Connection?" I need assistance for a clean solution for removing the old APN that was provisioned via MSP. Has anyone ran into this scenario?

Submitted by USER02034 on May 04, 2019 Permalink

First, never mess with the registry when dealing with Connection Manager stuff!!! What I meant is a two step procedure: 1) Use the application with an XML file which contains what Thomas suggested to remove the existing APN, i.e:    2) Use it again to create the right APN profile on another XML file. Maybe this could work on one single step, including both things on the same XML... Try it :)

Submitted by HPT864 on May 04, 2019 Permalink

Would using the xml to remove the APN profile work if the profile isn't even on the device?  The actual APN profile is not there, but in the connections list you can see its connected to both APN's. What we're trying to figure out is why the device is still connecting to the old APN when the actual APN profile has been removed.

Submitted by DHW736 on May 04, 2019 Permalink

John; How did you remove the APN such that it is "not there" but still connected to it?  Did you do it manually from Settings->Connections, using XML or what?  Also, does it make a difference if you remove it when it is or is not connected?  If removing the APN profile is not fully removing it, then it sounds like an issue you should raise with someone on the device team, not the MSP team.  Most likely if MSP eventually supports removing APN profiles, it will have the same issues you are experiencing with APN removal, and there will likely be nothing we can do about it.

Allan

Submitted by HPT864 on May 04, 2019 Permalink

The customer removed it, and I'm not sure which method worked but I know that he did try deleting the setting and than manually deleting registry keys.  Yes the profile was not there, but device still showed connected to it.  I'm not sure what the final outcome was as Tim Broadway worked directly with the customer. Tim did you submit a GRIP for this?  What was the final outcome?

Submitted by Anonymous (not verified) on May 04, 2019 Permalink

You could also package the XML into a CAB/cpf file and use wceload.exe to install the cab and remove the APN - MSP should be able to do this.

Submitted by USER02034 on May 04, 2019 Permalink

I once wrote an application you might find useful (pls find attached, as well as an example). It "installs" (or provisions) XML files. Its usage is: XMLInstall [-d] Optional -d deletes XML file after successful installing You could create a package with it and the right XML file, with "Install command line" = XMLInstall [-d] And this will (in principle) do.

Submitted by HPT864 on May 04, 2019 Permalink

Is this for Tim Lombardo at Saia Motor Freight?  I'm working with him and ECRT on this issue right now.  There is an option for "Remove Existing Connection" but as you can see in the setting and in the Help documentation it's stated that is not currently supported.  We don't yet know the reasoning as the developer that wrote this is out for two weeks. As I let Tim know, it appears the only way around this is to do a clean boot on the devices.

Submitted by Anonymous (not verified) on May 04, 2019 Permalink

You could use an xml prov file that will remove the GPRS entry from the connection manager first. Than you could send down your new WWAN settings object.    But this works only if your devices running at least MSP Client Software 7.03.38 and higher.

Hope this helps Thomas