An old password still works after you change it in Outlook Web Access

Assume that a user changes their password in Outlook Web Access (OWA) in one of the following versions of Microsoft Exchange Server:

  • Microsoft Exchange Server 2010
  • Microsoft Exchange Server 2007
  • Microsoft Exchange Server 2003

In this case, you may notice a 15-minute period during which the user can log on to their mailbox by using either the old password or the new password. However, if the user uses a MAPI client (such as Microsoft Outlook) to access the mailbox or if the user tries to access other files and resources, the user is authenticated only if they use the new password.

This latency exists by design for Internet Information Services (IIS) performance reasons and is controlled by the following registry setting.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Start Registry Editor (Regedt32.exe) on the server that is running IIS and through which the user gains access to OWA.
Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters
On the Edit menu, click Add Value, and then add the following registry value:
Value Name: UserTokenTTL (Note This is case-sensitive!) Data Type: REG_DWORD Value Range: 0 – 0x7FFFFFFF (Note This unit is in seconds.)
Exit Registry Editor, and then restart IIS.

Microsoft SQL Server Management Studio 2005 is to slow

In a corporate environment it is not uncommon for Microsoft SQL Server Management Studio (SSMS) for SQL Server 2005 to take over 45 seconds to start as well as lags and delays when opening various windows and dialog boxes from within the application. If you are experiencing this issue, then a quick fix is to add an entry in your HOSTS. file that points crl.microsoft.com to 127.0.0.1

  1. Exit SSMS
  2. Press the keys [Win] + [R]
  3. Enter the following..
    notepad %systemroot%\system32\drivers\etc\hosts.
  4. Append the following..
    127.0.0.1    crl.microsoft.com
  5. Save the file.
  6. Start SSMS (ah! much better)

The reason why it is slow is because .Net Runtime tries to contact crl.microsoft.com to ensure that the certificate in various .Net packages that were shipped with SSMS is valid.
If you are behind a firewall/proxy as is the usual case then there is no direct route out to the internet to crl.microsoft.com to validate the certificate(s) and it eventually times out. The wait for the time out causes the delay for each and every package it checks.

With the change to the HOSTS. file, you are forcing the certificate checks to crl.microsoft.com to route to the local host which immediately fails and the certificate checks are ignored.

SQL Server Management Studio may also be configured to use online help recourses, while the host computer may not have access to the online resources.

First Step:

  1. Go to “Start” -> “Programs” -> “Microsoft SQL Server 2005”.
  2. Open “SQL Server Management Studio”.
  3. Navigate to “Tools”  -> “Options” -> “Help” -> “Online”.
  4. Mark the checkbox “Try local first, not online”
  5. Press on “Ok” button.
  6. Restart SQL Server Management Studio”.

Tip: In some cases you may need to disable “Check for publishers certificate revocation” option under the Internet Explorer -> “Internet Options” -> Advanced”.

Second Step:

  1. Go to “Start” -> “Programs” -> “Microsoft SQL Server 2005”.
  2. Open “SQL Server Error and Usage Reporting”
  3. Uncheck the following checkboxes:
    a.”Send error reports for all components and instances of SQL 2005 to Microsoft or your corporate error reporting server.”
    Note: Using local “corporate error reporting server”, may require to enable this feather.
    b. “Send feather usage reports for all components and instances of SQL 2005 to Microsoft.”
  4. 4. Press on “Ok” button.

Speed up your Joomla! site

Here are a few tips for speeding up your Joomla! site.

Gzip, Sometimes

Encoding your pages with Gzip is an 90% solution…  If your server’s processor is faster than your bandwidth (again, 90% of the time), than enabling Gzip compression will actually speed up your site.  I say that because gzipping the pages does require some CPU horsepower.  Try enabling Gzip and see if your site loads any faster (especially on highly loaded servers).  If it doesn’t, or you get CPU warnings from your host, disable Gzip.  It can hurt you, but most of the time it does help.  The only way to find out is to try it.

Statistics May Seem Nice, but…

They use a ton of SQL queries to get done what they do.  They are not worth it at all!  If you want nice stats, use Google Analytics to track your users.  Stay away from 3pd stats components.  They do generate nice stats, but at a huge performance penalty.  The only statistic worth keeping is the search queries (from the Joomla config).  If you have access to the webserver, you can also disable logging statistics from the server end as well (this process is much more efficient, and only will really help if your server is heavily loaded).

SEF is not Server Friendly

One of the best things you can do to a site, is make the URL’s look more better.  The Joomla core does an acceptable job, but there are a handful of 3pd components that make really nice URLs.  The problem with these components, is that they are not very performance friendly (they use a ton of queries).  I prefer OpenSEF to any of the others (But it’s no longer actively developed) as it seems to be a good mix of power, flexibility and performance.  Keep in mind, that using SEF URLs is a tradeoff.  A good URL will look better to a search engine, and to end users, but it hurts the load time.  Think carefully before deciding to enable SEF URLs.  One thing you can do, is periodically optimize the database by purging unpublished and invalid URLs from the OpenSEF database (an option in the admin section of OpenSEF).

Enable Caching as Much as Possible

If you can, enable Joomla’s core content cache.  It does speed things up when viewing content and modules (mambots don’t need to be processed each time the page is loaded).  If you really want to speed things up for unregistered users, take a look at my  Page Caching component which caches entire pages.  This is probably the best performance gain you can find you unregistered users (the majority of users for 95% of websites).  This does not mean that you can forget about the rest of these optimizations, because the registered users will still see the uncached site.

For a complete list of Joomla Performance tips please visit: JoomlaPerformance.com