Testing your desktop COSA/APN database submission
Before submitting an APN update request to Microsoft, it is important for the MNO or MVNO to validate the APN entries that they are about to submit. Microsoft does not have access to your network, so it is your responsibility to ensure the values that are being submitted are valid and work correctly.
Contact your Microsoft TAM
The first step in testing and submitting your APN update is to work with your TAM to open a MS Solve case with Microsoft Customer Services and Support. This case is for tracking purposes. After a MS Solve case is opened, provide the following information to the support engineer:
- A completed spreadsheet that contains your APN information.
If you do not have a TAM:
- Contact Microsoft Customer Services and Support by calling (800) MICROSOFT (642-7676).
- Inform the customer service representative that a COSA/APN database update is needed.
- Provide the spreadsheet to the support engineer.
- If asked, specify Windows 8 or Windows 10 as the product, as appropriate.
You will need to provide a credit card to open the incident, but you will not be charged.
Test your submission for desktop COSA
Use this process for Windows 10, version 1703 and later.
After you have submitted your completed spreadsheet that contains your APN information to your TAM, Microsoft will create a provisioning package (.ppkg) file for you and return it to you so you can install and test your APN.
For more information about how to install a provisioning package file, see Apply a provisioning package.
Modify the local COSA database (desktop COSA)
Follow these steps to test the updated COSA Provisioning Package (PPKG) you received from Microsoft after completing your APN information spreadsheet and submitting it to your TAM.
These steps require a script from Microsoft to apply and test the PPKG file. Use the following link to download the latest version of the script: https://go.microsoft.com/fwlink/p/?linkid=866771.
Apply the test PPKG file
Create a backup of the original provisioning package before performing the following actions. The original provisioning package is located here:
- Remove any SIM from the device, if any.
- Copy the script and the new PPKG file to a local directory.
- Open an elevated Command Prompt window and change to the directory containing the script.
- Run the script with this syntax to apply the PPKG:
ApplyCosaProvisioning.BAT -a <full path to the PPKG local directory>.
- For example:
ApplyCosaProvisioning.BAT -a "C:\FromMicrosoft\Microsoft.Windows.Cosa.Desktop.Client.ppkg"
- For example:
- Insert the SIM and await provisioning.
Restore the original PPKG file
Once validation of the new PPKG received from Microsoft has completed, always restore it with the following steps. Restoring back to the original PPKG will ensure that you receive the latest COSA updates via Windows Update.
- Once validated, remove the SIM from the device.
- Run the script with this syntax to restore the original PPKG:
- Insert the SIM for provisioning to take effect, reading the original PPKG.
Collect logs in case of failure
To collect logs in the event of a failure during the testing process, follow these steps:
- Remove any SIM from the device.
- Run the script with this syntax to start netsh logging:
- Insert the SIM and wait for provisioning to fail.
- Follow the tool's prompts to end logging.
- Send the logs to Microsoft in zipped format.
Test your submission for the APN database (apndatabase.xml)
Use this process for Windows 8, Windows 8.1, and versions of Windows 10 before Windows 10, version 1703.
There are two ways that you can ensure that the APN entries work before submitting them to Microsoft:
A simple way to test that an APN can connect to your network is to edit the current profile and insert the APN to test into the profile. To perform this test, follow these steps:
This test does not simulate the full experience, which is described in the Modify the local APN database section.
Insert a SIM into the PC that works with the APN value you want to test.
Turn on the PC, log on to Windows, and open Windows Connection Manager. The mobile broadband connection should appear.
Right-click the mobile broadband connection, and then select View connection properties.
Enter the APN value to test into this dialog box.
Save your changes, and then try to connect to the mobile broadband network.
Before you submit an APN update, you should editing the local APN database or creating a new one for testing. By doing this, you closely simulate the full experience because the APN selection logic that Windows Connection Manager uses is fully tested.
Modify the local APN connectivity database
Copy any existing values from the local APN database file -- View the existing entries in the local APN database on your PC and copy these entries into a new XML file. If you don’t have any APN entries in the local copy of the APN database, skip this step and start with a blank XML file.
Modify values in the XML file according to the published APN schema – Ensure that your APN entries follow the APN database schema reference.
Generate your hardware IDs – Hardware IDs specify one or more hardware identification strings that match the SIM characteristics to an APN entry in the database. Each string is specified by a HardwareId element. We recommend that you use mbidgenerator.exe to generate your hardware IDs. For more information, see Using mbidgenerator.exe to generate hardware IDs.
Validate that the file you generated conforms to the published APN database schema -- Always perform a schema check to ensure that the file you have generated conforms to the APN database schema reference.
Overwrite the APN connectivity database on the PC with your new database
From an elevated command prompt, type cd %systemroot%\system32 and then press ENTER.
Type takeown /f .\ApnDatabase.xml and then press ENTER.
Type icacls .\ApnDatabase.xml /grant %username%:F and then press ENTER.
Copy your customized version of the ApnDatabase.xml file to the directory.
Validate that the APN entries exist in the local APN database:
Ensure that there are no existing mobile broadband profiles by running the following command: netsh mb show profiles
If a mobile broadband profile exists, type netsh mb profile interface=<Interface name> name=<Profile name>
Ensure that the device doesn’t have a provisioned context by running the following command: netsh mb show provisionedcontext interface=<Interface name>
Note If the device provides a provisioned context, Windows will use the APN from that provisioned context instead of the local APN database and you will not able to test your APNs. If the device has a provisioned context, you need to acquire another device that doesn’t provide a provisioned context.
Open Windows Connection Manager. It will show the Wi-Fi and mobile broadband networks that are within range.
Select the Mobile Network, and then click Connect.
If you have multiple APNs that match the SIM properties, Windows Connection Manager will try each of the matching APNs until a successful connection takes place. If none of the APNs connect, Windows Connection Manager will either show an error or show a custom APN entry screen, allowing the user to enter a custom APN.
Note The auto-connect order that you specify in the APN database is used to determine the order in which APNs are tried.
If you have only one APN in the APN database, Windows will automatically connect to the operator network.
You can see which APN was applied to the connection profile by opening Windows Connection Manager, right-clicking the Mobile Broadband entry for your network, and then clicking Properties.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.