II. Management: Powershell

  1. Set-up
    1. Run Powershell as admin
    2. Import-Module WebAdministration
      1. Required to run IIS commandlets inside powershell
    3. IIS:
      1. Powershell treats IIS as a drive letter
    4. Dir
      1. Will list three directories: AppPools, Sites, SslBindings
    5. IIS
      1. Typing IIS at the powershell prompt will open IIS GUI
  2. Adding a new site (with and without www header)
    1. Import-Module WebAdministration
    2. IIS:
    3. New-Item iis:\Sites\SiteName.com -bindings
      1. @{protocol="http";bindingInformation="*:80:SiteName.com"}
      2. physicalPath C:\inetpub\SiteName.com [PubMed]
    4. New-ItemProperty iis:\Sites\SiteName.com -namebindings -value
      1. @{protocol="http";bindingInformation="*:80:www.SiteName.com"}

III. Management: FTP File Transfer Setup

  1. Background
    1. FTP Publishing is an older, but simpler method for site maintenance related file uploads
    2. Distinguish from creating an FTP server where users can upload files to a site (that is another process)
    3. Alternatively, Filezilla can be installed on the server (my preferred option)
  2. Enable FTP services
    1. Open Services
    2. Find Microsoft FTP Services and enable, Automatic
    3. Start the FTP Service
  3. Enable FTP Publishing for the web site
    1. Right click on the web site name (e.g. Default Web Site) in IIS Connections panel
    2. Choose FTP Publishing
    3. Enter a Binding IP Address (typically the same site IP Address), and keep the port set to 21
    4. Choose "Require SSL" and select the SSL Certificate to use
    5. Choose "Basic Authentication"
    6. Choose "Allow Access" to a user or group (e.g. Administrators)
    7. Set Permissions (read, write)
  4. Connect using FTP client (e.g. FTP Voyager, Filezilla)
    1. Enter the IP, username and password
    2. Select use SSL

IV. Management: Troubleshooting

  1. Worker Processes
    1. Allows for identifying slow pages
    2. Available from the root IIS directory
    3. Lists Running worker processes on the web server
      1. Double-clicking on a process displays all requests within that process Running >1 second
      2. Each request demonstrates file, verb, client IP, state and time elapsed
  2. Failed Request Tracing
    1. Allows for logging errors to files
    2. Available from the IIS site
    3. Add rules on failed requests to capture (e.g. requests lasting longer than 30 sec or status code 500)
    4. Click "Edit Website Failed Tracing" to enable the traces and set the maximum number of tracing files
    5. When data collected, click "View Trace Files"
  3. LogParser and LogParser Studio
    1. Allows for a SQL-like query of data in the IIS logs
    2. Download and install LogParser (complete version)
    3. Download and extract LogParser studio (I put in c:\inetpub\logs\logparserstudio)

V. References

  1. Evans (2011) IIS for Developers, Pluralsight
  2. Schaefer (2014) Professional Microsoft IIS 8, Wrox

Images: Related links to external sites (from Bing)

Related Studies (from Trip Database) Open in New Window