Torque Pro Android No Mobile Data Upload Log File Only on Wifi

Introduction

This guide helps you understand and troubleshoot Wi-Fi profile issues that yous may encounter when you use Microsoft Intune.

This article is divided into the post-obit sections:

• Overview of Wi-Fi profiles

• Creating Wi-Fi profiles

• Assigning Wi-Fi profiles

• What successful Wi-Fi profiles look like on your device

• Entries in Company Portal logs of successful Wi-Fi profile deployment

• Troubleshooting mutual problems

The examples in this guide apply SCEP document hallmark for these profiles and assume that the Trusted Root and SCEP profiles work correctly on the device. In the examples, the Trusted Root and SCEP profiles are named equally follows.

	Android	iOS	Windows
Trusted Root Contour	AndroidRoot	iOSRoot	WindowsRoot2
SCEP profile	AndroidSCEP	iOSSCEP	WindowsSCEP2

Overview of Wi-Fi profiles

Wi-Fi is a wireless network that's used by many mobile devices to get network access. Microsoft Intune includes born Wi-Fi settings that can exist deployed to users and devices in your organisation. This group of settings is called a profile. It can be assigned to unlike users and groups. After the profile is assigned, your users get access your organization's Wi-Fi network without configuring it themselves.

For example, you install a new Wi-Fi network that is named Contoso Wi-Fi. And then, yous want to gear up all iOS devices to connect to this network. This procedure includes the following steps:

1. You create a Wi-Fi profile that includes the settings that connect to the Contoso Wi-Fi wireless network.

2. You assign the profile to a group that includes all users of iOS devices.

3. Users find the new Contoso Wi-Fi network in the list of wireless networks on their device. They can then connect to the network by using the authentication method of your pick.

Wi-Fi profiles support the post-obit device platforms and versions:

• Android 4 and later

• Android Enterprise and kiosk

• iOS viii.0 and later

• macOS X 10.11 and newer

• Windows 10 and later, Windows x Mobile, and Windows Holographic for Business

Creating Wi-Fi profiles

To create a Wi-Fi profile, follow the steps in the "Create a device contour" department of the following Microsoft Docs article:

Add together and use Wi-Fi settings on your devices in Microsoft Intune

The Properties screen on the supported platforms resembles the following examples.

Assigning Wi-Fi profiles

After yous create the Wi-Fi profile, assign the profile to selected groups.

See the following Assignments screen examples.

What successful Wi-Fi profiles look similar on your device

The following is an case of Nokia 6.one device. In this example, yous must install the Trusted Root and SCEP profiles before the Wi-Fi profile tin be installed on the device.

1. You receive a notification to install the Trusted Root certificate profile.

   

   

2. You receive a notification to install the SCEP certificate profile.

   

   

   Note If you use a device administrator-managed Android device, in that location may exist multiple certificates. This is because the certificates aren't revoked or removed when a certificate profile is inverse or removed. In this example, select the latest certificate. Unremarkably, this is the last one in the list of certificates.

   This situation doesn't occur on Android Enterprise and Samsung Knox devices. For more information, come across Manage Android piece of work profile devices with Intune and Remove SCEP and PKCS certificates in Microsoft Intune.

3. You receive a notification to install the Wi-Fi profile.

   

4. The Wi-Fi connection is successfully created.

   

After the Wi-Fi profile is installed on the device, you can see it in the Management Profile screen.

After the Wi-Fi profile is installed on the device, go toSettings >Accounts >Access work or school, select your work or school account, and and then selectInfo.

You tin can see WiFiunder the Areas managed by Microsoft.

The Wi-Fi profile is listed underSettings >Network & Internet  > Wi-Fi.

Entries in Company Portal logs of successful Wi-Fi profile deployment

On an Android device, the Omadmlog.log file logs detail activities of the Wi-Fi contour when it's candy on the device. Depending on how long the Company Portal app has been installed, you may have upward to v Omadmlog log files. You can utilize the timestamp of the last sync to help discover the related entries.

The post-obit example uses CMTrace to read the logs and uses "wifimgr" equally the search cord filter.

The following sample log snippet shows a successful processing of the Wi-Fi profile:

2019-08-01T19:22:46.7340000    VERB    com.microsoft.omadm.platforms.android.wifimgr.WifiProfile    15118    04142  Starting to parse Wifi Profile XML with name '<profile ID>'.
2019-08-01T19:22:46.7490000    VERB    com.microsoft.omadm.platforms.android.wifimgr.OneX    15118    04142    Starting to parse OneX from Wifi XML.
2019-08-01T19:22:46.8100000    VERB    com.microsoft.omadm.platforms.android.wifimgr.OneX    15118    04142    Completed parsing OneX from Wifi XML.
2019-08-01T19:22:46.8209999    VERB    com.microsoft.omadm.platforms.android.wifimgr.WifiProfile    15118    04142    Completed parsing Wifi Profile XML with name '<profile ID>'.
2019-08-01T19:22:46.8240000    INFO    com.microsoft.omadm.utils.CertificateSelector    15118    04142    Selected ca document with alias: 'user:205xxxxx.0' and thumbprint '<thumbprint>'.
2019-08-01T19:22:47.0990000    VERB    com.microsoft.omadm.platforms.android.certmgr.CertificateChainBuilder    15118    04142    Complete certificate chain built with Consummate certs.
2019-08-01T19:22:47.1010000    VERB    com.microsoft.omadm.utils.CertUtils    15118    041421 cert(s) matched criteria: User<ID>[i:<ID>,17CECEA1D337FAA7D167AD83A8CC7A8FCBF9xxxx;eku:ane.3.6.1.5.5.7.3.one,one.3.6.ane.5.v.7.3.2]
2019-08-01T19:22:47.1090000    VERB    com.microsoft.omadm.utils.CertUtils    15118    04142    0 cert(s) excluded by criteria:
2019-08-01T19:22:47.1110000    INFO    com.microsoft.omadm.utils.CertificateSelector    15118    04142    Selected client cert with alias 'User<ID>' and requestId 'ModelName=<ModelName>%2FLogicalName_<LogicalName>;Hash=-912418295'.
2019-08-01T19:22:47.4120000    VERB    com.microsoft.omadm.Services    15118    04142Successfully applied, enabled and saved wifi profile '<profile ID>'
2019-08-01T19:22:47.4240000    VERB    com.microsoft.omadm.platforms.android.wifimgr.OneX    15118    04142    Starting to parse OneX from Wifi XML.
2019-08-01T19:22:47.4910000    VERB    com.microsoft.omadm.platforms.android.wifimgr.OneX    15118    04142    Completed parsing OneX from Wifi XML.
2019-08-01T19:22:47.4970000    VERB    com.microsoft.omadm.platforms.android.wifimgr.WifiProfile    15118    04142    Starting to parse Wifi Profile XML with proper name '<profile ID>'.
2019-08-01T19:22:47.5080000    VERB    com.microsoft.omadm.platforms.android.wifimgr.OneX    15118    04142    Starting to parse OneX from Wifi XML.
2019-08-01T19:22:47.5820000    VERB    com.microsoft.omadm.platforms.android.wifimgr.OneX    15118    04142    Completed parsing OneX from Wifi XML.
2019-08-01T19:22:47.5900000    VERB    com.microsoft.omadm.platforms.android.wifimgr.WifiProfile    15118    04142    Completed parsing Wifi Profile XML with proper noun '<profile ID>'.
2019-08-01T19:22:47.5910000    INFO    com.microsoft.omadm.platforms.android.wifimgr.WifiProfileManager    15118    04142  Applied profile <contour ID>

On an iOS device, the Company Portal log doesn't contain whatsoever data about Wi-Fi profiles. To meet details near the installation of the Wi-Fi profiles, examine the Console and Device logs. To practise this, follow these steps:

1. Connect the iOS device to Mac, and then go to Applications > Utilities to open the Console app.

   

2. Under Action, selectInclude Info Messages and Include Debug Letters.

   

3. Afterwards the problem is reproduced, salve the logs to a text file. To exercise this, selectEdit > Select All to select all the messages on the electric current screen, and and so selectEdit > Copy to copy the letters to the clipboard. Side by side, open up the TextEdit application, paste the copied logs into a new text file, and so save the file.

Yous tin can search the file that has the Wi-Fi profile name to view detailed information.

Sample log snippet:

Line 390870: debug    11:19:58.994815 -0400    profiledAdding dependent world wide web.windowsintune.com.wifi.Contoso to parent Microsoft.Profiles.MDM in domain ManagingProfileToManagedProfile to system\
Line 390872: debug    xi:19:58.995210 -0400    profiledAdding dependent Microsoft.Profiles.MDM to parent world wide web.windowsintune.com.wifi.Contoso in domain ManagedProfileToManagingProfile to organization\
Line 392346: default    11:19:59.360460 -0400    profiledContour \'93www.windowsintune.com.wifi.Contoso\'94 installed.\

On a Windows device, the details about Wi-Fi profiles are logged in the following location in Issue Viewer:

• Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostic-Provider > Admin

Note Y'all must select the Show Analytic and Debug Logs selection in Event Viewer to run into these logs.

Sample log snippet:

Log Name:      Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin
Source:        Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider
Date:          8/7/2019 viii:01:41 PM
Effect ID:      1506
Job Category: (1)
Level:         Information
Keywords:      (2)
User:          Organisation
Estimator:      <Figurer Name>
Description:
WiFiConfigurationServiceProvider: Node set value, type: (0x4), Result: (The operation completed successfully.).

Troubleshooting common issues

Issue i: The Wi-Fi contour isn't deployed to the device

• Verify that the Wi-Fi profile is assigned to the correct group.

  In the Intune portal, get toDevice configuration >Profiles,selectAssignments, and and so examine the selected groups.

  

  Also review the Assignments information in the Troubleshoot pane.
  

  

• Verify that the device can sync with Intune by checking the Last Check In time in the Troubleshoot pane.

• If the Wi-Fi profile is linked to the Trusted Root and SCEP profiles, verify that both profiles have been deployed to the device. The Wi-Fi profile has a dependency on these profiles.
  

  
  If the Trusted Root and SCEP profiles aren't installed on the device, you volition see the following entry in the Company Portal Omadmlog file:

  2019-08-01T19:18:xiii.5120000    INFO    com.microsoft.omadm.platforms.android.wifimgr.WifiProfileManager    15118    04105Skipping Wifi profile <profile ID> because it is pending certificates.

  Note There is a scenario in which the Trusted Root and SCEP profiles are on the device and compliant but the Wi-Fi profile is however non on the device. This situation occurs when the CertificateSelector provider from the Company Portal app doesn't find a document that matches the specified criteria. The specific criteria can be on the Document Template or in the SCEP contour. If a matching document isn't establish, the certificates on the device will be excluded. This will cause the Wi-Fi profile to be skipped considering it doesn't have the correct certificate. In this scenario, yous see the following entry in the Company Portal Omadmlog file:

  Skipping Wifi contour <profile ID> because it is pending certificates.

  The following is a sample log snippet in which certificates are excluded because the Any Purpose Extended Key Usage
  (EKU) criteria was specified just the certificates that are assigned to the device don't have that EKU:
  

  2018-11-27T21:10:37.6390000    VERB     com.microsoft.omadm.utils.CertUtils      14210    00948Excluding cert with allonym User<ID1> and requestId <requestID1> as it does non have whatsoever purpose EKU.
  2018-xi-27T21:ten:37.6400000    VERB     com.microsoft.omadm.utils.CertUtils      14210    00948Excluding cert with alias User<ID2> and requestId <requestID2> as it does not have any purpose EKU.
  2018-xi-27T21:10:37.6400000    VERB     com.microsoft.omadm.utils.CertUtils      14210    00948    0 cert(s) matched criteria:
  2018-11-27T21:10:37.6400000    VERB     com.microsoft.omadm.utils.CertUtils      14210    00948    2 cert(s) excluded by criteria:
  2018-11-27T21:10:37.6400000    INFO       com.microsoft.omadm.platforms.android.wifimgr.WifiProfileManager       14210                00948Skipping Wifi profile <contour ID> because it is awaiting certificates.

  In this instance, the SCEP profile has the option of Any Purpose EKU specified, only information technology is not specified in the Document Template on the document dominance (CA). To fix the issue, add the Whatever Purpose option to the certificate template, or remove the Any Purpose pick from the SCEP profile.

  

  

• Verify that all required certificates in the consummate certificate chain are on the device. Otherwise, the Wi-Fi profile tin can't be installed on the device. For more data, encounter Missing intermediate document authorisation.

• Filter Omadmlog with keyword to await for useful information, such every bit what certificate is used for the Wi-Fi contour and whether it was practical or not.
  

  For example, you tin can use CMTrace to read the logs and utilise the search string filter of "wifimgr".

  

  Sample log snippet:

  

  If you see an error in the log, copy the time stamp of the error and un-filter the log.  Then use the "find" option with the time stamp to see what happened right before the error occurred.

• Verify that the Wi-Fi contour is assigned to the right grouping.

  In the Intune portal, go toDevice configuration >Profiles,select the profile >Assignments,verify the selected groups.

  

  As well review the Assignments data in the Troubleshoot pane.

  

• Verify that the device can sync with Intune past checking the Final Check In time in the Troubleshoot pane.

• If the Wi-Fi profile is linked to the Trusted Root and SCEP profiles, verify that both profiles accept been deployed to the device. The Wi-Fi profile has a dependency on these profiles.
  

• Verify that the Wi-Fi profile is assigned to the correct grouping.

  In the Intune portal, go toDevice configuration >Profiles,select the profile >Assignments,verify the selected groups.

  

  Likewise review the Assignments data in the Troubleshoot pane.

  

• Verify that the device tin can sync with Intune by checking the Concluding Check In time in the Troubleshoot pane.

• If the Wi-Fi profile is linked to the Trusted Root and SCEP profiles, verify that both profiles have been deployed to the device. The Wi-Fi contour has a dependency on these profiles.
  

• Examine the MDM Diagnostic Information log from Windows 10 devices.

  To do this, download the MDM Diagnostic Information log. Then, open File Explorer, and navigate to c:\Users\Public\Documents\MDMDiagnostics to see the study.

  

  

  

  

Issue 2: The Wi-Fi profile is deployed to the device, just the device can't connect to the network

Typically this is non an Intune event. There can exist multiple causes of a connectivity event. The post-obit items may help you understand and troubleshoot the outcome:

• Tin you manually connect to the network past using a certificate that has the same criteria that's specified in the Wi-Fi profile?

  If and then, examine the properties of the document that yous used in the manual connection and make changes to the Intune Wi-Fi profile accordingly.

• Did the Radius server log show that the device tried to connect by using the Wi-Fi profile? Usually, connectivity errors are logged in the Radius server log.

More information

If you're however looking for a solution to a related trouble, or if you want more data about Intune, mail a question in our Microsoft Intune forum. Many back up engineers, MVPs, and members of our development squad visit the forums. So, at that place's a good risk that you can detect someone who has the information that you need.

If you lot want to open up a support request with the Microsoft Intune Support team, see the following article:

How to get back up for Microsoft Intune

For more information about Wi-Fi profiles in Microsoft Intune, see the following articles:

• Add Wi-Fi settings for devices running Android in Microsoft Intune

• Add Wi-Fi settings for iOS devices in Microsoft Intune

• Add Wi-Fi settings for Windows 10 and after devices in Intune

• Back up Tip - How to configure NDES for SCEP certificate deployments in Intune

• Troubleshooting SCEP certificate contour deployment in Microsoft Intune

• Troubleshooting NDES configuration for use with Microsoft Intune certificate profiles

For all the latest news, information, and tech tips, visit our official blogs:

• The Microsoft Intune Support Team Weblog

• The Microsoft Enterprise Mobility and Security Blog

malleymottee.blogspot.com

Source: https://support.microsoft.com/en-us/topic/troubleshooting-wi-fi-profile-issues-in-microsoft-intune-23c9261f-3b0c-95fa-81e2-b894f645ce97

Share this post