O2 Mobile Connection Manager Download
HALEY SCHANDELMIER
The Network Connection Manager (NetworkConnectionMgr) allows an administrator to set preferences for device connection to cellular (WWAN) and Wi-Fi (WLAN) networks to help ensure that devices use the optimal network at all times. NetworkConnectionMgr allows administrators to manage and deploy lists of access points for wireless networks, rank them in order of priority, and/or set minimum signal levels when establishing connections with a set time interval for attempting to improve connections.
Used to select an Action to perform for managing the list of cellular (WWAN) and/or Wi-Fi (WLAN) network names on the device. Cellular networks are identified by their operator name, plus their associated mobile country code (MCC) and mobile network code (MNC). Wi-Fi networks are identified by their SSID.
Used to enter the name of a .txt file containing a prioritized list of cellular (WWAN) and/or Wi-Fi (WLAN) networks. The first name on the list is given the highest priority for connection; each subsequent name gets a lesser priority.
Used to enter the minimum signal level (in dBm) for connection to a Wi-Fi (WLAN) network. Values range from -90 dBm (poor) to -30 dBm (excellent). A value of "0" (default) is ignored, causing no change to any current value.
Used to enter the minimum signal level (in dBm) for connection to a cellular (WWAN) network. Values range from -156 dBm (poor) to -31 dBm (excellent). A value of "0" (default) is ignored, causing no change to any current value.
Used to enter a time interval (in seconds) to wait before comparing the quality of the current connection against those from the list of cellular and Wi-Fi access points stored on the device. A value of "0" (default) is ignored, causing no change to any current value.
This topic is intended for Microsoft's mobile operator (MO) partners who can configure how Windows connects to their networks. If you are a customer who is experiencing Windows network connection issues, see Fix network connection issues in Windows.
Automatic connection management, introduced in Windows 8, makes connection decisions by looking at Ethernet, Wi-Fi, and mobile broadband interfaces. These decisions lead to automatic connect and disconnect actions on Wi-Fi and mobile broadband interfaces.
Windows 8, Windows 8.1, and Windows 10 include a number of policies to control connection management. These policies are not exposed in the Windows user interface but can be configured by using the WcmSetProperty API or Group Policy.
If this policy is enabled, Windows attempts to maintain the smallest number of concurrent connections that offer the best available level of connectivity. Windows maintains connectivity to the following networks:
This policy setting determines if a computer can have multiple connections to the Internet, to a Windows domain, or to both. If multiple connections are allowed, the policy then determines how network traffic is routed.
If this policy is set to 0, a computer can have simultaneous connections to the Internet, to a Windows domain, or to both. Internet traffic can be routed over any connection, including a cellular connection or any metered network. This was previously the Disabled state for this policy setting in builds of Windows before Windows 10, version 1809, build 17663.404. This option was first available in Windows 8.
If this policy is set to 1, any new automatic Internet connection is blocked when the computer has at least one active Internet connection to a preferred type of network. The order of preference is as follows:
If this policy setting is set to 2, the behavior is similar to when it is set to 1. However, if a cellular data connection is available, that connection will always stay connected for services that require a cellular connection. When the user is connected to a WLAN or Ethernet connection, no Internet traffic is routed over the cellular connection. This option was first available in Windows 10, version 1703.
If this policy setting is set to 3, the behavior is similar to when it is set to 2. However, if there is an Ethernet connection, Windows does not permit users to connect to a WLAN manually. A WLAN can only be connected (automatically or manually) when there is no Ethernet connection.
When Windows decides that a network should no longer be connected, it does not immediately disconnect. Abrupt disconnections degrade the user experience without providing an appreciable benefit and are avoided when possible.
When the traffic drops below this threshold, the interface will be disconnected. Applications that keep long-lived idle connections, such as an e-mail client, may be interrupted and should re-establish their connections over a different interface.
Because Windows 8, Windows 8.1, and Windows 10 cannot automatically connect Ethernet cables to or disconnect them from a PC, they can only enforce the policy by allowing or prohibiting wireless connections. When a PC has an Ethernet connection to the domain network, wireless networks that do not connect to the domain cannot be connected, and vice versa. Attempts to do so will result in the following error:
Because prohibiting interconnections is a security consideration, any disconnections that comply with this policy take effect immediately, even if there is ongoing activity. Users will experience a connectivity disruption when transitioning between public and corporate networks, even if the two networks overlap.
For example, a user engaged in a VoIP call over a mobile broadband network with a laptop docked to a corporate Ethernet connection will lose the call, although the app may be able to automatically recover over the new connection. If the policy was not enabled, Windows would instead soft-disconnect the mobile broadband connection by waiting for the call to complete. On the other hand, a VoIP call started over a corporate Wi-Fi network will not be disrupted when docked to the corporate network because both networks connect to the domain. The Wi-Fi network is disconnected after the call is completed.
This policy prevents Windows from connecting to mobile broadband networks that are in a roaming state. By default, this policy is disabled, and the user may choose to manually connect to a mobile broadband network while roaming or to enable automatically connecting to such a network. When this policy is enabled, the user cannot choose a roaming mobile broadband network from Connection Manager.
When considering which multiple connections to maintain, Windows uses a number of traits to determine the preferred networks. This is used only when determining whether to maintain a connection to a given interface, not for routing. If a connected interface is not in the process of being soft-disconnected, routing is determined by the metric in the routing table. If the route metric is not specified manually, Windows will automatically assign a route metric based on the link speed of the adapter.
Even though the link speed influences routing behavior among currently connected interfaces, Windows does not make connectivity decisions based on the link speed or throughput of a network. It is not possible to configure Windows to change its connection preference between a mobile broadband network and a Wi-Fi network based on the current speed of the mobile broadband network. If both are connected, the user or a desktop app can change route metrics to influence routing preferences.
For Windows 8 and Windows 8.1, if Windows detects that the currently connected Wi-Fi network has very low signal strength, it may choose to connect a mobile broadband network (if permitted by policy) to avoid disrupting network connectivity. This helps to smooth the transition when a user is moving away from a wireless access point.
Windows does not disconnect a more preferred Wi-Fi network until the signal strength cannot maintain the connection. If signal strength improves, Windows may soft-disconnect the mobile broadband adapter.
In most situations, the preferred network list determines which wireless network profiles Windows will use to connect. Prior to Windows 8, this list applied to Wi-Fi networks only. In Windows 8, Windows 8.1, and Windows 10, it can also include mobile broadband networks.
Windows 8, Windows 8.1, and Windows 10 automatically update the preferred network list based on user actions. Any manual connection or disconnection will update the network list so that the same behavior will occur automatically in the future.
Mobile broadband and Wi-Fi hotspot operators provide Windows with a series of mobile broadband and Wi-Fi profiles by using the ProvisioningAgent or msProvisionNetworks APIs.
When initially provisioned, the operator-created profiles are added to the top (Wi-Fi only) or bottom (if mobile broadband is included) of the existing network list. You cannot influence the position of the networks the user provisions in the network list. However, you can define the relative order of their networks in the network list.
Prior to Windows 8, the Wi-Fi preferred network list was accessible to the user through the Manage Wireless Networks control panel. Telemetry indicates that very few users ever accessed this functionality. Additionally, this user interface was tied to Wi-Fi only and could not incorporate preferences between Wi-Fi and mobile broadband.
To modify the order of the network list, use the WcmSetProfileList function. We do not recommend using the WlanSetProfileList function, as it may disturb the position of mobile broadband profiles in the network list in unintended ways.
The order of the Wi-Fi profiles in the network list may be modified using the netsh wlan set profileorder command. However, this is not recommended and can disturb the position of mobile broadband profiles in the list in unintended ways.
Windows supports combinations of the GSM-based and CDMA-based mobile broadband technologies including LTE. The minimum connectivity capability for a Mobile Broadband device is 3G connectivity. 2G connectivity is optional. Devices for the various broadband technologies must follow the specifications of standards bodies and be certified by the preferred mobile operator.
35fe9a5643