| **iOS** |
| Inventory Queries to list device compatibility |
| Compatible Query | Incompatible Query |
| [ios14\_compatible.json](https://kb.filewave.com/attachments/145) | [ios14\_incompatible.json](https://kb.filewave.com/attachments/146) |
| **iOS** |
| Inventory Queries to list device compatibility |
| Compatible Query | Incompatible Query |
| [ios17\_compatible.json](https://kb.filewave.com/attachments/228) | [ios17\_incompatible.json](https://kb.filewave.com/attachments/227) |
| Server FQDN from Preferences | demo.filewave.ch |
| Authorisation Token | e2E1OTU4ZmYyLTg4ZTYtNDEzNC1iZjdhLWE0ZmJmMTViNmI5OH0= |
| "Profile - WLTC wifi" \[File ID of Fileset: 'Profile - WLTC wifi'\] | 780638 |
| iPad001 \[FileWave Device ID\] | 3425 |
| iPad002 \[FileWave Device ID\] | 4342 |
| iPad003 \[FileWave Device ID\] | 3312 |
The above may mean you have hundreds of associations to change...if that is the case, remember that you can mass-edit associations in the Associations view.
# iOS BYOD User Enrollment Overview ## What With Version 14(+) of FileWave, you can now BYOD (bring-your-own-device) enroll a device without giving total management of the device to the system admin. ## When/Why Typically, this option works best if the device to be supported is not company owned. For instance, an employee with their own iPhone may want to BYOD enroll a device to allow distribution of company-owned app licenses, but without giving their company the ability to manage their phone in other ways. ## How BYOD enrollment is off by default in FileWave, and must be enabled on the Mobile tab in preferences as shown below:  Once enabled, a new tab will be added to the "Enroll iOS Device..." Assistant:  And, once user enrollment is enabled, you can go to [https://my.server.address:20443/ios/byod](https://my.server.address:20443/ios/byod) to see the user enrollment page:  Note that by BYOD's very nature the only way you will enroll BYOD devices is through this page. (i.e. it won't be through DEP). BYOD enrollment **does** require the use of managed apple ids from either Apple School, or Apple Business, Manager. See below video of a BYOD device enrollment:Unlike a DEP enrollment, you don't have to wipe the device first to BYOD enroll it. However, trying to enroll a device with a managed Apple ID that is already logged into iCloud on the device will result in an error.
# Managing BYOD User Enrollment ## What You have no doubt gotten used to managing supervised iOS devices, where you have the ability to manage most elements of the device. If you have previously had folks do a manual OTA enrollment, then you know you have less management of those devices than those that are supervised. BYOD user enrolled devices take that a step further, and even fewer capabilities exist (but for good reason). ## When/Why If you are going to utilize BYOD enrollment, it is because the devices to be enrolled actually shouldn't be managed by you, but they should have the ability to leverage the organization's resources. So, with BYOD enrollment, you can distribute VPP apps and licenses: - An important feature provided through the Managed Apple IDs is the deployment of apps and media via VPP - For User Enrollment, FileWave will automatically register and associate VPP users for each associated VPP asset on demand (because the licenses can't be associated to the device) - Configuration profiles, like email settings and VPN settings are supported (to ease customer setup) But there are also restrictions to management: - No access to device-identifying information (e.g. serial number, universal device identifier (UDID), IMEI, or mac addresses) - No access to personal data - No access to personal apps (no taking management or removing) - Limited control capability (no remote wipe, no restrictions, device is not supervised so no profiles requiring supervision) - Not all profiles are supported (profiles that restrict the user are largely not permitted, e.g strict passcode requirements, configurations that proxy network traffic, restrictions that block content) ## How Once the devices are enrolled, associations for content are managed like you are used to, but there is one important (and helpful) change to the way FileWave is managing VPP license assignation. So please make sure and check out the article linked below on VPP License/Association ChangesYou may be saying to yourself: "If I have to assign these licenses to the user, doesn't that mean I'll have to create VPP users in FileWave and invite them?" And the answer to that is thankfully, no. For User Enrollment, FileWave will automatically register and associate VPP users for each associated VPP asset on demand.
# New Inventory Item -- Enrollment Type ## What There are now several methods of enrolling devices into FileWave and a new inventory field has been created to record the enrollment method. ## When/Why This field can be helpful when assigning content to devices. The field in question is called Enrollment Type as you'll see below:  ## How There is nothing special about access the item...you can do it in any query or smart group, but the following are the breakdown of the values for the field:| Displaying information | Description |
| Enrollment via APK | Device was manually enrolled via installation of FileWave application |
| Enrollment via EMM\_API | Device was enrolled via the Android Management API (through NFC or a QRcode) |
| OTA Enrollment | Device was enrolled over-the-air |
| User Enrollment | Device was enrolled BYOD |
| DEP Enrollment | Device was enrolled via Apple DEP |
| Enrollment via fwcld | Device was enrolled via fwcld |
| Enrolled | Enrollment of Chromebook |
| User approved enrollment | Device was enrolled over-the-air and approved by user |
| Presumed DEP Enrollment | Device is supervised iOS client that was enrolled before v14. "Presumed DEP" because there is no absolute concrete criteria to determine if it is DEP or Apple Configurator. |
| Not available | Enrollment type is not determined |
**Self-Signed Certificate** As 3rd party suppliers have been supplying appropriate keys now for some time, this is likely to impact Self-Signed Certificates only.
## Directions The following command may be used to check the certificate RSA key size. macOS, Linux: ```bash openssl x509 -in /usr/local/filewave/certs/server.crt -text -noout | grep Public-Key ``` Windows ```bash C:\OpenSSL-Win64\bin\openssl.exe x509 -in C:\ProgramData\FileWave\FWServer\certs\server.crt -text -noout | FINDSTR Public-Key ``` Windows does not have openssl installed as standard so you will need to go to [https://slproweb.com/products/Win32OpenSSL.html](https://slproweb.com/products/Win32OpenSSL.html) and download the appropriate version of OpenSSL for your environment. If the output is anything less than 2048, then the server certificate will need to be updated. If you are using a Self-Signed Cert, you will need to either: - Re-use your process for generating the certificate to update to ensure it has a RSA key size of 2048 or larger - Consider moving to an official 3rd party certificate Please take into consideration the following KB when moving to a new certificate: [Root Trusted SSL Certificate (Using and Renewing)](https://kb.filewave.com/books/certificates/page/root-trusted-ssl-certificate-using-and-renewing "Root Trusted SSL Certificate (Using and Renewing)") # Customising iOS Wallpaper # Customizing iOS Device Wallpaper with Dynamic Text ## What FileWave v14.10.0 introduced a new feature that allows customisation of wallpaper on iOS devices. This feature enables the additions of wallpaper text and with FileWave's parameters within Profiles, a single generic profile can be used to display Serial Number, Department and Assigned User, simplistically on all devices. ## When/Why Some suggestions of using text with wallpaper include: - Personalizing the device for an organization, department or individual - Identifying a device with its unique Serial Number, which can be helpful in tracking and asset management - Providing additional information that may be useful for the end-user or technical support team - Displaying room names for wall mounted tablets outside meetings rooms, lecture theatres and hospital surgeries. ## How To utilise this feature in FileWave v14.10.0: - Log in to your FileWave console. - Create a new iOS Profile. - Select the **Command Policy** item from the left list of profile types. - In the **Command Policy**, add the desired text, e.g. Department, Telephone Number into the 'Text overlay' box. Note this example demonstrates the use of a parameter to supply the device's Serial Number.  - Save the configuration and apply it to the chosen, targeted iOS devices. It's that simple! Now your iOS devices will have a customized wallpaper that displays the information configured.If the image's aspect ratio doesn't match the device's screen resolution, iOS or iPadOS will resize the image which may lead to portions of the image being cropped. Even where an images resolution matches the screen resolution in one orientation, when rotated between landscape and portrait, this can no longer be the case. The consequence is a resize of the image, also leading to cropped edges. The Text is burnt into the image and as such, if not placed with consideration, could also become cropped. Test the outcome of the image with text in both Portrait and Landscape.
## Digging Deeper Extensive details of image sizes with text placement and its impact is highlighted in: - [Custom iOS Wallpaper Dynamic Text Tips](https://kb.filewave.com/books/ios-ipados/page/custom-ios-wallpaper-dynamic-text-tips) Referencing parameters within all profiles (which can now be used to personalise the text on the wallpaper since FileWave v14.10.0) is also described in: - [Using parameters in iOS/macOS Profiles](https://kb.filewave.com/books/profiles-apple/page/using-variables-in-apple-iosmacos-profiles "Using variables in Apple iOS/macOS Profiles") # Custom iOS Wallpaper Dynamic Text Tips ## What Consideration of the size and where to place the text being added to an Apple mobile device's Wallpaper. ## When/Why When adding text, there are 3 Font size options, plus 9 possible locations for placing text. Note, the preview is portrait, but this is not necessarily how the image will appear on the device. [](https://kb.filewave.com/uploads/images/gallery/2023-09/s7LQ6yFcn951Ptgi-image.png) The Font used is [GothicA1-Regular](https://fonts.google.com/specimen/Gothic+A1) and the sizes refer to:| SMALL | MEDIUM | BIG | |
| FONT SIZE | 65 | 80 | 95 |
Image uploaded to FileWave must be smaller than 2MB to add text, to help protect against undue heavy load on the server.
## How Consider the devices currently managed. An image of the correct size should be required for each different device screen aspect ratio. Unfortunately, MDM cannot retrieve screen resolution from devices, but each device type resolution can be observed at the following: [https://www.ios-resolution.com/](https://www.ios-resolution.com/) Alternatively, a tool like [Mactracker](https://mactracker.ca) lists details for all Apple device types. ### Smart Groups Since a Wallpaper Profile Command Policy will be required for each screen resolution, devices need to be targeted appropriately. Consider the following method: Obtain the Product Name for a device type to be managed (e.g. iPad6,11). Cross reference this with something like Mactracker to obtain details. - Create a New Smart Group - Type: Inventory Query - Criteria: Product Name > is > iPad6,11 - Group Name: (Something obvious)It may be sensible to include the screen resolution as part of the group name, but not use the Product Name. There is overlap with device types and resolution. E.g. both 'iPad 6th Gen' and 'iPad mini 5th Gen' have a resolution of 2048x1536, so one group could be used to target both device types. Example group name: iOS 2048x1536
Example of multiple device types for the Smart Group which all share the same resolution. Note the 'one or more expressions must be true' and the 'Main Component': [](https://kb.filewave.com/uploads/images/gallery/2023-09/jUbJ4sjWFdtJEDN5-image.png) Copy the above process for each required resolution. ### Image Preparation Although there is an options to set the colour of text, complex images may hinder the visibility of the text. Image levels could be altered before uploading to FileWave. However, wouldn't it be better to test this first. Additionally, text position can be of consequence, since devices may be rotated between portrait and landscape and the image will adjust accordingly. This will have the appearance of a cropped image, either at the sides or top and bottom, which in turn could crop the text. Before commencing, download the Font and use [Font Book to add the Font.](https://support.apple.com/en-gb/guide/font-book/fntbk1000/mac) The following walkthrough should help assist with pre-planning the image and text visibility. Taking the above 2048x1536 as an example. The chosen starting image is: [](https://kb.filewave.com/uploads/images/gallery/2023-09/mMnuSnprOhfJkTWq-image.png) Note this image is currently the wrong resolution. Preview.app can be used to address this landscape image: 1. Open the image in Preview 2. Proportionally alter the height (which is currently too small) to match the height (y value in this example) of the device's screen resolution with the Adjust Size Tool. The image is now oversized, but will more than fill the entire screen in one axis and match in the other. (In this example, the height should now be 1536 and the width greater than 2048) 3. Zoom out so the entire image may be viewed 4. Select All 5. Move one of the sliders of the selection area, in this example left or right, until it reads 2048. 6. The selection can then be moved to the desired area [](https://kb.filewave.com/uploads/images/gallery/2023-09/Szc4WNETJv298di5-image.png) Copy this selection, open into a new Preview window and save. Add an outline: 1. Alter the size of this new image, such that the smaller axis is set to match the larger. In this case alter 1536 to 2048 2. There will now be an image that is 2732x2048. Make a note of these values and undo. 3. Open Keynote 4. Select the Document button and alter the Document Slide Size to match this newly observed resolution: 2732x2048 5. From a blank slide, add a rectangle and remove the colour fill 6. Add a border line to the rectangle, choosing an obvious colour (for example bright green) and 5pt width should suffice 7. Alter the size of this rectangle, such that it matches the reverse dimensions of the device: 1536x2048 8. Centre the rectangle within the slide 9. Copy the rectangle 10. Alter the size of the new copied rectangle to match the resolution of the entire slide and centre: 2732x2048 11. [Edit the Master Slide](https://support.apple.com/en-gb/guide/keynote/tan7a2b69972/mac) so that it has no background 12. Export the slide as a PNG with transparent background 13. Open the exported image into Preview 14. Resize the image, matching the resolution back to the target resolution, in this case: 2048x1536 15. Select All from Preview and Copy 16. Back in Keynote, create a new document and alter the slide size to the desired screen resolution: 2048x1536 17. Add the desired matching sized image to the slide, in this case the 2048x1536 FileWave building image 18. Paste the copied green boxes from Preview over the top In Keynote there should now be an image, including the green inserted boxes, something like: [](https://kb.filewave.com/uploads/images/gallery/2023-09/Qlmb68bV1kYEC90m-2048-2-green-boxes-002.jpeg)Since the green lines forming the boxes have a transparent background, the image behind may be altered, simplifying the testing of differing images.
Consider duplicating slides to test alternate images, in case the desire to revert is experienced!
### Test Text Keynote may now be used to test adding some text. - Add a text box - Set the Font as Gothic A1 Regular and a desired Font size, e.g. 80 - Select a colour for the Font - Add the chosen text, ensuring it does not cross over the lines when centred If the text does cross the lines, the smaller Font size of 65 could be chosen or reduce the amount of included characters.If using variables, confirm the longest value from FileWave and then test with that value as text in Keynote
From Keynote, if the text is unclear, it is easier to adjust the text colour or even make adjustments with the image itself, to enhance the appearance of the text.
Once happy, copy the line of text. ### Create Fileset Remove the text from the Keynote slide and save the slide as an image, using JPG (smaller size). Remember, the image to be uploaded needs to be less than 2MB. Open up the Profile Editor in FileWave and search for Wallpaper, it should be located in the Command Policy. As per the directions in the prior KB article, choose the image just saved as the Wallpaper and paste the desired text into the text box. Clearly, alter the text to include any parameters if necessary. Don't forget to set the Font colour. As per this example, the middle position is going to be chosen. Save the profile and consider including the screen resolution as part of the name: [](https://kb.filewave.com/uploads/images/gallery/2023-09/79bUT7dUS1Nbzs1X-image.png) ### Test Associate the Profile to a test device and Update Model, observing the Command History. The IntsallProfile command should appear and then disappear; this is not a permanent profile, but a one off command. However, the Settings command will persist. Further details in the following KB: [Profile Editor Command Policy](https://kb.filewave.com/books/profiles-apple/page/profile-editor-command-policy) Turn the screen to confirm the look for both Portrait and Landscape. ##### Portrait [](https://kb.filewave.com/uploads/images/gallery/2023-09/PGXtwASlyecVzKkN-portrait.jpg) ##### Landscape [](https://kb.filewave.com/uploads/images/gallery/2023-09/qATkxPmmoDp65SU1-landscape.jpg) ### Additional Info First, it is worth observing how Apple alter an image when the device is rotated between Landscape and Portrait. Apple avoid having black bars around the image. As such, to alter the image, as can be seen above, The smaller, un-matching aspect is resized to match the size of the device's resolution. The impact of this is that the large matching aspect is now oversized and the overall effect is the image appears cropped. The green lines from the image above show the crop position that will be seen in portrait when the device is turned from landscape. This has a consequence with the text. If the text position were bottom right instead, for example, the green box shows the text that would be lost: ##### Landscape [](https://kb.filewave.com/uploads/images/gallery/2023-09/X1eQaHXdXPgcrYt9-landscape-br.jpg) ##### Portrait Indeed, rotating the device into portrait shows the loss of text: [](https://kb.filewave.com/uploads/images/gallery/2023-09/5a58961Mvpj8pLxf-portrait-br.jpg) With this in mind, best practice would be: - Where devices may be rotated - For a landscape image, only ever consider using Middle, Top Middle or Bottom Middle - For a portrait image, only ever consider using Middle, Left Middle or Right Middle - Where devices will not be rotated - Any position could be chosen Apple do not provide an option to prevent rotation, however, in some circumstances devices will not be rotated, e.g. wall mounted outside meeting rooms, lecture theatres, hospitals, etc. ### Conclusion Why use the profile, since the above has just made an image of the correct size and Keynote could have just added the text? This is indeed a good question and the above is to assist with a guide on building out the image, ensuring that the text will display clearly and not be cropped on the image size. Chances are once you have done this for one resolution, that you need not bother for others and will already be armed with a good approximate example. However, the Profile still comes into its own! The Profile can use parameters from FileWave, customising the text per device, based either upon built-in inventory or Custom Fields. This greatly exceeds the above method and is very much the beauty of this feature.