Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Error rendering macro 'excerpt-include' : No link could be created for 'Almirah Knowledgebase'.

Whilst Almirah is a cloud-based appliance local versions of the documents can be kept on the physical LAN. This article explains how to set up a local site.

Background

IIS is one of the Windows Server® server roles. IIS can be installed through the graphical user interface (GUI) by using the new Server Manager interface after the Windows Server operating system is installed.

Server Manager provides a single dashboard to install or uninstall server roles and features. Server Manager also gives an overview of all currently installed roles and features. When IIS is chosen from the Server Manager, the basic components and services needed for IIS are automatically selected.

Before You Begin

Ensure that you have administrative user rights on the computer on which you plan to install IIS 7.5 or above. Note that by default, you do not have administrative user rights if you are logged on as a user other than as the built-in administrator, even if you were added to the local Administrators group on the computer (this is a new security feature in Windows Server 2008 called Local User Administrator).

Log on either to the built-in administrator account, or explicitly invoke applications as the built-in administrator by using the runas command-line tool.

Note: You can run runas /user:administrator cmd.exe so that every application you run from that command line will be elevated, eliminating the need to use the runas syntax from that command line.

If you are logged on to an account other than the built-in local administrator account, you may see the following security alert dialog box.

Figure 1: Windows® Security (User Account Control)

Prerequisites

  • Local Document Site Setup

  • Create a Service Account that the IIS Proxy will use. It must have permissions of Full Access (Read and Write Access) to the 'Published' and 'Version Control' Locations

  • Assign staff to Read Only access to the 'Published Version' Location.

  • Assign staff No access to the Version Control Location 

  • No labels