OpenUEM - An Open Source Unified Endpoint Manager
Replies: 3 comments
|
Sure, most of the tables in the console should have a search dialog, I'll try to implement a new component for that and discuss it suits our needs |
|
💡💡💡. Understood. The user logged into the PC opens the store → sees only the IT-approved software → installs/uninstalls by themselves. In OpenUEM, administrators approve, publish, and control which applications will appear in the internal store on user computers. Below is the ideal architecture, followed by three different ways to deploy this internal store, all 100% compatible with OpenUEM. 🎯 FINAL GOAL — How it needs to work On the user’s Windows PC Icon: “📦 Company Application Store” Interface similar to Microsoft Store / Company Portal Catalog filtered by permissions User clicks → installs/uninstalls without needing administrator rights Execution and logs controlled by the OpenUEM agent In OpenUEM IT imports packages (Chocolatey/MSI/EXE) IT approves and publishes into the catalog IT defines which AD groups can see each app OpenUEM generates the dynamic catalog for the Windows client This is fully possible using open-source tools and the OpenUEM API. 🧩 IDEAL ARCHITECTURE (OPEN-SOURCE + WINDOWS + OPENUEM) WINDOWS USER ⭐ THREE WAYS TO IMPLEMENT THE INTERNAL STORE 🔵 OPTION 1 — Simple and Fast ✔️ “Chocolatey GUI + Internal Repository + OpenUEM as orchestrator” How it works The user opens Chocolatey GUI (visual store, open-source). They see only the packages that OpenUEM allows. When clicking install/remove → Chocolatey executes the silent installer. OpenUEM records everything. How administrators approve software in OpenUEM
“Add Software” Provide package → create metadata Mark as Approved Publish to AD groups How the store appears in Windows Create a shortcut named “Company Internal Store” Chocolatey GUI lists only the internal repository User clicks and installs Pros Very quick to implement Ready-to-use interface Pure open-source Zero development required Cons Limited interface (not fully customizable) Does not display polished icons by default (can be customized) 🟣 OPTION 2 — Internal Store inside OpenUEM ✔️ “OpenUEM Web Portal → Windows Agent → Chocolatey/Script” How it works User opens the OpenUEM Portal → “Internal Store” Modern interface (React/Bootstrap) App list based on group/permission Buttons: Install, Uninstall, Update Commands are sent to the PC via the OpenUEM agent On Windows The logged-in user gets: Desktop icon “Company Applications” Opens a web browser → internal OpenUEM store Fully authenticated through AD/SSO How administrators approve In the OpenUEM panel:
Pros Full corporate experience No external interfaces needed Completely controlled by IT Catalog filtered by policy Cons Requires installing an add-on or module in OpenUEM More configuration needed 🟢 OPTION 3 — Native Windows Application Store ✔️ “Windows UWP/WinUI/React Native App + OpenUEM API” How it works A dedicated Windows application, with a Store-like interface: Shows approved apps via the OpenUEM API User clicks → app triggers the OpenUEM agent → installs/uninstalls IT controls everything via OpenUEM Recommended stack UX: WinUI 3 or Electron (open-source) Backend: OpenUEM API + Nexus repository Installation engine: Chocolatey/Silent scripts Pros Best user experience Fully customizable Icons, screenshots, categories, search Cons Requires development More maintenance 📦 COMPLETE SOFTWARE LIFECYCLE IN THE INTERNAL STORE
IT downloads the original installer Packages it as .nupkg or silent .msi Uploads to Nexus / Artifactory
Tests the software in a staging environment Validates silent install and uninstall Registers in OpenUEM: name, version, icon, category Marks “Approved for Internal Store”
Defines AD groups Example: “Finance can install Office” Defines permissions: Install Uninstall Update Enables: “Show in Windows Internal Store”
Depending on the chosen model: Option 1 (Chocolatey GUI) User opens “Application Store” Sees allowed apps Clicks → installs Option 2 (OpenUEM Portal) Desktop icon Opens web portal Sees allowed apps Clicks → installs Option 3 (Windows App) Native app with Store-like layout Executes via API
OpenUEM shows: Who installed When installed Installed version Failures Uninstall history Per-machine history Everything is visible in the OpenUEM dashboard. 🧱 REQUIRED COMPONENTS (LICENSE-FREE) Component Function Open-source? Nexus OSS Package repository ✔️ If you want, I can also: |
|
I'm closing the discussion as the search field was added, I'll save the information provided by @wallabarizon-hue for a different feature Thank you both |
Uh oh!
There was an error while loading. Please reload this page.
Hi Miguel,
I think it would be a good idea to add a software search button to the software list, to find out if software has been deployed correctly on a computer. This is a common task for an administrator.
Thanks again.
All reactions