Thank you for the post.
"1. What happens to the existing sites if you do install Filemaker Server anyway?"
If existing IIS sites are using ports 80 and 443, then during the installation, a prompt to disable those sites will appear:
"2. Is there any way to restore the existing sites into a running state after the installation either by reconfiguring Filemaker, the existing default site, or through some other means?"
FileMaker Server 13 additionally includes Custom Web Publishing with PHP or XML.
Page 25 of the following guide shows the location FileMaker Server 13 loads the site directory structure:
Lastly, a server operating system is not required for FileMaker Server 13:
Ref TSFalcon's posts. The answer to 1 is correct. Basically the default website gets disabled when installing Filemaker Server. FMServer13 creates a new website called: FMWebSite and it requires access to port 80 (http), 443 (https) and 16000 (for admin console).
However with regard to question 2 - I don't think the links directly address your question.
Basically, when FMServer installs itself, it creates this folder for storing the default website:
C:\Program Files\FileMaker\FileMaker Server\HTTPServer\conf
From there you have a few options:
- The root folder is pretty much empty and you can add a site directly to here which becomes the root folder for your domain
- You can add sub directories or a virtual directory to this folder
- You can edit the web.config file to redirect users to other folders on the server
As such, you can host a single website and domain easily, however I'm not sure about hosting multiple sites, as I'm not that experienced with IIS. My set up is for a single domain running a simple web site within the FMWebSite which uses .php to interact with a Filemaker database running off Server13.
Hope this helps.