Friday, October 29, 2010

Where the 32-bit Programs Hide in the Registry

Trying to increase the speed of a Windows system typically involves disabling Services, removing items from the Startup menu and deleting Registry entries under Run, in both the Current User and Local Machine trees. The latter bit is what was missing when working on 64-bit systems.

After noticing that the pesky Acrobat Speed Launcher and other usual suspects were missing from the Run locations I ran a registry search for reader_sl.exe and with little delay was presented with the location below, which also hosted all it's resource sapping pals as well.

HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Run

Note: As always, the Registry can be a dangerous place, so do a backup/export before making changes.

Sunday, October 17, 2010

Exchange 2003 RPC over HTTPS - Easy

If you remember way back in September of 2003, (I don't, had to look up the date), a new version of Exchange Server was released with a new and really cool feature, RPC over HTTPS. This allowed for use of Outlook outside the company's network without the need for VPN. What a huge boon for traveling employees and IT staff alike.

With that came a convoluted configuration that probably resulted in more support calls to Microsoft than anything else involving the then-new Exchange Server 2003 product. And I always found it puzzling that Microsoft didn't create a wizard to automate this configuration, as they did for Small Business Server 2003, which included Exchange Server. (This was addressed in the later Exchange Server releases, 2007 and 2010.)

In any case it always seemed like a miracle was preformed when RPC over HTTPS finally did work. Fast-forward seven years and there are web pages and tutorials aplenty. In my recent search, the MSExchange article I found was the most straight-forward for a single system, Exchange Server 2003 deployment. One key element upon completion of the feature install and changes to the registry, is to make sure you reboot any Domain Controllers that were updated after the work is complete.

The reboot is necessary to complete the Global Catalog port mapping of 6004. In fact, you should be able to telnet to ports 6001 and 6002 on the Exchange Server, and 6004 on the Global Catalog server that was updated.

And as always, there is the ├╝ber-useful Exchange Remote Connectivity Analyzer to aid with troubleshooting (that's how I found out the Global Catalog needed a reboot).