MDM_WiFiProfile01_01 class
[Some information relates to pre-released product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.]
The MDM_WiFi_Profile01_01 class represents a Wi-Fi configuration profile. This profile enables the device to connect to the Wi-Fi network when it is in range.
The following syntax is simplified from Managed Object Format (MOF) code and includes all of the inherited properties.
Syntax
[dynamic, provider("DMWmiBridgeProv"), AMENDMENT]
class MDM_WiFiProfile01_01
{
string InstanceID;
string ParentID;
string WlanXml;
string Proxy;
};
Members
The MDM_WiFi_Profile01_01 class has these types of members:
- Properties
Properties
The MDM_WiFi_Profile01_01 class has these properties.
InstanceID
Data type: string
Access type: Read-only
Qualifiers: key
Identifies the name of the parent node. For this class, the string is the SSID of the Wi-Fi network.
ParentID
Data type: string
Access type: Read-only
Qualifiers: key
Describes the full path to the parent node. For this class, the string is "./Vendor/MSFT/Wi-Fi/Profile"
Proxy
Data type: string
Access type: Read-only
Specifies the configuration of the network proxy. A proxy server host and port can be specified per connection for Windows 10 Mobile Insider Preview. This proxy configuration is only supported in Windows 10 Mobile Insider Preview. Using this configuration in Windows 10 Insider Preview will result in failure.
The format is host:port, where host can be one of the following:
- A registered host name, such as server name, FQDN, or Single Label Name, such as myweb instead of myweb.contoso.com.
- IPV4 address
- IPv6/IPvFuture address.
If the format is an IPvFuture address, then it must be specified as an IP literal as "[" (IP v6 address / IPvFuture ) "]", such as "[2441:4880:28:3:204:76ff:f43f:6eb]:8080".
WlanXml
Data type: string
Access type: Read-only
The XML that describes the network configuration and follows the WLAN_profile Schema on MSDN.
The profile XML must be escaped, as shown in the examples below.
If it exists in the blob, the keyType and protected elements must come before keyMaterial, as shown in the example in WPA2-Personal Profile Sample.
Requirements
Minimum supported client |
Windows 10 Insider Preview [desktop apps only] |
Minimum supported server |
None supported |
Namespace |
Root\CIMv2\MDM\DMMap |
MOF |
DMWmiBridgeProv.mof |
DLL |
DMWmiBridgeProv.dll |