LukeDC's Posts

So here is what support had me do a while back: After doing some digging, I found there have been some Scheduler improvements with In-memory scheduling. In console 1904, we automatically set the 'InMemoryScheduleryFeature' flag set to true. This allows the service to continue running even during a DB outage. Starting in console 1811, this option is available, but we must turn it on manually. Here are the steps you will need to take to enable this: 1. Get the Global OG UUID from the following db query: select LocationGroupUUID from LocationGroup (nolock) where locationgroupid = 7 2. Call the following API https://<host>/api/system/featureflag/InMemorySchedulerFeatureFlag/<GlobalOGUUID>/true where GlobalOGUUID is your UUID. retrieved from the step above. Method: POST Here are headers that are required: Headers: authorization: Basic [Base64 Encoded Credentials] content-type: application/json aw-tenant-code: [API Key] accept: application/json Expected response should be 204 No Content 3. Validate if Feature Flag is enabled by calling the following api. Expected response is 200. https://{host}/api/system/featureflag/InMemorySchedulerFeatureFlag/{GlobalOGUUID} Method: GET with the following response: { "name": "InMemorySchedulerFeatureFlag", "isEnabled": true, "state": "Production" }

Hi Paul, There should be no issue with them being in the domain. The SEG and DS servers usually sit in the DMZ and most best practices say your servers in the DMZ should not be domain joined. But it is not going to limit you in any way.

Hey there. Android App Configs can be very useful provided you meet the requirements: Devices need to be enrolled using Android Enterprise, legacy enrollments using the Device Admin model will not work. The app needs to support App Config standards You can figure this out by adding an app via the "iFrame" in the WS1 console. The app will indicate it is configurable as shown below: Once you add the app via the iFrame, you can configure it during the assignment phase. During the assignment setup you will find a section for "Application Configuration" and by enabling this option you will find a bunch of options filled in automatically by the app. Contact your vendor to get the appropriate values for each config option. Hope that helps. The main takeaway here is that you HAVE to use Android Enterprise. Without it, none of this works.

Not a whole lot. Just basics. CPU usage, disk usage, etc. Haven't found a need to go much further as I haven't seen performance issues. Are you using Cache servers? Memcached is recommended for large deployments.

Look at the architecture guides and make sure you are spec'ing your servers properly. It really makes a difference. Also make sure Windows is configured to handle the load with Virtual Memory settings, etc. If these are virtual servers (VMware, azure, etc) make sure they are also tuned to work with high pressure situations. Introduction to Workspace ONE UEM Recommended Architecture

We use SolarWinds. You can probably setup some fancy monitoring using it. Or if you are so inclined use some powershell scripts to check these things as well. Also seen Nagios - The Industry Standard In IT Infrastructure Monitoring  before and that was nice as well.

Hi! Sounds like you probably have a load balancer involved here. If you do you can easily just set up your 2016 servers and add them to the pool(s). Then when you're satisfied they are working fine, remove the 2012 servers from the pool. Not really migrating at all. Done this a few times with success.

Hi! SDK profiles can only be used in conjunction with apps that have embedded the Airwatch SDK into it. Apps from VMware etc already come ready to apply SDK settings. Microsoft already uses MAM settings from intune, so I doubt they would do this for any of the office Apps.