The Internet Explorer Enhanced Security Configuration (IE ESC) that is turned on by default on Windows Server drives me crazy. Being unable to download files, and constantly being prompted to add URLs to be viewed, is super-annoying. So, my SOP now is to disable that setting for Administrative users on servers (note: these are generally test servers that I use; consult your overall security policy before disabling this feature.)
So, how do you turn off IE ESC? First open the Server Manager then click on Local Server. Once there you can see IE Enhanced Security Configuration shown, but if you are like me, you may have missed that there is more content to the right of the screen. So to actually control this setting, scroll to the right:
Click where it currently (by default) shows “on”:
Then just select the Off radio button and “OK” to turn off the feature.
Now close Server Manager and restart any browser sessions that you might have open. Life is now so much easier for you to administer the server and obtain files that may be needed to complete your custom configuration.
Brad on Google+
The new R2 release of Windows Server 2012 makes it just a little trickier to power-down a server. Here are the steps with screen-shots showing how it’s done.
First click on the Windows image in the bottom left-hand corner of the screen:
You then seen the new “start” screen:
What isn’t obvious at this point is that if you now move your mouse, some icons show up along the right side of the screen, AND a little minus-sign shows up in the bottom right-hand corner of the screen:
DON’T click the minus sign because that will just shrink the screen tiles. Hover above it then move your mouse up to the Settings icon (looks like a gear):
That Settings icon brings up more options, one of which is Power. Clicking on Power then gives you the option to Shut down the server or Restart it.
I hope this saves you all the time I spent clicking everything in sight looking for an option to power down my machine.
Brad on Google+
Below is a guest post by Desiree at OrcsWeb with an IIS/PHP/CGI troubleshooting tip:
I installed WordPress for one of our managed clients recently, and what should have been a simple install, turned into quite a bit of troubleshooting. The client was running Windows Server and using IIS for their site hosting. Before starting the WordPress install I confirmed that the server showed PHP was previously installed and configured.
After the install, the site wouldn’t load and returned the error below:
HTTP Error 500.21 - Internal Server Error
Handler "PHP54_via_FastCGI" has a bad module "FastCgiModule" in its module list
Detailed Error Information
Module IIS Web Core
Error Code 0x8007000d
Requested URL http://test.domain.com
Physical Path C:\Data\test.domain.com\wp-admin\setup-config.php
Logon Method Anonymous
Logon User Anonymous
Failed Request Tracing Log Directory C:\inetpub\logs\FailedReqLogFiles
The problem is that the error isn’t very clear. After some troubleshooting and research I figured that to resolve the issue I would need to either install CGI or remove and then reinstall CGI. The server showed that CGI was already installed, but perhaps it wasn’t installed properly? As part of continued troubleshooting, I removed and then reinstalled CGI. The application still didn’t work and was now showing the following error:
If this happens, it is because the removal of CGI removes the registration in PHP Manager. In IIS, open PHP Manager. Click on “Register new PHP version” task and then provide the full path to the location of the main PHP executable file: php-cgi.exe (i.e., C:\Program Files (x86)\PHP\v5.4\php-cgi.exe).
After those changes, we reloaded the site and everything worked properly.
If you run into a similar issue getting PHP and CGI (and perhaps specifically WordPress) working on your IIS server, I hope this helps!
These are some of the most popular posts on my site so I figured I’d put them into a single link making it easy to find and deal with them together.
People are generally interested in sending email via ASP.NET code (the first post) but then they stumble on the examples because they don’t have SMTP installed (the second post) and afterward they stumble one more time because the security settings aren’t set to allow local relay (the third and past post).
Sending email from ASP.Net 4 – C# sample code
Installing the Microsoft IIS SMTP Service on Windows Server 2008
Configuring Microsoft’s SMTP Service to allow relay
Happy hosting (and coding!)
Are you or one of your users getting the following error when trying to execute a sudo command?
[username] is not in the sudoers file. This incident will be reported
Here is how to fix that problem (*see note). As root type:
echo '[username] ALL=(ALL) ALL' >> /etc/sudoers
Obviously substitute [username] with your actual username.
*NOTE: Not every user on your system should be part of the sudoers group. Be sure you are following best security practices, and practices specific for your systems, before deciding whether to add someone to the sudoers group or not.