Speed up Evernote with the secret Debug menu
Exit Evernote, hit Win+R and type Evernote.exe /DebugMenu. Evernote should pop up with a new menu option – Debug. Choose Optimize Database from the menu.

Evernote does optimize its database automatically, but if you feel it’s been running slowly for a while, use this option to speed it up. This should make searches faster too. Thanks Killer Tech Tips!

The short conference by TED about Stuxnet ! (actually comments are very intersting than the talk for me!)

Access the stuff on your computers from almost anywhere

With Windows Live Mesh and the Devices website, you can finally stop emailing files to yourself, carrying them around on a USB drive, or worrying whether the version you have with you is the latest

Download link : http://explore.live.com/windows-live-mesh?os=other

It`s working buddy!

Try it!

Attention: Important Information on Sharepoint 2007 Service Pack 2

 Just before installing sharepoint service pack 2 in my organization the following article from "Microsoft sharepoint team blog" saved me of bad hazard.

With thanks to sharepoint Blog.

 

Attention: Important Information on Service Pack 2

We take product quality seriously and make every effort to avoid and resolve issues that adversely impact our customers.  Unfortunately, we have recently discovered a bug with Service Pack 2 (SP2) that affects all customers that have deployed it for SharePoint Server 2007. 
During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date passes. Furthermore, product expiration 180 days after SP2 installation will not affect customer’s data, configuration or application code but will render SharePoint inaccessible for end-users.
We are working to release a hotfix to automatically fix this issue. A manual work-around is currently available and involves customers re-entering their Product ID number (PID) on the Convert License Type page in Central Administration.  For more information and detailed steps please read this KB article.
We want to assure our customers that this issue does not impact data integrity or their SharePoint deployment in any other way.
For your convenience, below are some answers to questions that you may have and we will update this blog post with a link to the hotfix as soon as it’s available.
We apologize for any inconvenience this issue may cause you.
Jeff Teper
Corporate Vice President
SharePoint.
Q&A
Which products are affected by this?
Applying Service Pack 2 to any of the following products will result in this issue: Office SharePoint Server 2007, Office SharePoint Server 2007 for Internet Sites, Project Server 2007, Form Server 2007, Search Server 2008 and Search Server 2008 Express.
Windows SharePoint Services 3.0 is not affected by this issue.
What can I do to fix it?
To work around this issue customers will need to re-enter their Product ID numbers (PID) on the Convert License Type page in Central Administration.  Please see this KB article for detailed steps. 
Customers can also wait for the hotfix (available for free from http://support.microsoft.com) to resolve this issue.
Product ID numbers (PIDs) can be retrieved by logging into the Volume Licensing Service Center.
Note: For Search Server 2008 Express the only way to resolve this issue is to apply the hotfix.
What is Microsoft doing to fix it?
Microsoft is working on a hotfix and public update for the product. We will update this blog post with details and a link to the hotfix as soon as it is available.
Do I need to update all of the servers in my farm?
No. The Product ID number only needs to be entered once.
What if I haven’t installed SP2 yet but want to? What should I do? You can continue to plan for and install Service Pack 2 for SharePoint Server 2007 with the additional step of re-entering your Product ID number after the installation is complete by following the instructions in this KB article.
Does this issue impact anything else?
The issue only activates the product expiration date. The activation of the expiration date does not affect the normal function of SharePoint up until the expiration date passes, at which point SharePoint will be inaccessible for end-users. This issue does not affect customer’s data, configuration or application code.
I can’t find/don’t know my original PID, where can I find it?
Product ID numbers (PIDs) can be retrieved by logging into the Volume Licensing Service Center.

Non-administrator users joind computers to domain

I was confused why all my configuration does not apply to a group called " Client Support Group" .
I`ve set a policy for this group and then permitted them to add computer object from advanced security option in that policy properties but none of them was effective.

After some googling i was found this useful article and now must thanks to Microsoft.

Users cannot join a computer to a domain

To resolve the issue in which users cannot join a computer to a domain, follow these steps:

1. Click Start, click Run, type dsa.msc, and then click OK.
2. In the task pane, expand the domain node.
3. Locate and right-click the OU that you want to modify, and then click Delegate Control.
4. In the Delegation of Control Wizard, click Next.
5. Click Add to add a specific user or a specific group to the Selected users and groups list, and then click Next.
6. In the Tasks to Delegate page, click Create a custom task to delegate, and then click Next.
7. Click Only the following objects in the folder, and then from the list, click to select the Computer objects check box. Then, select the check boxes below the list, Create selected objects in this folder and Delete selected objects in this folder.
8. Click Next.
9. In the Permissions list, click to select the following check boxes:
   • Reset Password
   • Read and write Account Restrictions
   • Validated write to DNS host name
   • Validated write to service principal name
10. Click Next, and then click Finish.
11. Close the "Active Directory Users and Computers" MMC snap-in.

RVTools version 2.9 has been released

RVTools version 2.9 has been released

Rob de Veij over at Robware.net has released version 2.9 of the most awesome utility I know, well if you don’t count in the vmClient You better check out the newest release of RVTools. I already did, and recorded a walkthrough which can be watched here in HD quality. You can also take a peek at Vimeo.
RVTools is a windows .NET 2.0 application which uses the VI SDK to display information about your virtual machines and ESX hosts. Interacting with VirtualCenter 2.5, ESX 3.5, ESX3i, ESX4i and vSphere 4 RVTools is able to list information about cpu, memory, disks, nics, cd-rom, floppy drives, snapshots, VMware tools, ESX hosts, nics, datastores, switches, ports and health checks. With RVTools you can disconnect the cd-rom or floppy drives from the virtual machines and RVTools is able to list the current version of the VMware Tools installed inside each virtual machine and update them to the latest version.
Version 2.9 (April 2010)
• On vHost tab new fields: Vendor and model.
• On vHost tab new fields: Bios version and Bios release date.
• On vInfo tab new field: VM overall size in bytes (visible when using VI API 4.0)
• On vSnapshot tab new fields: Snapshot filename and size in bytes (visible when using VI API 4.0)
• New vNic tab. The vNic tab displays for each physival nic on the host the following fields: Host, datacenter, cluster name, network device, driver, speed, duplex setting, mac address, PCI and wakeon switch.
• Layout change on vHost, vSwitch and vPort tabpages. They now all start with host name, datacenter and cluster name.
• The commandline function ExportAll extended with an extra optional parameter. It's now possible to specify the directory where the export files are written.

CCBoot - iSCSI Boot Windows XP, 2003, Vista, Windows 7 and 2008

CCBoot allows a diskless boot of either Windows XP, Windows 2003, Windows Vista, Windows 7, or Windows 2008 from an iSCSI target machine remotely located over a standard IP network. Diskless boot makes it possible for computers to be operated without a local disk. The diskless computer is connected to a hard drive over a network and boots up an operating system from a remotely located machine. CCBoot is the convergence of the rapidly emerging iSCSI protocol with gPXE diskless boot technology.
CCBoot offers a seamless diskless boot. Eliminating the need for a local hard drive opens a wide range of possibilities for network management. Using this configuration, the disks for many network computers can be centrally managed, thereby facilitating backup, redundancy, and dynamic allocation of valuable storage resources while at the same time reducing cost to the enterprise.

Booting from iSCSI makes system administration considerably easier. Freeing a server of its boot volume allows administrators to manage investments in their iSCSI SANs, attaining improved data security, integrity and recovery, higher availability, quicker server deployment & repurposing, and more efficient utilization of storage resources.

http://ccboot.com/