Very useful tools...

http://www.piriform.com/

CCleaner Optimization and Cleaning

Defraggler File Defragmentation

Recuva File Recovery

_____________________________________

Stefano Mazgon

 

Commenti

Posta un commento

Post popolari in questo blog

Removing Terminal Server licenses from an RDP client

    Article ID: 187614 Last Review: October 11, 2007 Revision: 6.4 This article was previously published under Q187614 SUMMARY If an unlicensed client connects to a Terminal Server for the first time, the Terminal Server issues the client a temporary Terminal Server Client Access License (CAL) token. After the user has logged into the session, the Terminal Server instructs the License Server to mark the issued temporary Terminal Server CAL token as being validated. The next time the client connects, an attempt is made to upgrade the validated temporary Terminal Server CAL token to a full Terminal Server CAL token. If no license tokens are available, the temporary Terminal Server CAL token will continue to function for 90 days. The license is stored in the client's registry. Thirty-two bit RDP clients store their license under the key HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing. Important This section, method, or task contains steps that tell you how ...
Continua a leggere

Errors in attaching mdf after ldf corruption or deletion

Fix : Error Msg 1813, Level 16, State 2, Line 1 Could not open new database ‘yourdatabasename’. CREATE DATABASE is aborted. This errors happens when corrupt database log are attempted to attach to new server. Solution of this error is little long and it involves restart of the server. I recommend following all the steps below in order without skipping any of them. Fix/Solution/Workaround: SQL Server logs are corrupted and they need to be rebuilt to make the database operational. Follow all the steps in order. Replace the yourdatabasename name with real name of your database. 1. Create a new database with same name which you are trying to recover or restore. (In our error message it is yourdatabasename ). Make sure the name of the MDF file (primary data file) and LDF files (Log files) same as previous database data and log file. 2. Stop SQL Server. Move original MDF file from older server (or location) to new server (or location) by replacing just created MDF file. Del...
Continua a leggere