Project

General

Profile

Actions

Bug #10575

closed

Backlog - Bug #10554: [Windows] Issues and improvements for windows azure and PPKG enrollments

Initial pending operations added in bulk enrolled devices through OOBE throws null pointers when updating application list

Added by Arshana Atapattu 10 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Medium
Assignee:
Start date:
14/06/2024
Due date:
16/06/2024
% Done:

100%

Estimated time:
Device Type:
Windows
Component:
Type:
Windows

Description

Environment details
6.0.1 server

Prerequisites
Windows Bulk enrolled device

Steps
Initial pending operations

Description
Initial pending operations added in bulk enrolled devices through OOBE throws null pointers when updating application list

"In OOBE enrollments the device syncing shows abnormal behaviour. There seems to be more than 10-20 SyncML requests per second coming from the device, this seems to be an issue with polling interval not getting added correctly and there are null pointers thrown when updating application list in the initial pending operations. This is due to the device sending empty responses in the response body without any SyncML tags. "

Doc: https://docs.google.com/spreadsheets/d/18pkOLACeNSq9vbLUKo4CA7jfuKka3om5YB-Y5IwvB_8/edit?usp=sharing

Actions #1

Updated by Arshana Atapattu 10 months ago

  • Parent task set to #10554
Actions #2

Updated by Arshana Atapattu 10 months ago

  • Description updated (diff)
Actions #3

Updated by Navod Zoysa 5 months ago

  • Project changed from Backlog to product-uem 6.2.0 GA
  • Due date set to 16/06/2024
  • Status changed from New to QA
  • Priority changed from None to Medium
  • Start date changed from 24/01/2024 to 14/06/2024
  • % Done changed from 0 to 100
  • Device Type set to Windows
  • Type set to Windows
Actions #4

Updated by Arshana Atapattu 5 months ago

  • Status changed from QA to QA Accept

This is working, now syncing devices when enrolled.
Now doesn't take 20 minutes to sync

Actions #5

Updated by Arshana Atapattu 5 months ago

  • Status changed from QA Accept to Closed

Closing due to QA accept

Actions

Also available in: Atom PDF