(12.04.120-de_orig) Troubleshooting: UMS as Update Proxy
- Emese Pogany
- Harald Saller
Translation needed
The content of this page was copied from another page tree and needs to be translated or updated.
When you finish translation, make sure to
-
Replace the label NEEDS-TRANSLATING with TRANSLATED
-
Remove this macro from the page
This article collects possible troubleshootings for when you are using the UMS App proxy feature or your UMS doesn't have internet access., and you get the following error message: "Failed getting metadata from all APP Portals".
Possible reason 1:
Microsoft Defender Antivirus blocked the UMS App Proxy functionality.
On the client i got the Error Failed to get meta data from app portal.
Solution 1:
In the Filesystem of the UMS Server C:\Program Files\IGEL\RemoteManager\rmguiserver\persistent folder was missing.
In this folder we host the apps including the meta data.
We had to create a local group policy or change the domain wide policy to exclude the C:\Program Files\IGEL\RemoteManager\ folder from Microsoft Defender Antivirus.
The policy can be found under: Computer Configuration - Administrative Templates - Windows Components - Microsoft Defender Antivirus - Exclusions - Path Exclusions
This needs to be enabled and C:\Program Files\IGEL\RemoteManager to be added.
Possible reason 2:
Bug
In addition to the Defender Exclusion list, there is a difference between Upload App Icon and the Upload Button in the App Settings.
This button seems to only import the meta data, independent if you choose a .iam or .ipkg file.
The App will not be copied into the local App Proxy cache.
Solution 2;
The Upload Button in the WebApp App Settings, imports the meta Data and copies the app to the Proxy cache folder in the Filesystem.
even if the app is available from the portal, it seems that the apps download to the ums "persistent" folder is only triggered when you try to deploy it to the first device (as opposed to when clicking on "import" from the app portal)
They have just tested importing the same base system but with the 2nd button now, although they received the below message, after closing it the app was copied to the ums 'Persistent' folder and they could deploy fine