Staff.Wiki Professional (also known as Standard or Enterprise on-premise) comes with an embedded test web server to makes it easy to get started. However this web server, while capable of serving a small number of users, lacks the sophisticated functionality of a professional web server. To use features such as unattended operation, web farms, secure sockets and certificates, to name just a few, you will need to use Staff.Wiki Professional with Microsoft Internet Information Server, which comes with Windows Server.

Note: Staff.Wiki allows you to set up any number of separate databases by creating multiple sites in IIS and modifying the sqlserver.cfg to have it use a different database.

To make the transition easier, Staff.Wiki's folder structure reflects the structure required by Microsoft IIS. After copying these files in, you will simply need to point IIS to the application folder. You will also need to enable ASP.Net, enable 32 bit (under the setting 'Enable 32 bit') in the Application Pool settings, and make sure Managed Pipeline is set to Integrated (as of v5.1)..

The ZIP file will contain a web.config file with some special entries.

You can follow these steps to add the application to IIS:

1. Locate the folder where your Staff.Wiki Professional is installed. (we'll assume the folder is called StaffWiki)
2. Add a new Application Pool
   1. The name should be the name of the app (eg. StaffWiki)
   2. Set to Integrated (NOT Classic)
   3. Set CLR version to be v4
   4. Go to its Advanced Settings, and set “Enable 32bit” to True.
   5. Check the "Identity" setting to set the account to run the server under. It may be simpler to set this to "Local System", at least to start with. See below.
3. Add a new site
   1. The name should be the name of the app (eg. StaffWiki)
   2. Select the Application Pool you just created
   3. Set the Physical Path to be the StaffWiki folder
   4. Set the binding as required (usually port 80, unless you have an SSL certificate)

You should then be able to visit the website to check if it's running. 

Note: To enable HTTPS (SSL) on your IIS site, you will need to acquire an SSL certificate from a third party.

This may be a good time to determine if you want to support large file uploads (which is disabled in IIS by default). Please see this note for details.

Application Pool Identity

The account to run the Application Pool under may be set to Local System initially to help with getting everything set up, however it would be better to instead use a more restricted account. The account must have, at a minimum:

• Read/Write access to the local machine registry section.
• Read/Write access to the installation folder and sub-folders.
• Read/Write access to the Windows temp folder.
• Internet access to the on.staff.wiki and workflowfirst.com server, for licensing verification.
• Suitable SQL Server permissions (if connecting to SQL Server with the same user credentials). This will include db_owner permissions - the ability to create databases, create tables and so on.