Project

General

Profile

Actions
Copy link

Task #12169

closed

New Feature #11197: ADMX ingestion support (Custom policies)

User Interface for ADMX Ingestion File Upload

Added by Thilina Sandaruwan 5 months ago. Updated 1 day ago.

Status:
Closed
Priority:
None
Assignee:
Thilina Sandaruwan
Start date:
12/11/2024
Due date:
17/11/2024
% Done:

100%

Estimated time:
Type:
UI

Description

Description
  • Develop a user-friendly UI for uploading ADMX and ADML files, including status and error messages for successful/failed imports.
Tasks
  • Design UI for file upload with fields for selecting ADMX and ADML files.
  • Implement progress tracking and status display (e.g., Available, Error).
  • Include error messages for file validation and dependency issues

Files

Download all files
Screenshot from 2025-02-07 17-36-00.png (104 KB) Screenshot from 2025-02-07 17-36-00.png [1] Arshana Atapattu, 10/02/2025 12:34 PM
Screenshot from 2025-02-17 07-49-11.png (48.2 KB) Screenshot from 2025-02-17 07-49-11.png Thilina Sandaruwan, 17/02/2025 02:20 AM
Screenshot from 2025-02-17 07-52-53.png (219 KB) Screenshot from 2025-02-17 07-52-53.png Thilina Sandaruwan, 17/02/2025 02:23 AM
Actions
Copy link
 #1

Updated by Thilina Sandaruwan 5 months ago

  • Due date set to 17/11/2024
  • Start date changed from 04/11/2024 to 12/11/2024
Actions
Copy link
 #2

Updated by Thilina Sandaruwan 5 months ago

  • Status changed from New to Implementation
  • % Done changed from 0 to 90
Actions
Copy link
 #3

Updated by Thilina Sandaruwan 3 months ago

  • Tracker changed from New Feature to Task
  • Device Type deleted (Windows)
  • Component deleted (Device Management)
Actions
Copy link
 #4

Updated by Thilina Sandaruwan 3 months ago

  • % Done changed from 90 to 100
Actions
Copy link
 #5

Updated by Thilina Sandaruwan 3 months ago

  • Status changed from Implementation to QA
Actions
Copy link
 #6

Updated by Arshana Atapattu 2 months ago

  • Project changed from product-uem 7.0.0 GA to product-uem 6.4.0 GA
Actions
Copy link
 #7

Updated by Arshana Atapattu 2 months ago

https://roadmap.entgra.net/issues/12258
https://roadmap.entgra.net/issues/12256

will be QA along with this ticket.
the whole feature will be tested in this ticket

Actions
Copy link
 #8

Updated by Arshana Atapattu 2 months ago

Ingestion operation does not complete [1].
Other bus and improvements are mentioned in this ticket: https://roadmap.entgra.net/issues/12552

[1]
[1]

Actions
Copy link Download all files
 #9

Updated by Thilina Sandaruwan about 2 months ago

FIx with PR: https://github.com/entgra-proprietary/emm-proprietary-plugins/pull/102

  • Handle Windows response codes 406 and 425.
  • Now, when uploading a valid ADMX ingestion file, the policy will be installed on the Windows device, and the relevant registry entries will be created correctly. If an invalid file or a file with insufficient permissions is uploaded, the ingestion operation will move to an error state.
Actions
Copy link
 #10

Updated by Arshana Atapattu about 2 months ago

Cannot create same ADMX files for 2 tenants
need to fix this

Actions
Copy link
 #11

Updated by Thilina Sandaruwan 4 days ago

Previously, we added the tenant ID as a prefix to differentiate the ADMX configs. However, this caused an issue when applying the policies on the device side. The generated ADMX registry path included the tenant ID, but the LocURI used to apply the policies did not. As a result, the policies could not be applied. To resolve this issue, removed the tenant ID prefix from the ADMX ingestion install LocURI and then the registry path creation in this PR: https://github.com/entgra-proprietary/emm-proprietary-plugins/pull/147

Actions
Copy link
 #12

Updated by Arshana Atapattu 1 day ago

  • Status changed from QA to QA Accept

Feature is working

Actions
Copy link
 #13

Updated by Arshana Atapattu 1 day ago

  • Status changed from QA Accept to Closed

Closing due to QA accept

Actions
Copy link

Also available in: Atom PDF