
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-02-2020 11:46 PM
from lansweeper test tool:
my test for scanning intune:
2020-09-02 17:39:26,287 [1] INFO LOGINTUNESCANNING ERROR Error checking Intune credential (Id 0: 'Intune') The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.IdentityModel.Clients.ActiveDirectory.HttpWebRequestWrapper.<GetResponseSyncOrAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.IdentityModel.Clients.ActiveDirectory.HttpHelper.<SendPostRequestAndDeserializeJsonResponseAsync>d__0`1.MoveNext()
my test for scanning o365:
2020-09-02 17:40:27,792 [1] INFO LOGOFFICE365SCANNING DEBUG Office 365 - Session creation error: The 'Connect-MsolService' command was found in the module 'MSOnline', but the module could not be loaded. For more information, run 'Import-Module MSOnline'.
i checked and the module exists and was installed as admin available to the whole system.
my test for scanning intune:
2020-09-02 17:39:26,287 [1] INFO LOGINTUNESCANNING ERROR Error checking Intune credential (Id 0: 'Intune') The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.IdentityModel.Clients.ActiveDirectory.HttpWebRequestWrapper.<GetResponseSyncOrAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.IdentityModel.Clients.ActiveDirectory.HttpHelper.<SendPostRequestAndDeserializeJsonResponseAsync>d__0`1.MoveNext()
my test for scanning o365:
2020-09-02 17:40:27,792 [1] INFO LOGOFFICE365SCANNING DEBUG Office 365 - Session creation error: The 'Connect-MsolService' command was found in the module 'MSOnline', but the module could not be loaded. For more information, run 'Import-Module MSOnline'.
i checked and the module exists and was installed as admin available to the whole system.
Labels:
- Labels:
-
General Discussion
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-04-2020 06:53 PM
I'm seeing the exact same behavior. We did manage to get it work work once, but haven't been successful in other attempts. On the assets that were imported, they did not get inserted into the Intune device tables but were deposited in the Assets tables with very little information.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-03-2020 12:59 AM
so i re-created the app registration based on a suggestion from another thread, and now the test tool works.
2020-09-02 18:56:18,247 [1] INFO Open TestTool
2020-09-02 18:56:49,491 [1] INFO LOGINTUNESCANNING DEBUG Fetching Intune devices
2020-09-02 18:56:50,319 [1] INFO LOGINTUNESCANNING DEBUG Found 1 Intune devices
2020-09-02 18:56:50,350 [1] INFO LOGINTUNESCANNING DEBUG Scan Intune container with app Id 'my app guid', using email 'my account'
2020-09-02 18:56:50,804 [1] INFO LOGINTUNESCANNING DEBUG Fetching Intune devices
but it still wont work from the lansweeper website/service
2020-09-02 18:56:18,247 [1] INFO Open TestTool
2020-09-02 18:56:49,491 [1] INFO LOGINTUNESCANNING DEBUG Fetching Intune devices
2020-09-02 18:56:50,319 [1] INFO LOGINTUNESCANNING DEBUG Found 1 Intune devices
2020-09-02 18:56:50,350 [1] INFO LOGINTUNESCANNING DEBUG Scan Intune container with app Id 'my app guid', using email 'my account'
2020-09-02 18:56:50,804 [1] INFO LOGINTUNESCANNING DEBUG Fetching Intune devices
but it still wont work from the lansweeper website/service
