Unlock files used by processes

Overview

I think most of the Windows users have seen the screen saying that “Cannot delete XXX: It is being used by another person or program”. This is quite annoying as you don’t have a clue what is actually locking the file. Now I would like to share some of the programs I used (or heard) to solve this problem.

Reference

Unlocker - http://ccollomb.free.fr/unlocker/

It is a very nice program which add a extensions to your Windows Explorer, so that you can right-click on any file/folder and select the “unlocker” option. It will shows all processes locking the file for your to decide what to do next. However the latest version (1.8.7) does not supports 64-bit OS.

LockHunter - http://lockhunter.com/

LockHunter is a similar tool to Unlocker, Windows Explorer extensions. However it works for both 32-bit and 64-bit OS, and it delete files to recycle bin.

Process Explorer - http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

Finding what files (handles) is used by a process is just one of the features of Process Explorer. As it actually shows much more information than the list of handles used. Because it is more powerful, it is also more complicated to use.

To use Process Explorer for unlocking files from processes, following the steps below:

1. Select "Find" –> "Find Handle or DLL"
2. Enter the full path of the file as the Handle substring, click "Search"
3. For each of the search results that match the file you want to delete, right-click on the handle and choose "Close Handle"
4. Done! However I recommend using “LockHunter” if you ONLY want to unlock files. ;-)

Terminal Service Gateway in Windows Server 2008

Overview

Terminal Service & Remote Desktop allow you to access your computer/server virtually anywhere with Internet access. They are very useful and commonly used. However, there is no way to pre-authenticate client or have centralized Authorization Policy settings. Now, with Windows Server 2008 Terminal Service Gateway, we can make use of all this features.

Reference

Configuring the Windows Server 2008 Terminal Services Gateway (Part 1)

Dmitrii blog: Windows Terminal Services Gateway

Steps (Outline only, refer to reference links for Detailed Steps)

Setup the TS Gateway Server

1. On a server with Windows Server 2008 installed
2. Add "Terminal Services" role, select "TS Gateway" as Role services
3. Create a Certificate for SSL connection (Common name must be pointing to the TS Gateway Server IP)
4. At "TS Gateway Manager", configure the following:
   • Install the Cert created at Step 2 to the TS Gateway Server
   • Configure the "Connection Authorization Policies (CAP)"
   • Configure the "Resource Authorization Policies (RAP)"

Connect to Remote Desktop/Terminal Services thru TS Gateway

1. For Windows XP / Windows Server 2003 (Not needed for Vista)
   • Download and Install "Remote Desktop Connection 6.0 Terminal Services Client" by this Link
2. Open "Remote Desktop Connection", click "Options >>"
3. Go to "Advanced" Tab, "Settings"
4. Select "Use these TS Gateway server settings" and input the Server name (Common name of the SSL Certificate) and Logon method.
5. Press "OK" to exit and enter the IP of the computer you want to connect. Beware that the IP here is for the TS Gateway, so it should be IP within the TS Gateway's local network.
6. Click "Connect" to start the connection.

Problems installing SQL Server 2005 with IIS 7

Overview

When I install SQL Server 2005 Enterprise on Windows Server 2008 with IIS 7, I was warned that "Microsoft Internet Information Services (IIS) is either not installed or is disabled". Actually this misleading warning means some features of IIS 7 are not installed, and SQL Server 2005 installation needs those features.

Reference

Problems installing SQL Server 2005 on Vista and IIS7