Todd's Tips for System Adminstrators
At some point, someone had to create the Simpson’s opening in real life. Well that some point has finally arrived. Check out the Live Action version of the Simpson’s opening. I will say it looks really well.
You can find the video at the top of the page at http://www.itsnicethat.com/articles/come-home-to-the-simpsons. Here’s a still picture from the video, it looks great.
Enjoy
If you have deployed Office 365 or are planning to and are looking to publish your ADFS to external users, for example, workers from a remote location like Starbucks or for mobile devices then you have a couple of choices.
You can chose to deploy an ADFS proxy. This is pretty simple and is really just a role service of ADFS.
Instructions on how to setup ADFS can be found on Kelsey Epp’s blog.
The one drawback of using ADFS Proxy is that you can’t logon to Office365 if the Active Directory (AD) account is expired or has been marked “User Must Change Password on Next Logon” If you have a lot of users who are using a web browser or mobile devices and they don’t come into the office much, this could be a problem.
The alternative is to use Microsoft Forefront Threat Management Gateway 2010. The drawback here is the product is being slated for retirement and it has a cost. But with it you can have users directed to a page where they can reset the password if it is expired. The link to set up TMG for ADFS.
Following these instructions for TMG 2010 I did run into an issue where I was getting error 8004789A. The issue was I had to uncheck Link Translation. I found this on Risual Blogs.
I am hoping over the next little bit that we will see Microsoft give us something that will allow us to change passwords remotely like TMG but make it free like ADFS Proxy.
I was playing with a security plugin for WordPress and everything came up fine except for a warning that .htaccess was missing from the wp-admin folder. Fine, its not there, but what the heck do you put in it.
I did a search for this error and found lots of people asking the same question. I did find one solution and thought I would share it.
Basically create a .htaccess file with these parameters:
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress
Save and it upload it into the wp-admin folder. You should be good as far as clearing that error up.