Windows Server 2012 – Install and Configure an FTP Server
KB ID 0000847 Problem FTP might be an ages old solution for moving files around, but a lot of people swear by it. With Windows Server it’s still supported, even if it is hidden as a ‘role service’. Solution Create a Security Group For Domain FTP Access Note: For a Standalone/Workgroup server see below for setting up users and groups. 1. Launch Server Manager > Tools > Active Directory Administrative Center. 2....
Windows Server – Installing IIS and PHP
KB ID 0000879 Problem What used to be a complicated task has been simplified greatly by the Microsoft Web Platform installer, the process of adding PHP is the same for Windows 8,(though to install IIS you need to enable that as a windows feature (run appwiz.cpl > Turn Windows feature on or off). Solution 1. From Server Manager (ServerManager.exe) > Manage > Add Roles and Features > Follow the wizard and in the Server Roles...
Server 2012 – Certificate Services – ‘HTTP Error 403.14 – Forbidden’
KB ID 0001067 Problem I spun up a new Certificate Services server on my test network today, because I needed to issue some certificates for something I’m working on. It was a pretty vanilla build, just the Certificate Services role, and the Web Enrollment feature. Solution I spent a while searching this one down, as you can see (above) it was showing me the root cause of the problem. The page you normally see when you log into...
Install and Configure Remote Desktop Services (Web Access)
KB ID 0000104 Problem Originally we had TS Web in 2003, and while I had a little play with it, it basically just gave you RDP over web, which would have been good if it ran over HTTP or HTTPS, but it didn’t. Also, as anyone who has ever done a complex Google search for “/tsweb” will testify, left a nice big security hole in to your servers. With the release of Server 2008 we got TSWeb 2008, this was a whole different...
IIS – ‘This Web site cannot be started. Another Web site may be using the same port’.
KB ID 0000660 Problem After being unable to access my Exchange Management console, it turns out the default website had stopped. When I attempted to start it I was greeted with this error. Solution 1. Nothing was using the usual web ports (80 and 443) which I found out by running the following two commands; netstat -aon | find “:80″</p> <p>netstat -aon | find “:443” Note: If you do have a process...