Web Client Installation in RDP environment

Currently I have 20 users or so using a App server with a full installation of Sage installed, financial and operating suite accessing sage as published app from the RDP server.  I want to start to move users over to web client.  the IT people do not want IIS installed on their RDP server.   ISS is already operational on their SQL server.

My question is:

- do i need to run a full Sage 300 install on SQL with the Web client or will a workstation install be sufficient

- for troubleshooting reasons I would prefer to run a full install but when it comes to shared data location it would be an UNC path.  Previously when working with the Web client i was warned not to use UNC is that still an issue

- could I run a full sage 300 install on the SQL server and have a different shared location (accepting that users ism files would be new/different when launching sage from the web client or classic client from this server . . . . it's primarily for troubleshooting a random hang issue I am having with print preview on custom forms from OE.