Windows 10: XML file for Kiosk with directory access or network drive or letter

Hi thereI tried to offer a limited experience to read only PDF file for one user. I used assigned access Kiosk. To create XML file as example under this message, I don't success to authorize to access on the directory P:Is anyone succeed to work with this functionality ? How to do this ?Thanks.

:)

 

Network Mapped drive is not accessible with Drive letter but accessible via UNC path through application

Issue: Applications are unable to access the files using network mapped drive letter but accessible using UNC Path

Azure VM

Windows Server 2022 Datacenter Azure Edition

Created a file share from Azure storage and mounted as network drive in Azure VM (using windows PowerShell command provided in Azure).

We are able to access the files via network mapped drive letter from VM (while we use RDP) and also through command prompt inside VM.

Applications are unable to access the files using network mapped drive letter. But applications are able to access by using full UNC path.

Kindly let me know what needs to be done to access using drive letters (Network mapped drive letters).

 

How to allow Windows 10 multi-app kiosk mode to run program from network drive

I'm experimenting with Windows 10 multi-app kiosk mode as a possible solution for some public kiosk terminals, and I've gotten the XML file written in a way that everything works perfectly after applying the provisioning package.

Almost.

The provisioning works fine if I do not add the paths of our specific software under "AllowedApps" and leave it as simply a list of basic Windows apps like File Explorer, Google Chrome, etc.

As soon as I add the paths to the proprietary apps though, the newly built provisioning file fails to make any changes to the computer at all.

The apps (desktop apps, not UWP) that need to load are located on a server in the same LAN and must be loaded via a network share. They cannot be installed locally on the kiosk computer.

So I've pinpointed the problem being that the kiosk mode doesn't seem to like allowing apps that are located on a network drive.

I'll appreciate any kind of pointers on how to get around this. Is it a known limitation of kiosk mode? And if so, is there an unofficial workaround I can do to "trick" it into allowing specific desktop apps to load from a network drive that are not and cannot be installed on the local kiosk computer?

I'm really liking the kiosk mode, but unfortunately the whole point of using it would be to run apps that can only be loaded from a network drive.

Here's the different ways I tried writing the network paths for the programs, none of which worked:

<App DesktopAppPath="Z:\\[RemotePC]\[ShareName]\[FolderInShare]\[ServerApplication].exe" />

<App DesktopAppPath="\\[RemotePC]\[ShareName]\[FolderInShare]\[ServerApplication].exe" />

<App DesktopAppPath="Z:\[FolderInShare]\[ServerApplication].exe" />

 

cannot open files on network shared drive

Some application need both read and write permission to access their file.
I don't have any knowledge of your application. Usually if you can access that file and copy it to you networked pc should be enough.
I would add write permission and try it again.
Perhaps in the software your using, you need to set a target drive letter for the application data. Some applications can be poorly written and expect the data to come from either a C Drive or D Drive etc.
Firewall permission, network permission, application data target folder. Let us know how your going.