Reviving a non-responsive Nokia Treasure Tag

by Shijaz Abdulla on 21.10.2014 at 14:34

The Nokia Treasure tag is an amazing companion for your Nokia Lumia phone. It uses NFC (Near Field Communication) to help you keep track of your things like keys, bag/purse etc, by making an audible beep when the phone and the tag are beyond bluetooth reach of one another.

However, over time the Nokia Treasure Tag may stop responding to your phone and it may seem nothing works, including removing and re-installing the battery.

If this happens, here is a fix:

WP_20141021_010  WP_20141021_014

1. Open the battery compartment of your treasure tag using a tiny screwdriver or pointed object.

2. Remove the battery.

3. Press and hold the multifunction button your treasure tag while you re-install the battery. Press and hold it till you put the battery cover back in place.

Your tag is now reset and you can pair it once again with your Lumia phone.

Preventing an image in your Outlook signature from pixelating

by Shijaz Abdulla on 29.08.2014 at 23:59

You’ve probably noticed that Outlook compresses an image you place in your signature when it sends the email, causing loss of quality. However the rate of pixelation varies by image type.

image image
Before (left) and after (right)

Here’s a quick tip that will help you get better results. Outlook compresses all images to 96 dpi before it sends the email. If you change your image to 96 dpi before you embed it in your signature you will have better results.

1. Open your high-resolution image in an image editor such as IrfanView or GIMP.

2. Re-scale the image to 96dpi.

In GIMP, you would go to Image > Scale Image.


In IrfanView, you would go to Image > Resize/Resample.


3. Save the image. If necessary adjust the height and width on the same tool.

4. Go back to Outlook, and embed the new image in your signature. You should get better results now.

Creating a shortcut to change the default audio device in Windows

by Shijaz Abdulla on 13.05.2013 at 15:25

Most of us use multiple audio devices. Sometimes its a headset, at other times it’s the default laptop speakers, and at other times it might a speaker system connected to your docking station or even a webcam microphone.

Unfortunately, switching between the various audio devices can be tedious as you need to change the Windows “default device” or the “default communications device” each time for both recording and playback.

Today we’re going to see how you can create simple shortcuts on your taskbar that let you effortlessly switch between audio devices.


The three shortcuts you see in my little “Audio Control” custom toolbar let me switch between by Microsoft LifeChat LX-3000 headset, Internal Speakers and Logitech c920 HD webcam microphone. Here’s how I created these shortcuts:

Note: I have tried this on Windows 8, but I am pretty sure it will work on Windows 7 too.

1. Download the NIRCMD utility and extract it to a folder on your computer, let’s call it C:\NIRCMD

2. Open your Windows Playback devices (Right click on your speaker icon on the taskbar).


Note the names of each of the devices you need to change. You can click on Properties to view the correct name. You will need the exact same name for the NIRCMD command to work. If you have two devices with the same name (example: “Speakers”) you will need to rename one of them so that they are unique. Click Properties if you need to rename devices.

Note the names in a text file for easy copy-paste.

In my case, the three playback device names are:

  • “Headset Earphone”
  • “Speakers”

3. Do the same with recording devices. Note the names in a text file. In my case the names of my 3 recording devices are:

  • “Headset Microphone”
  • “Microphone”
  • “C920 Microphone” (renamed)

4. Now open the C:\NIRCMD folder, create a new batch file for each device, let’s call them SPEAKERS.BAT, HEADPHONE.BAT, and WEBCAM.BAT

5. Use similar commands as below for each of the BAT files. Use the device names you copied earlier.


C:\NIRCMD\NIRCMDC setdefaultsounddevice "Speakers" 2
C:\NIRCMD\NIRCMDC setdefaultsounddevice "Internal Microphone" 2
C:\NIRCMD\NIRCMDC setdefaultsounddevice "Speakers" 1
C:\NIRCMD\NIRCMDC setdefaultsounddevice "Internal Microphone" 1


C:\NIRCMD\NIRCMDC setdefaultsounddevice "Headset Earphone" 2
C:\NIRCMD\NIRCMDC setdefaultsounddevice "Headset Microphone" 2
C:\NIRCMD\NIRCMDC setdefaultsounddevice "Headset Earphone" 1
C:\NIRCMD\NIRCMDC setdefaultsounddevice "Headset Microphone" 1


C:\NIRCMD\NIRCMDC setdefaultsounddevice "Speakers" 2
C:\NIRCMD\NIRCMDC setdefaultsounddevice "C920 Microphone" 2


  • The “1” in the NIRCMD command line argument indicates that the device is set as “Default Device”. A “2” in the command indicates that the device will be set as a “Default Communications Device” (useful for Skype, Lync etc).
  • The device name string should be EXACTLY the same that is defined in Windows.

6. Test each batch file by double clicking on them and observing if the default device changed.

7. Create a folder "Audio Control” for your custom toolbar. Your NIRCMD folder should look like the below now.


7. Inside the Audio Control folder, create three shortcuts to the batch files that you created in step 5. Click Change Icon in the shortcut file properties if you want to change the icons like I have done.

8. Right click on an empty space on your taskbar and choose New toolbar.



9. Choose the C:\NIRCMD\Audio Control folder. You now have an awesome new Audio Controls toolbar.

You will appreciate the one-click ease with which you can now change your default audio device in Windows. Leave a comment and let us know your feedback! 🙂

What happens when you choose the “repair” option on a network connection

by Shijaz Abdulla on 30.11.2012 at 21:12

Ever wondered what happens when you choose the “Repair” option on your local area network (LAN) or high speed internet connection?

Here is a list of steps that are taken in the order that it happens:

  • Dynamic Host Configuration Protocol (DHCP) lease is renewed: ipconfig /renew
  • Address Resolution Protocol (ARP) cache is flushed: arp -d *
  • Reload of the NetBIOS name cache: nbtstat -R
  • NetBIOS name update is sent: nbtstat -RR
  • Domain Name System (DNS) cache is flushed: ipconfig /flushdns
  • DNS name registration: ipconfig /registerdns
  • IEEE 802.1X Authentication Restart (Windows XP SP1 and above)

Location-aware printing: Automatically selecting the default printer in Windows 7

by Shijaz Abdulla on 12.12.2009 at 21:01

Thanks to the location-aware printing feature in Windows 7, your computer will automatically print to the correct printer at home or office, depending on where you are.


Here’s how you can set up this feature:

  • From the Start menu, select Devices & Printers 

    Devices and Printers
  • Click on a printer, and click on the Manage default printers button (highlighted in the above screenshot).
  • Make sure ‘Change my default printer when I change networks’ is selected.
  • From the dropdown boxes for the network and the printer, select the appropriate printer for each network.


In my configuration, I print on the HP printer at the office when I’m at the office, and the Lexmark printer when I’m back home, and Windows will automatically change the default printer depending on where I am.

Top 12 mistakes while configuring ISA Server

by Shijaz Abdulla on 03.05.2009 at 18:17

This article used to exist on before it was taken down in May 2009. Originally published in August 2007.


This article lists some of the common configuration mistakes and gives information on how to avoid them.

  1. There is no such thing as a single interface firewall

A firewall has a minimum of two network interfaces. This means you need at least *two* NIC cards in your ISA box if you want it to work as a firewall. Theoretically you can run ISA on a box with a single NIC, but that will do little to secure your network. You might just use it as a proxy that your users can connect to the Internet with.

Tom Shinder of says: “Deploying a single-NIC ISA Firewall is like giving a soldier a Desert Eagle .50 and no ammo.”

In short, you’re not using ISA as a real firewall if you don’t have two interfaces on it!

  1. Specify the default gateway on that published server!

You need to specify the internal IP address of the ISA server as the default gateway on the server that you want to publish on ISA. Or, make sure that there are appropriate static routes in place.

  1. Rules that contradict each other

As can be seen from the diagram below, ISA processes your access rules in the order that you specify them, i.e. rule #1 processed first, then 2, 3, etc. If ISA finds that rule #1 is satisfying the conditions required for the access requested by the user, it skips all remaining rules and grants (or denies) access. However, if the condition is not matching for the current rule, it moves on to the next rule and so on.

If you happen to place a rule that ‘allows internet access to all users’ BEFORE a rule that ‘denies internet access to Peter’, then Peter will still have internet access. It might look simple but these mistakes happen all the time.


  1. IP Addresses


The external interface and internal interfaces on the ISA firewall must belong to separate IP ranges. You cannot have internal and external interface IP addresses from the same IP range.

IP Spoofing: In case there is an internal router that splits the internal network into two (see diagram above), and ISA Server is in one of these networks, make sure that ranges on either side of the internal router are entered in the Internal network address range on ISA. For example, if you have two internal (protected) networks and separated by a router, and the ISA is at (say), the Internal range on ISA should ideally include as well as to

  1. Installing a service on Port 80 of the ISA Server

Avoid installing any service to listen on port 80 of the ISA Server as this is used by the Web Proxy service. A common mistake is installing a website to listen on port 80 on the ISA Server. Usually this is the result of installing certain third party components (like Trend Micro OfficeScan, which has a web-based console) installed on the ISA Server.

When port 80 is used for listening by another service, Web Proxy may run into problems or clients may be unable to access the other service running on port 80. A symptom of this problem is when you see results under Logging in the Monitoring console where the Source Network, Destination Network, Protocol fields are blank, but the Port field contains 80 and the Action field may be Failed Connection. ISA Console also generates an alert when this happens.

  1. SMTP Fix-Up: ISA and Cisco PIX

When using ISA behind Cisco PIX (ISA being a second firewall), make sure you disable SMTP fixup on the Cisco PIX if you plan to publish Exchange behind ISA (see diagram). This can be done by typing the following command at the Cisco PIX console:

no fixup smtp protocol 25

write mem

Note: SMTP Fixup prevents you from telnetting on port 25 that is NATed on PIX to ISA Server, and NATed (published) on ISA Server to Exchange Server. When a telnet attempt is made, you get some asterisks (220*******************************************************0*2******0***********************

2002*******2***0*00) in the output. This can be avoided by disabling smtp fixup as explained above.

  1. FTP is allowed, but users can’t put files on the remote FTP server

You create a rule to Allow FTP from Internal to External so that your users can access FTP sites on the internet. But still your users still can’t write/delete files on the FTP server? It’s because you have to explicitly specify it!

Right click on the rule and click Configure FTP. Clear the check mark next to Read Only.

  1. Care while Installing Windows 2003 Service Pack 1 / Service Pack 2 and the Scalable Networking Pack

You are running ISA Server 2004 Standard Edition. One fine day, you decide to install Windows 2003 Service Pack 1 on your ISA Server. RPC traffic is blocked. You may not be able to browse the active directory for users from the ISA Server. Occasionally you get an error popup for RPC related errors.

When you see these symptoms, its time to install ISA Server 2004 Standard Service Pack 1!

If you install Windows Server 2003 Service Pack 2 or the Scalable Networking Pack, make sure that you read my KB article 555958.

  1. Scheduling limitations that you need to be aware of

This is not a configuration mistake, but is something of an expectation that requires clarification. When you create a rule in the access policy that has a schedule (In the rule properties, select the Schedule tab), there are two things that you cannot do:

i. Once you have created a schedule and applied changes, you can’t edit it. You will probably need to create a new schedule object.

ii. Your schedule limits cannot be in half hours, i.e. you can configure a rule to apply between 2 PM to 3 PM but not between 2.30 PM to 3.30 PM.

  1. Common name on Certificates

When you issue certificates from your CA (or obtain a commercial certificate), the common name should be the published name, i.e. DNS name that you would use to access the website/OWA/etc from outside. For example, if you are publishing a server webserver01.mydomain.local, and users will access thi
s using the internet name, then your SSL certificate common name should be “”. Else, your users will get a warning stating that “the name of the server does not match the name on the certificate”.

  1. More than one Default Gateway

Never specify more than one default gateway on the ISA Server. Do not specify the default gateway on both the internal and external NICs.

  1. DNS Server on more than one NIC

Never specify DNS on more than one NIC. For DNS best practices on ISA Server, see this article.

TIP: Keep a backup!

Keep an XML backup of your ISA configuration before you try out something with the access rules or the configuration. This will help you easily restore your ISA configuration in case you mess it up!

Also note that when you change the Network Template, you lose ALL your Access Rules and Network Rules!

Test your Exchange Server remotely

by Shijaz Abdulla on 03.04.2009 at 00:07

Microsoft Exchange Team has released the Exchange Server Remote Connectivity Analyzer.

This tool helps you ensure that your Exchange internet services like Autodiscover, ActiveSync, Outlook Anywhere, Inbound SMTP have been configured correctly.

Exchange implementers! Bookmark this website:


In the current release, the tool can check Exchange ActiveSync on Windows Mobile 5 and third party devices. It can also check Outlook Anywhere on Outlook 2003 and Outlook 2007 with Autodiscover.

For more information on the tool and a video, check out the Exchange Team blog.

My adventures with Blackberry

by Shijaz Abdulla on 21.12.2008 at 21:51

blackberry-logo I like to visualize the BlackBerry server as a ‘black box’ – only because it is often difficult to figure out where the problem is. Perhaps my ignorance is to blame, or it’s just my love for the simplicity/transparency surrounding the inner workings of ActiveSync.

The other day, for instance, I was trying to activate a Blackberry Bold device. The activation kept timing out for no reason. Most of the time when this happens, one of the following usually solves the problem.

  • "Wipe" the device
  • Delete and re-create the user on the Blackberry server
  • Do a failover (we have NeverFail for Blackberry)
  • Do a full restart of the server.

But this time it was rather strange. All the above actions were in vain. So I decided to ‘troubleshoot by elimination’.

  • Check if same SIM card works on another blackberry enabled device. (yes)
  • Check if another user can be activated on same blackberry device with same SIM (yes)

I then deduced that there is nothing wrong with the Black Box .. er.. BlackBerry server, the device or the SIM card. "It must be something on the mailbox", I thought. But what exactly?

A quick call to our service provider, and a long wait for someone to get back to me revealed to me what I was missing — the user’s junk mail filter!

Blackberry activation involves sending an email to the user’s inbox, which would contain some kind of a hash. The user’s junk mail filter mistakenly thought that the emails from blackberry were spam and sent it to the user’s Junk Mail folder in Outlook, before the blackberry server could pick it up (from the Inbox folder) and activate the device!

Removing leading/trailing white spaces from displayName using PowerShell

by Shijaz Abdulla on 14.11.2008 at 06:09

I am moving thousands of Exchange 2003 mailboxes to Exchange Server 2007 over this weekend. Most of these are student mailboxes which have been provisioned using another third party system. Due to a minor bug, the third party system added a trailing space to every student’s display name.

A trailing space is a whitespace at the end of the displayName string. This may look like a very small issue, but unfortunately Exchange Server 2007 is very fussy about such things:

The DisplayName property contains leading or trailing whitespace, which must be removed.

More of that… (ouch!)

Exchange 2007 would not let me move these mailboxes across from Exchange 2003 unless I correct the DisplayName property for all the mailboxes.

I have several thousands of mailboxes having an ‘inconsistent’ display name. Correcting each of these manually would have been a frustrating exercise – so I decided to coin my own PowerShell command to remove leading/trailing spaces from all mailboxes in a given mailbox database. Nerd

get-mailbox -Database ‘SERVERMailStore’ -ResultSize 4850 | Foreach { Set-Mailbox -Identity $_.Identity -DisplayName $_.DisplayName.Trim() }

where SERVER is the Exchange 2003 server hosting the mailboxes you want to modify, MailStore is the Mailbox store on that server containing those mailboxes. I set the ResultSize to 4850 because I have more than 4000 mailboxes and by default the get-mailbox command fetches only 1000.

Unlocking files that are in use

by Shijaz Abdulla on 22.10.2008 at 21:20

Sometimes you cannot delete or rename a file that is currently in use. You might receive an access violation error, or simply a message telling you that your action could not be completed because the file is open in another program.


You may have already come across the Unlocker freeware tool that lets you "unlock" files that are in use by some application.

Here is another way (let’s call it the ‘techie’ way) to unlock files that are in use. It makes use of the Process Explorer tool from Windows SysInternals.

  • Download the Process Explorer tool. Execute procexp.exe
  • Choose Find > Find Handle or DLL option


  • Type the name of the file you want to unlock and hit Search.


  • The process EXE locking the file and the path to the file are listed. Double click on the result.


  • The file handle will be highlighted. Right-click on it and choose Close Handle.

Your file is now unlocked and can now be deleted, moved or renamed.

A little disclaimer here, closing handles might cause data inconsistency, loss and/or other undesirable effects. Make sure you understand what you’re doing before you do it.

< Previous posts