mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Updated
This commit is contained in:
nimishasatapathy
parent
1aa7b73b72
commit
b204eb1ecf
@ -262,25 +262,6 @@ Data type is string.
|
|||||||
|
|
||||||
Supported operations are Get, Add, Delete, and Replace.
|
Supported operations are Get, Add, Delete, and Replace.
|
||||||
|
|
||||||
## <a href="" id="productname"></a>Find publisher and product name of apps
|
|
||||||
|
|
||||||
|
|
||||||
You can pair a Windows Phone (Windows 10 Mobile, version 1511) to your desktop using the Device Portal on the phone to get the various types of information, including publisher name and product name of apps installed on the phone. This procedure describes pairing your phone to your desktop using WiFi.
|
|
||||||
|
|
||||||
If this procedure does not work for you, try the other methods for pairing described in [Device Portal for Mobile](/windows/uwp/debug-test-perf/device-portal-mobile).
|
|
||||||
|
|
||||||
**To find Publisher and PackageFullName for apps installed on Windows 10 Mobile**
|
|
||||||
|
|
||||||
1. On your Windows Phone, go to **Settings**. Choose **Update & security**. Then choose **For developers**.
|
|
||||||
2. Choose **Developer mode**.
|
|
||||||
3. Turn on **Device discovery**.
|
|
||||||
4. Turn on **Device Portal** and keep **AuthenticationOn**.
|
|
||||||
5. Under the **Device Portal**, under **Connect using: WiFi**, copy the URL to your desktop browser to connect using WiFi.
|
|
||||||
|
|
||||||
If you get a certificate error, continue to the web page.
|
|
||||||
|
|
||||||
If you get an error about not reaching the web page, then you should try the other methods for pairing described in [Device Portal for Mobile](/windows/uwp/debug-test-perf/device-portal-mobile).
|
|
||||||
|
|
||||||
6. On your phone under **Device discovery**, tap **Pair**. You will get a code (case sensitive).
|
6. On your phone under **Device discovery**, tap **Pair**. You will get a code (case sensitive).
|
||||||
7. On the browser on the **Set up access page**, enter the code (case sensitive) into the text box and click **Submit**.
|
7. On the browser on the **Set up access page**, enter the code (case sensitive) into the text box and click **Submit**.
|
||||||
|
|
||||||
|
|||||||
@ -64,7 +64,6 @@ Allows the administrator to require storage card encryption on the device. This
|
|||||||
<th>Enterprise</th>
|
<th>Enterprise</th>
|
||||||
<th>Education</th>
|
<th>Education</th>
|
||||||
<th>Mobile</th>
|
<th>Mobile</th>
|
||||||
<th>Mobile Enterprise</th>
|
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||||
@ -122,7 +121,6 @@ Allows the administrator to require encryption to be turned on by using BitLocke
|
|||||||
<th>Enterprise</th>
|
<th>Enterprise</th>
|
||||||
<th>Education</th>
|
<th>Education</th>
|
||||||
<th>Mobile</th>
|
<th>Mobile</th>
|
||||||
<th>Mobile Enterprise</th>
|
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||||
@ -189,7 +187,6 @@ Allows you to set the default encryption method for each of the different drive
|
|||||||
<th>Enterprise</th>
|
<th>Enterprise</th>
|
||||||
<th>Education</th>
|
<th>Education</th>
|
||||||
<th>Mobile</th>
|
<th>Mobile</th>
|
||||||
<th>Mobile Enterprise</th>
|
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
<td><img src="images/crossmark.png" alt="cross mark" /></td>
|
||||||
|
|||||||
@ -61,7 +61,6 @@ Cache-Control: no-cache
|
|||||||
<OSEdition>101</OSEdition> <!--New in Windows 10-->
|
<OSEdition>101</OSEdition> <!--New in Windows 10-->
|
||||||
<OSVersion>10.0.0.0</OSVersion> <!--New in Windows 10-->
|
<OSVersion>10.0.0.0</OSVersion> <!--New in Windows 10-->
|
||||||
<RequestVersion>3.0</RequestVersion> <!--Updated in Windows 10-->
|
<RequestVersion>3.0</RequestVersion> <!--Updated in Windows 10-->
|
||||||
<DeviceType>WindowsPhone</DeviceType> <!--Legacy in Windows 10 for Windows Phone/Handheld-->
|
|
||||||
<ApplicationVersion>10.0.0.0</ApplicationVersion>
|
<ApplicationVersion>10.0.0.0</ApplicationVersion>
|
||||||
<AuthPolicies>Certificate</AuthPolicies> <!--New in Windows 10-->
|
<AuthPolicies>Certificate</AuthPolicies> <!--New in Windows 10-->
|
||||||
</request>
|
</request>
|
||||||
@ -353,12 +352,8 @@ http://schemas.microsoft.com/5.0.0.0/ConfigurationManager/Enrollment/DeviceEnrol
|
|||||||
<ac:Value>49015420323756</ac:Value>
|
<ac:Value>49015420323756</ac:Value>
|
||||||
<ac:ContextItem Name="EnrollmentType"> <!--New in Windows 10-->
|
<ac:ContextItem Name="EnrollmentType"> <!--New in Windows 10-->
|
||||||
<ac:Value>Full</ac:Value>
|
<ac:Value>Full</ac:Value>
|
||||||
<ac:ContextItem Name="DeviceType"> <!—From Windows Phone 8.1-->
|
</ac:ContextItem>
|
||||||
<ac:Value>WindowsPhone</ac:Value>
|
</ac:ContextItem>
|
||||||
</ac:ContextItem>
|
|
||||||
<ac:ContextItem Name="ApplicationVersion"> <!—From Windows Phone 8.1-->
|
|
||||||
<ac:Value>10.0.0.0</ac:Value>
|
|
||||||
</ac:ContextItem>
|
|
||||||
<ac:ContextItem Name="DeviceID"> <!--From Handheld 8.1 -->
|
<ac:ContextItem Name="DeviceID"> <!--From Handheld 8.1 -->
|
||||||
<ac:Value>7BA748C8-703E-4DF2-A74A-92984117346A</ac:Value>
|
<ac:Value>7BA748C8-703E-4DF2-A74A-92984117346A</ac:Value>
|
||||||
<ac:ContextItem Name="EnrollmentData">
|
<ac:ContextItem Name="EnrollmentData">
|
||||||
|
|||||||
@ -189,28 +189,7 @@ The XML below is the current version for this CSP.
|
|||||||
<MIME>text/plain</MIME>
|
<MIME>text/plain</MIME>
|
||||||
</DFType>
|
</DFType>
|
||||||
</DFProperties>
|
</DFProperties>
|
||||||
</Node>
|
</Node>
|
||||||
<Node>
|
|
||||||
<NodeName>SwV</NodeName>
|
|
||||||
<DFProperties>
|
|
||||||
<AccessType>
|
|
||||||
<Get />
|
|
||||||
</AccessType>
|
|
||||||
<Description>Returns the Windows Phone OS software version.</Description>
|
|
||||||
<DFFormat>
|
|
||||||
<chr />
|
|
||||||
</DFFormat>
|
|
||||||
<Occurrence>
|
|
||||||
<One />
|
|
||||||
</Occurrence>
|
|
||||||
<Scope>
|
|
||||||
<Permanent />
|
|
||||||
</Scope>
|
|
||||||
<DFType>
|
|
||||||
<MIME>text/plain</MIME>
|
|
||||||
</DFType>
|
|
||||||
</DFProperties>
|
|
||||||
</Node>
|
|
||||||
<Node>
|
<Node>
|
||||||
<NodeName>HwV</NodeName>
|
<NodeName>HwV</NodeName>
|
||||||
<DFProperties>
|
<DFProperties>
|
||||||
|
|||||||
@ -474,7 +474,7 @@ In Azure AD joined Windows 10 PC, provisioning /.User resources fails when the
|
|||||||
|
|
||||||
### Requirements to note for VPN certificates also used for Kerberos Authentication
|
### Requirements to note for VPN certificates also used for Kerberos Authentication
|
||||||
|
|
||||||
If you want to use the certificate used for VPN authentication also for Kerberos authentication (required if you need access to on-premises resources using NTLM or Kerberos), the user's certificate must meet the requirements for smart card certificate, the Subject field should contain the DNS domain name in the DN or the SAN should contain a fully qualified UPN so that the DC can be located from the DNS registrations. If certificates that do not meet these requirements are used for VPN, users may fail to access resources that require Kerberos authentication. This issue primarily impacts Windows Phone.
|
If you want to use the certificate used for VPN authentication also for Kerberos authentication (required if you need access to on-premises resources using NTLM or Kerberos), the user's certificate must meet the requirements for smart card certificate, the Subject field should contain the DNS domain name in the DN or the SAN should contain a fully qualified UPN so that the DC can be located from the DNS registrations. If certificates that do not meet these requirements are used for VPN, users may fail to access resources that require Kerberos authentication.
|
||||||
|
|
||||||
### Device management agent for the push-button reset is not working
|
### Device management agent for the push-button reset is not working
|
||||||
|
|
||||||
|
|||||||
@ -216,29 +216,6 @@ The XML below is the DDF for the current version for this CSP.
|
|||||||
</DFType>
|
</DFType>
|
||||||
</DFProperties>
|
</DFProperties>
|
||||||
</Node>
|
</Node>
|
||||||
<Node>
|
|
||||||
<NodeName>HighAccPositioningMethod</NodeName>
|
|
||||||
<DFProperties>
|
|
||||||
<AccessType>
|
|
||||||
<Get />
|
|
||||||
<Replace />
|
|
||||||
</AccessType>
|
|
||||||
<DefaultValue>0</DefaultValue>
|
|
||||||
<Description>Optional. Specifies the positioning method that the SUPL client will use for mobile originated position requests. The default is 0. The default method in Windows Phones provides high-quality assisted GNSS positioning for mobile originated position requests without loading the mobile operator's network or location services. For OMA DM, if the format for this node is incorrect the entry will be ignored and an error will be returned, but the configuration service provider will continue processing the rest of the parameters.</Description>
|
|
||||||
<DFFormat>
|
|
||||||
<int />
|
|
||||||
</DFFormat>
|
|
||||||
<Occurrence>
|
|
||||||
<One />
|
|
||||||
</Occurrence>
|
|
||||||
<Scope>
|
|
||||||
<Permanent />
|
|
||||||
</Scope>
|
|
||||||
<DFType>
|
|
||||||
<MIME>text/plain</MIME>
|
|
||||||
</DFType>
|
|
||||||
</DFProperties>
|
|
||||||
</Node>
|
|
||||||
<Node>
|
<Node>
|
||||||
<NodeName>LocMasterSwitchDependencyNII</NodeName>
|
<NodeName>LocMasterSwitchDependencyNII</NodeName>
|
||||||
<DFProperties>
|
<DFProperties>
|
||||||
@ -308,26 +285,6 @@ The XML below is the DDF for the current version for this CSP.
|
|||||||
</DFType>
|
</DFType>
|
||||||
</DFProperties>
|
</DFProperties>
|
||||||
</Node>
|
</Node>
|
||||||
<Node>
|
|
||||||
<NodeName>RootCertificate</NodeName>
|
|
||||||
<DFProperties>
|
|
||||||
<AccessType>
|
|
||||||
<Get />
|
|
||||||
</AccessType>
|
|
||||||
<Description>Required. Specifies the root certificate for the H-SLP server. Windows Phone does not support a non-secure mode. If this node is not included, the configuration service provider will fail but may not return a specific error.</Description>
|
|
||||||
<DFFormat>
|
|
||||||
<node />
|
|
||||||
</DFFormat>
|
|
||||||
<Occurrence>
|
|
||||||
<One />
|
|
||||||
</Occurrence>
|
|
||||||
<Scope>
|
|
||||||
<Permanent />
|
|
||||||
</Scope>
|
|
||||||
<DFType>
|
|
||||||
<DDFName></DDFName>
|
|
||||||
</DFType>
|
|
||||||
</DFProperties>
|
|
||||||
<Node>
|
<Node>
|
||||||
<NodeName>Name</NodeName>
|
<NodeName>Name</NodeName>
|
||||||
<DFProperties>
|
<DFProperties>
|
||||||
@ -765,29 +722,6 @@ The XML below is the DDF for the current version for this CSP.
|
|||||||
</DFType>
|
</DFType>
|
||||||
</DFProperties>
|
</DFProperties>
|
||||||
</Node>
|
</Node>
|
||||||
<Node>
|
|
||||||
<NodeName>PositioningMethod_MR</NodeName>
|
|
||||||
<DFProperties>
|
|
||||||
<AccessType>
|
|
||||||
<Get />
|
|
||||||
<Replace />
|
|
||||||
</AccessType>
|
|
||||||
<DefaultValue>0</DefaultValue>
|
|
||||||
<Description>Optional. Specifies the positioning method that the SUPL client will use for mobile originated position requests. The default is 0. The default method in Windows Phones provides high-quality assisted GNSS positioning for mobile originated position requests without loading the mobile operator's network or location services. The Mobile Station Assisted and AFLT positioning methods must only be configured for test purposes. For OMA DM, if the format for this node is incorrect the entry will be ignored and an error will be returned, but the configuration service provider will continue processing the rest of the parameters.</Description>
|
|
||||||
<DFFormat>
|
|
||||||
<int />
|
|
||||||
</DFFormat>
|
|
||||||
<Occurrence>
|
|
||||||
<One />
|
|
||||||
</Occurrence>
|
|
||||||
<Scope>
|
|
||||||
<Permanent />
|
|
||||||
</Scope>
|
|
||||||
<DFType>
|
|
||||||
<MIME>text/plain</MIME>
|
|
||||||
</DFType>
|
|
||||||
</DFProperties>
|
|
||||||
</Node>
|
|
||||||
<Node>
|
<Node>
|
||||||
<NodeName>LocMasterSwitchDependencyNII</NodeName>
|
<NodeName>LocMasterSwitchDependencyNII</NodeName>
|
||||||
<DFProperties>
|
<DFProperties>
|
||||||
|
|||||||
@ -67,15 +67,6 @@ Required. Specifies the address of the MMS application server, as a string. The
|
|||||||
<a href="" id="ms"></a>**MS**
|
<a href="" id="ms"></a>**MS**
|
||||||
Optional. The maximum authorized size, in KB, for multimedia content. This parameter takes a numeric value in string format. If the value is not a number, or is less than or equal to 10, it will be ignored and outgoing MMS will not be resized.
|
Optional. The maximum authorized size, in KB, for multimedia content. This parameter takes a numeric value in string format. If the value is not a number, or is less than or equal to 10, it will be ignored and outgoing MMS will not be resized.
|
||||||
|
|
||||||
## Remarks
|
|
||||||
|
|
||||||
|
|
||||||
Windows Phone MMS does not support user–selectable profiles. While multiple MMS profiles can be provisioned and saved simultaneously, only the last received profile is active.
|
|
||||||
|
|
||||||
If provisioning XML is received for a profile with an existing name, the values in that profile will be overwritten with the new values.
|
|
||||||
|
|
||||||
For more information about the parameters used by the w4 APPLICATION configuration service provider and how they are used, see the OMA MMS Conformance Document (OMA-TS-MMS-CONF-V1\_3-20051027-C) available from the [OMA website](https://go.microsoft.com/fwlink/p/?LinkId=526900).
|
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user