II. Precautions: Non-Medical
- Not for Medical Care
- The author uses several software packages and programming languages to develop FPnotebook content
- For convenience, a dozen pages in FPNotebook are dedicated to quick notes on content creation
III. Management: Powershell
- Set-up
- Run Powershell as admin
- Import-Module WebAdministration
- Required to run IIS commandlets inside powershell
- IIS:
- Powershell treats IIS as a drive letter
- Dir
- Will list three directories: AppPools, Sites, SslBindings
- IIS
- Typing IIS at the powershell prompt will open IIS GUI
- Adding a new site (with and without www header)
- Import-Module WebAdministration
- IIS:
- New-Item iis:\Sites\SiteName.com -bindings
- @{protocol="http";bindingInformation="*:80:SiteName.com"}
- physicalPath C:\inetpub\SiteName.com [PubMed]
- New-ItemProperty iis:\Sites\SiteName.com -namebindings -value
- @{protocol="http";bindingInformation="*:80:www.SiteName.com"}
IV. Management: FTP File Transfer Setup
- Background
- FTP Publishing is an older, but simpler method for site maintenance related file uploads
- Distinguish from creating an FTP server where users can upload files to a site (that is another process)
- Alternatively, Filezilla can be installed on the server (my preferred option)
- Enable FTP services
- Open Services
- Find Microsoft FTP Services and enable, Automatic
- Start the FTP Service
- Enable FTP Publishing for the web site
- Right click on the web site name (e.g. Default Web Site) in IIS Connections panel
- Choose FTP Publishing
- Enter a Binding IP Address (typically the same site IP Address), and keep the port set to 21
- Choose "Require SSL" and select the SSL Certificate to use
- Choose "Basic Authentication"
- Choose "Allow Access" to a user or group (e.g. Administrators)
- Set Permissions (read, write)
- Connect using FTP client (e.g. FTP Voyager, Filezilla)
- Enter the IP, username and password
- Select use SSL
V. Management: Troubleshooting
- Worker Processes
- Failed Request Tracing
- Allows for logging errors to files
- Available from the IIS site
- Add rules on failed requests to capture (e.g. requests lasting longer than 30 sec or status code 500)
- Click "Edit Website Failed Tracing" to enable the traces and set the maximum number of tracing files
- When data collected, click "View Trace Files"
- LogParser and LogParser Studio
- Allows for a SQL-like query of data in the IIS logs
- Download and install LogParser (complete version)
- Download and extract LogParser studio (I put in c:\inetpub\logs\logparserstudio)
VI. References
- Evans (2011) IIS for Developers, Pluralsight
- Schaefer (2014) Professional Microsoft IIS 8, Wrox