-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS App Configuration #260
Comments
Hello, Did you try the attached file from #255? I attached it in this one as well. This should fix the Android problem. You will have to export the policy using the attached file as well since this adds additional information to the exported file. I probably have to do the same for the iOS policies with apps deployed via VPP. Not sure if I can detect that but should be possible one or the other. Can you upload the iOS policy so I can have a look? Or can you create a dummy iOS policy with Outlook from VPP. Cheers! |
Hi Confirmed, the updated EndpointManager.psm1 works perfectly for Android, thanks! Exported iOS policy with the VPP Outlook selected as below. |
Hello, Thank you for the update. Did you try importing the iOS policy with the new file? The policy you attached includes the new required property so it could work. Unless I only use the property on Android imports. Cheers! |
iOS still imports, but the policy shows "The targeted app no longer exists. You can delete this inactive app configuration policy." |
Hmm, ok. I'll try to spend some time on it on the weekend. Cheers! |
Thanks! |
Hello, I'm going through the code. Looks like it should work so not sure what is happing there. Can you send the logs of the import? There might be some hints in there. Cheers! |
Hi, The "console" output shows
CloudAPIPowerShellManagement.log as below (with some names and paths lightly obfuscated (to remove user and tenant names etc). CloudAPIPowerShellManagement.log Quite happy to provide unobfuscated via email, but would be difficult in a public GitHub issue. Looking at the CloudAPIPowerShellManagement.log, While I'm quite sure it is "cosmetic" the OS detection is incorrect, while it says "OS: Windows 10 Enterprise multi-session" it is a W11 AVD. |
For the OS version, the post from OlivTheFrog might be an alternative to lines 95-98 in core.psm1 (dropping the specific comparison that was in the post) |
Thank you for that. I might convert it to Get-ComputerInfo instead oof reading the registry. The interesting part though is this:
It uses this code to find the app.
So this will look for an app with the same name. It then filters the result based on object type. In this case: "#microsoft.graph.iosStoreApp". Based on the code and the error message, this means that it found at least one app with the name but none of the app(s) found was the requested type. What type is the "Microsoft Outlook" deployed via VPP in the second tenant? View the app info in the tool and then check the @OData.Type property. Also, when you are in the View dialog, click "Load full" and see if the OData.Type changes. Cheers! |
I also found that the code should not add this information for iOS Configuration policies. This is the if statement to add the #CustomRefTargetedApps property.
I have no clue how the property ended up in the json file. I created a new file that will add the #CustomRefTargetedApps property for iosMobileAppConfiguration as well during export. You can PM me on twitter if you have an account there, @Micke_K_72. We might be able to solve this with the additional logging. I hope it will give some hints on what is going on. Cheers! Cheers! |
re Outlook application type In the tool under Applications, I see two entries for "Microsoft Outlook" one is the iOS version, and the other is (by simple elimination) Android, but if I do an export from the tenant, only the Android one has a .json file, I wonder if this is because they both have the same name, and the iOS export happens before the Android export, which then overwrites? Checking a different (iOS only) app, the .json shows
I will try with the new one (-: I do not appear to be able to message you on X, but you should be able to DM me (I @ed you in a post) |
Apologies, what I should have done is export just that Application... I've removed the date for "largeIcon", and mildly obfuscated vppTokenOrganizationName and vppTokenAppleId, but otherwise is as below |
The json for the app says the type is: #microsoft.graph.iosVppApp That is not what it says in the exported policy file. That's probably why it is failing. So the question is then if it has different app type between list and full object API. Still don't understand how the property got there unless it was by an earlier version I created that didn't have the if statement. At least we're getting somewhere with this and have some idea what the problem is. Let's see what it says with the new file. Export the policy again and then retry import in new tenant. Then upload the import part of the log. Thanks for the help troubleshooting this. Cheers! |
If that doesn't work, try this one. Just a quick change that might cause it. Cheers! |
/me is an idiot After seeing again in your post above that the export did not show microsoft.graph.iosVppApp, although I was sure that the App Configuration Profile was for the VPP version, on deleting it and the App Store version version of Outlook, then recreating so that it could only be against the app store version, the import worked... many apologies for wasting your time. |
No need to be sorry! Thank you for helping with testing and troubleshooting the iOS policy. It was definitely not a waste of time. Cheers! |
I see an issue with iOS App Configuration (currently running release 3.9.7)
The "template" (what I export from) and "destination" (where I deploy to) both have the same app (Outlook) deployed via VPP (Volume Purchase Program) for iOS and via Google Managed Play Store for Android (both source and destination using the US store).
With iOS
The policy is exported and deployed, but shows "The targeted app no longer exists. You can delete this inactive app configuration policy." and none of the settings are able to be edited, the only option is to delete.
With Android
The policy is not deployed
Log message shows the below (I have deleted the Request ID and the Activity ID)
I've found the below that look as if they might be related.
#231
#255
As an aside from #231 "anyone" can sign up for Google Enterprise for Intune App deployment, just go to https://intune.microsoft.com/#view/Microsoft_Intune_DeviceSettings/DevicesMenu/~/enrollment > Android > Managed Google Play, complete the enrollment (can use Tenant domain email address) and then Managed Google Play apps can be added in Intune.
The text was updated successfully, but these errors were encountered: