Forum Discussion
Using EnterpriseExtFileSystem CSP to Deliver File to Windows 10 Mobile Device
I was finally able to get it to work. I changed the .txt file containing the Base64 encoded data to a .bin file and uploaded that under the Base64(File) data type. The file delivered and was converted back to the plain text where the device could read the scanner settings. I would like to thank you for talking this through with me! Much Appreciated!
Are you try to copy/place the file to Windows Device? You can copy/place files using Win32, check this out.
Hope I’m understanding the scenario!
Moe
https://cloudbymoe.com/f/use-intune-to-install-azure-vpn-client-and-import-xml-config-file?blogcategory=Azure+VPN+Client
Hey Moe_Kinani,
I thought exactly the same in the beginning :-), but then I realized he talked about Windows 10 IoT and this one is based on Windows 10 Mobile afaik. Furthermore he explained he succeeded with Airwatch with the CSP and the CSP is only supported/working on Windows 10 Mobile. So a kind of confirmation that it is based on Win10 Mobile then. IME is not working on Windows 10 Mobile, so not an option imho.
best,
Oliver
Yea sorry, the device runs Windows 10 Mobile Enterprise. The device manufacturer (Honeywell) lists the OS as Windows 10 IoT Mobile Enterprise, so it can get confusing at times when trying to describe the device. What I am really trying to do is push down a device scanner profile using the OMA-URI setting ./Vendor/MSFT/EnterpriseExtFileSystem/OEMProfile as described https://docs.microsoft.com/en-us/windows/uwp/devices-sensors/deploy-scanner-profiles-with-mdm It seems that this setting requires that the data be encoded in Base64, but there is no way to chose that as a data type in a custom configuration profile unless you are pushing a certificate. As mentioned before, I have tried inputting the Base64 value using a String data type but that didn't work either.
