Project

General

Profile

Actions
Copy link

Improvement #10304

open

Task #12671: Improvements to wipe device functionality

Improvement to Windows wipe operation handling

Added by Navod Zoysa almost 2 years ago. Updated 14 days ago.

Status:
Testing
Priority:
Medium
Assignee:
Thilina Sandaruwan
Start date:
24/04/2025
Due date:
12/06/2025 (19 days late)
% Done:

100%

Estimated time:
127:00 h
Device Type:
Windows
Component:
Device Management
Type:
Windows
QA Start Time:
QA Due Time:
QA Estimated Time(Hours):

Description

With the current implementation after the wipe command is sent to the device, the server does not receive any response whether the command was accepted or not. Due to this the operation is changed from pending state to completed without checking for a device response and then the device will be disenrolled.

In the future it would be ideal to find a way to guarantee that the wipe command was successfully triggered and to add different options to wipe i.e wipe device without removing user data [1]

[1] RemoteWipe CSP - https://learn.microsoft.com/en-us/windows/client-management/mdm/remotewipe-csp#dowipe

Actions
Copy link
 #1

Updated by Arshana Atapattu almost 2 years ago

  • Project changed from PRODUCT IOTS to 33
  • Category deleted (Backend)
Actions
Copy link
 #2

Updated by Viranga Gunarathna over 1 year ago

  • Project changed from 33 to Backlog
Actions
Copy link
 #3

Updated by Navod Zoysa 4 months ago

  • Project changed from Backlog to product-uem 7.0.0 GA
  • Parent task set to #12671
  • Type set to Windows
Actions
Copy link
 #4

Updated by Subodhinie chathurajika 2 months ago

  • Assignee set to Thilina Sandaruwan
Actions
Copy link
 #5

Updated by Thilina Sandaruwan 2 months ago

  • Due date set to 02/05/2025
  • Status changed from New to Implementation
  • Start date set to 24/04/2025
Actions
Copy link
 #6

Updated by Thilina Sandaruwan about 2 months ago

  • % Done changed from 0 to 90
Actions
Copy link
 #7

Updated by Thilina Sandaruwan about 2 months ago

  • Due date changed from 02/05/2025 to 19/05/2025
  • Status changed from Implementation to Testing
Actions
Copy link
 #8

Updated by Subodhinie chathurajika about 1 month ago

  • Estimated time set to 20:00 h
Actions
Copy link
 #9

Updated by Subodhinie chathurajika about 1 month ago

  • Priority changed from None to Medium
Actions
Copy link
 #10

Updated by Thilina Sandaruwan 29 days ago

  • Due date changed from 19/05/2025 to 04/06/2025
Actions
Copy link
 #11

Updated by Thilina Sandaruwan 20 days ago

  • Due date changed from 04/06/2025 to 12/06/2025
  • Estimated time changed from 20:00 h to 127:00 h

Estimated time updated due to the need to test the full feature and fix newly identified bugs using the virtual machine. Also included time to identify and working with a few issues in ui-components.

Actions
Copy link
 #12

Updated by Thilina Sandaruwan 14 days ago

  • % Done changed from 90 to 100
Actions
Copy link

Also available in: Atom PDF