One of the most useful features in Windows 7 is Libraries. Unfortunately, it is also one of the most painful to administer in a domain. In an ideal world you'd be able to use Group Policy to add or remove whatever library locations you desired. However Microsoft seems to have forgot about Libraries when they updated Group Policy for Server 2008 R2 and Windows 7 as there is no Group Policy to control Libraries.
Just got my new dock a few days ago and decided to post some pictures and write a quick review since when I was looking to purchase it I couldn't find much info online.
I just spent several hours attempting to get PEAR installed into my EasyPHP distribution (EasyPHP is my current choice for a Windows Apache MySQL PHP development server). For whatever reason it was a complete mess to get working. In this post I'll list some of the problems I had as well as some workarounds (not necessarily solutions) that allowed me to get PEAR up and running.
Just thought I'd post some quick notes on doing a Windows 7 reinstall on my Lenovo W520. I'll go over some useful tools and some frustrating problems I encountered and how to avoid them.
I'll also list some really useful tools that should make your reinstall much easier regardless of what type of computer you have.
A few of the Drupal sites I administer use the i18n module to server content in multiple languages on separate subdomains (example.com for English, cn.example.com for Simplified Chinese, and hk.example.com for Traditional Chinese).
One of the minor annoyances I'd been encountering while working with these sites was the need to login on each subdomain before being able to properly administer content. For example, when adding a translation I would get access denied messages until I logged into the subdomain of the language I wanted to add a translation for. Thankfully these problems are no more!
On an SBS 2008 machine I was noticing the following error every day around 3:30 am
Event 2003, Perflib
The configuration information of the performance library C:\Windows\system32\sqlctr90.dll for the MSSQL$SBSMONITORING service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
While setting up an install of SBS 2011 I was forced to rely on the POP3 Connector while I waited for Telus to change the internet connection to a static IP.
One of the email accounts of the company was a Shared Mailbox for the company info line that I created with an Exchange Management Shell command. Because the mailbox wasn't created using the SBS Console it wasn't visible in the list of Exchange Mailboxes the POP3 Connector could download to. Fortunately, it was an easy fix.
