Managed App Configuration - Revision history

CWI at 13:50, 18 September 2025

2025-09-18T13:50:57Z

CWI at 10:20, 18 September 2025

2025-09-18T10:20:09Z

LGE at 08:06, 12 September 2024

2024-09-12T08:06:13Z

LGE at 14:39, 10 September 2024

2024-09-10T14:39:48Z

JKN at 14:22, 3 January 2023

2023-01-03T14:22:14Z

MKR: Updated number of max profiles from 9 to 25

2022-04-25T12:30:22Z

Updated number of max profiles from 9 to 25

MKR at 14:26, 23 August 2021

2021-08-23T14:26:27Z

MKR at 13:47, 23 August 2021

2021-08-23T13:47:09Z

MKR at 13:43, 23 August 2021

2021-08-23T13:43:07Z

MKR at 15:28, 19 August 2021

2021-08-19T15:28:25Z

@@ Line 1: / Line 1: @@
 In enterprise environments, there are sometimes hundreds of employee phones centrally managed by some EMM (Enterprise Mobility Management) software. This not only allows to limit the apps available for use (via a company-internal store ("Company App Store")) and remotely wipe devices (in the case of lost devices and fired employees), it also allows you to remotely set configurations of these apps to ease user experience. There are different types of management, like fully managed phones that belong to the company but also privately-owned phones with a work profile.
-Starting with [[Version_4.0_Xamarin| UBIK Xamarin Android 4.0]] and [[Version_4.8_Xamarin| UBIK Xamarin iOS 4.8]], the {{UBIK}} Xamarin app supports managed app configuration for configuring profiles. That removes the need to manually copy over a {{UBIK}} Profile to every phone and importing it before its users can use {{UBIK}}. Historically, there was also the need to deploy the customizing ("XAML") before the app could be properly used, however, this has been solved already with the help of the [[Deploy_UI_Customizings_(Client)|XAML rollout feature]].
+Starting with [[Version_4.0_Xamarin| UBIK Xamarin Android 4.0]] and [[Version_4.8_Xamarin| UBIK Xamarin iOS 4.8]], the {{UBIK}} Mobile app supports managed app configuration for configuring profiles. That removes the need to manually copy over a {{UBIK}} Profile to every phone and importing it before its users can use {{UBIK}}. Historically, there was also the need to deploy the customizing ("XAML") before the app could be properly used, however, this has been solved already with the help of the [[Deploy_UI_Customizings_(Client)|XAML rollout feature]].
 == Function ==
@@ Line 19: / Line 19: @@
 All that's necessary to get the profile rolled out is to open a profile in your favorite text editor (we recommend Visual Studio Code or Notepad++) and copy the entire content into the configuration value. If your EMM system doesn't want to paste in multi-line strings, use an XML-minifier first.
 [[Category:Mobile|Managed App Configuration]]

← Older revision		Revision as of 10:20, 18 September 2025
Line 20:		Line 20:

	[[Category:Version 4.0\|Managed App Configuration]]		[[Category:Version 4.0\|Managed App Configuration]]
−	[[Category:~~Xamarin~~\|Managed App Configuration]]	+	[[Category:Mobile\|Managed App Configuration]]

@@ Line 1: / Line 1: @@
 In enterprise environments, there are sometimes hundreds of employee phones centrally managed by some EMM (Enterprise Mobility Management) software. This not only allows to limit the apps available for use (via a company-internal store ("Company App Store")) and remotely wipe devices (in the case of lost devices and fired employees), it also allows you to remotely set configurations of these apps to ease user experience. There are different types of management, like fully managed phones that belong to the company but also privately-owned phones with a work profile.
@@ Line 20: / Line 18: @@
 All that's necessary to get the profile rolled out is to open a profile in your favorite text editor (we recommend Visual Studio Code or Notepad++) and copy the entire content into the configuration value. If your EMM system doesn't want to paste in multi-line strings, use an XML-minifier first.
 [[Category:Version 4.0|Managed App Configuration]]
 [[Category:Xamarin|Managed App Configuration]]

@@ Line 1: / Line 1: @@
 In enterprise environments, there are sometimes hundreds of employee phones centrally managed by some EMM (Enterprise Mobility Management) software. This not only allows to limit the apps available for use (via a company-internal store ("Company App Store")) and remotely wipe devices (in the case of lost devices and fired employees), it also allows you to remotely set configurations of these apps to ease user experience. There are different types of management, like fully managed phones that belong to the company but also privately-owned phones with a work profile.
-Starting with [[Version_4.0_Xamarin| App Version 4.0.0]], the {{UBIK}} Xamarin app supports managed app configuration for configuring profiles. That removes the need to manually copy over a {{UBIK}} Profile to every phone and importing it before its users can use {{UBIK}}. Historically, there was also the need to deploy the customizing ("XAML") before the app could be properly used, however, this has been solved already with the help of the [[Deploy_UI_Customizings_(Client)|XAML rollout feature]].
+Starting with [[Version_4.0_Xamarin| UBIK Xamarin Android 4.0]] and [[Version_4.8_Xamarin| UBIK Xamarin iOS 4.8]], the {{UBIK}} Xamarin app supports managed app configuration for configuring profiles. That removes the need to manually copy over a {{UBIK}} Profile to every phone and importing it before its users can use {{UBIK}}. Historically, there was also the need to deploy the customizing ("XAML") before the app could be properly used, however, this has been solved already with the help of the [[Deploy_UI_Customizings_(Client)|XAML rollout feature]].
 == Function ==
 The new '''''profile rollout''''' feature allows for the rollout of up to 25 individual [[Settings|Ubik Profiles]]. The configuration supports the [https://appconfig.org/ AppConfig.org] standard, allowing compatibility to almost every EMM software. During the application start, the current configuration values are read and profiles created (with <code>.managed.profile</code> ending). All profiles created by the system will be updated to the current configuration during the startup phase, allowing recently configured profiles to appear and no longer configured profiles to be removed. Other profiles added to the {{UBIK}} application will not be affected by this system (except they have a <code>.managed.profile</code> ending for some unknown reason). Clearing all profiles also clears the configured profiles, and the app needs to be restarted for them to update.
-On Android, the system makes use of the Android Restrictions System. On iOS, the NSUserDefaults System is used. These libraries are native to the system and widely supported.
+{{Hint|On Android, the system makes use of the Android Restrictions System. On iOS, the NSUserDefaults System is used. These libraries are native to the system and widely supported.}}
 == Configuration==
@@ Line 18: / Line 20: @@
 All that's necessary to get the profile rolled out is to open a profile in your favorite text editor (we recommend Visual Studio Code or Notepad++) and copy the entire content into the configuration value. If your EMM system doesn't want to paste in multi-line strings, use an XML-minifier first.
 [[Category:Version 4.0|Managed App Configuration]]
 [[Category:Xamarin|Managed App Configuration]]

@@ Line 1: / Line 1: @@
 In enterprise environments, there are sometimes hundreds of employee phones centrally managed by some EMM (Enterprise Mobility Management) software. This not only allows to limit the apps available for use (via a company-internal store ("Company App Store")) and remotely wipe devices (in the case of lost devices and fired employees), it also allows you to remotely set configurations of these apps to ease user experience. There are different types of management, like fully managed phones that belong to the company but also privately-owned phones with a work profile.
-Starting with [[Version_4.0_Xamarin| App Version 4.0.0]], the {{UBIK}} Xamarin app will support managed app configuration for configuring profiles. That removes the need to manually copy over a Ubik Profile to every phone and importing it before its users can use Ubik. Historically, there was also the need to deploy the customizing ("XAML") before the app could be properly used, however, this has been solved already with the help of the [[Deploy_UI_Customizings_(Client)|XAML rollout feature]].
+Starting with [[Version_4.0_Xamarin| App Version 4.0.0]], the {{UBIK}} Xamarin app supports managed app configuration for configuring profiles. That removes the need to manually copy over a {{UBIK}} Profile to every phone and importing it before its users can use {{UBIK}}. Historically, there was also the need to deploy the customizing ("XAML") before the app could be properly used, however, this has been solved already with the help of the [[Deploy_UI_Customizings_(Client)|XAML rollout feature]].
 == Function ==
-The new '''''profile rollout''''' feature allows for the rollout of up to 25 individual [[Settings|Ubik Profiles]]. The configuration supports the [https://appconfig.org/ AppConfig.org] standard, allowing compatibility to almost every EMM software. During the application start, the current configuration values are read and profiles created (with <code>.managed.profile</code> ending). All profiles created by the system will be updated to the current configuration during the startup phase, allowing recently configured profiles to appear and no longer configured profiles to be removed. Other profiles added to the Ubik application will not be affected by this system (except they have a <code>.managed.profile</code> ending for some unknown reason). Clearing all profiles also clears the configured profiles, and the app needs to be restarted for them to update.
+The new '''''profile rollout''''' feature allows for the rollout of up to 25 individual [[Settings|Ubik Profiles]]. The configuration supports the [https://appconfig.org/ AppConfig.org] standard, allowing compatibility to almost every EMM software. During the application start, the current configuration values are read and profiles created (with <code>.managed.profile</code> ending). All profiles created by the system will be updated to the current configuration during the startup phase, allowing recently configured profiles to appear and no longer configured profiles to be removed. Other profiles added to the {{UBIK}} application will not be affected by this system (except they have a <code>.managed.profile</code> ending for some unknown reason). Clearing all profiles also clears the configured profiles, and the app needs to be restarted for them to update.
 On Android, the system makes use of the Android Restrictions System. On iOS, the NSUserDefaults System is used. These libraries are native to the system and widely supported.
 == Configuration==
-Microsoft Intune is just one of the EMM systems that will work with Ubik. This is the system that Augmensys uses for internal testing. For other EMM systems, the process will be similar.
+Microsoft Intune is just one of the EMM systems that will work with {{UBIK}}. This is the system that Augmensys uses for internal testing. For other EMM systems, the process will be similar.
-For Intune, an Application Configuration Policy can be defined. It is possible to limit the scope of this policy to groups, devices, and even device management types. In the Configuration Designer, the desired values can be chosen, but for Ubik, all of them do the same and only differ by the number. For other EMM systems, this might be different, but you should end up with something similar-looking:
+For Intune, an Application Configuration Policy can be defined. It is possible to limit the scope of this policy to groups, devices, and even device management types. In the Configuration Designer, the desired values can be chosen, but for {{UBIK}}, all of them do the same and only differ by the number. For other EMM systems, this might be different, but you should end up with something similar-looking:
-[[File:managed-app-configuration.png|thumb|none|750px|Screenshot of creating an App Configuration for Ubik in Microsoft Intune/Endpoint. Note that in the right panel the items to configure can be chosen.|center]]
+[[File:managed-app-configuration.png|thumb|none|750px|Screenshot of creating an App Configuration for {{UBIK}} in Microsoft Intune/Endpoint. Note that in the right panel the items to configure can be chosen.|center]]
-It is currently possible to define 25 Ubik profiles using this technology.
+It is currently possible to define 25 {{UBIK}} profiles using this technology.
 All that's necessary to get the profile rolled out is to open a profile in your favorite text editor (we recommend Visual Studio Code or Notepad++) and copy the entire content into the configuration value. If your EMM system doesn't want to paste in multi-line strings, use an XML-minifier first.

← Older revision		Revision as of 13:47, 23 August 2021
Line 20:		Line 20:

	[[Category:Xamarin\|Managed App Configuration]]		[[Category:Xamarin\|Managed App Configuration]]
		+	[[Category:Version 4.0\|Managed App Configuration]]