Renaming and disabling AD administrator account is good secure practice, because this account very good target for hackers. Also I would recommend to disable and rename local admins accounts on users workstations and domain servers.
Below you can find my solution for this task. Of course I didn't invent it, just used the best practices.
1. I created new security group in AD, for example "Computer Admins".
2. I added to this group all help desk administrators accounts.
3. I created group policy which added this group to local administrators group on all workstations which have to be managed by help desk administrators.
4. I created group policy for disabling and renaming local administrator account on all workstations which have to be managed by help desk administrators.
And what do I have in summary?
Help desk administrators manage workstations by their domain accounts. All local administrator accounts are disabled. If workstation doesn't have access do DC, help desk can simple restarts it in Safe Mode and log on as local administrator (this account automatically unlocks when you start windows in safe mode).
Be careful with "Restricted Groups", group policy, which used for adding "Computer Admins" accounts to Local Admins group. All members of local group will be replaced by accounts which you defined in group policy.

Microsoft Tech Net Article: http://technet.microsoft.com/en-us/library/cc747353%28WS.10%29.aspx

Try the following:
gpupdate /force.
If that does nnot work try the following:
log in as Admin
Click Start, click Run, type gpedit.msc, and then click OK.
Double-click Computer Configuration, and then double-click Administrative Templates.
Double-click System, and then double-click Group Policy to display the group policies.
Depending on the type of computer from which you making this change, double-click Group Policy refresh interval for computers to make this change for workstations or for member servers. Or, double-click Group Policy refresh interval for domain controllers.
Click Enable in Group Policy refresh interval for computers so that you can modify the refresh and offset intervals settings on the Policy tab. Optionally, the administrator can enable Disable background refresh of group policy.
Click OK, and then close the Computer Management snap-in. restart the machine..

How to delete an OU from windows server -2008 as an administrator:
Right click the OU -> Properties -> click the "Object" tab -> uncheck "Protect object from accidental deletion" -> Apply -> OK

Every time you format and reinstall your PC, you have to activate Windows again, which can sometimes be a pain once you’ve done it too many times. Here’s how to backup and then restore the activation status.
Note: we aren’t going to cover how to reinstall Windows, since you should know how to do that already. This article just covers backing up and restoring your activation. Read More on How To Geek
Posted on How To Geek, 10/21/2011

See what kinds of IT classes MBA students can take to earn an IS concentration Read More on Network World
By Ann Bednarz, Network World, 10/13/2011

IT pros who earn MBA degrees are valued for their hybrid technical-business skills. Read More on Network World
By Ann Bednarz, Network World
October 13, 2011 01:35 PM ET

With each passing year, hardware devices grow less dependent on proprietary components and more reliant on open source technologies. Open source DD-WRT firmware can breathe new life -- and advanced features -- into your old wired or wireless router. Read More on InfoWorld

Drupal is a great product and I am going to put together the stuff that has made drupal easy.

Upgrade Alsa (1.0.23) on Ubuntu Lucid Lynx 10.04

Source Website of this information.
http://monespaceperso.org/blog-en/2010/05/02/upgrade-alsa-1-0-23-on-ubun...
it worked for me and it was great!
 

Installation :
To do this, we must begin by determining our version of alsa as follows :
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.21.

To avoid problems during the upgrade of Alsa-utils, we need to stop it with the following command :
sudo /sbin/alsa-utils stop

We must then install the necessary tools to compile along with the kernel headers :
sudo apt-get -y install build-essential ncurses-dev gettext xmlto libasound2-dev
sudo apt-get -y install linux-headers-`uname -r` libncursesw5-dev

Then, we go in our personal folder and download alsa-driver, alsa-lib and alsa-utils :
cd ~ rm -rf ~/alsa* ~/.pulse*
wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.23.tar.bz2
wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.23.tar.bz2
wget ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.23.tar.bz2

After that, we create a new folder for the compilation and installation of the 3 files. Then, we move the 3 tar files that we just downloaded in this folder :
sudo rm -rf /usr/src/alsa
sudo mkdir -p /usr/src/alsa cd /usr/src/alsa
sudo cp ~/alsa* .

Unpack the 3 tar files :
sudo tar xjf alsa-driver*
sudo tar xjf alsa-lib*
sudo tar xjf alsa-utils*

We compile and install alsa-driver :
cd alsa-driver*
sudo ./configure
sudo make
sudo make install

We compile and install alsa-lib :
cd ../alsa-lib*
sudo ./configure
sudo make
sudo make install

We compile and install alsa-utils :
cd ../alsa-utils*
sudo ./configure
sudo make
sudo make install

(Please note I didn't do this step because I did a release update sound was gone again so I just did the config all over and fixed it again).
Then, we remove the 3 tar files in our personal folder that are not anymore necessary :
rm -f ~/alsa-driver*
rm -f ~/alsa-lib*
rm -f ~/alsa-utils*
 

Then, just restart your computer and your alsa version should be 1.0.23!
You can verify that you have now indeed have this version of alsa :
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.23. Compiled on May 2 2010 for kernel 2.6.32-21-generic (SMP).
 

Just to be sure everything is well configured, execute this command :
sudo alsaconf and reboot again!

 Worked very well for me.