[0] says "In a Windows guest, you must then install spice-webdavd service, and register the drive (by running map-drive.bat from Program Files/Spice webdav)."
Imo this script should ship with spice-webdavd, not with vdagent-win

(In reply to Christophe Fergeau from comment #1)
> [0] says "In a Windows guest, you must then install spice-webdavd service,
> and register the drive (by running map-drive.bat from Program Files/Spice
> webdav)."
> Imo this script should ship with spice-webdavd, not with vdagent-win

Indeed. I've tested last week with Lukas and it seems better to do on spice-webdavd. He is currently working on this.

I managed to duplicate the script programatically in webdavd, but there are some issues.

Currently the biggest issue is that there is no way to disconnect the drive. This is because of mainly 2 reasons.
1. If we map the drive using the service, then user can't disconnect it manually
   This is most likely, because the service has SYSTEM privileges.
2. webdavd doesn't notice when we close the channel (turn of sharing)
   Because of this, we can't disconnect the drive in webdavd itself.
   This is most likely Windows issue.

Proposed fix is making it so that webdavd tries to find already connected drive on start, and if found, won't try to connect to it again.
On exit, webdavd will then disconnect the drive.

I propose that vd_agent could have aditional protocol for sending information whether sharing is enabled to the guest.
After enabling the sharing, vd_agent would start webdavd, which would map the drive.
After disabling sharing, vd_agent would stop the webdavd service, which would the unmap the drive.

This way the drive is always connected.

Automounting is done by phodav: https://git.gnome.org/browse/phodav/commit/?id=13151735cb97bc4e95deb72597c1024d139504e3