by
Shijaz Abdulla on 16.08.2007 at 18:29
An excellent post has been made by Jim Harrison on the ISA Server team blog on how to troubleshoot issues with RPC over HTTPS while publishing these services using ISA Server.
I’ve had a chance to skim through some of the content and I think it will be really helpful. Check it out.
Thanks Jim!
by
Shijaz Abdulla on 13.08.2007 at 08:13
If you have published Outlook Web Access (OWA) using ISA Server 2006 Forms-based authentication (FBA) and decided to use the new Password Management features on ISA Server 2006 FBA instead of the conventional OWA change password feature, you need to read this.
When you have install Windows Server 2003 Service Pack 2 or the
Scalable Networking Pack on the computer running ISA Server 2006, you will probably face issues when you enabled ISA Server 2006 Password management features. Users may report that the login process takes a long time (15 seconds or more) when you turn on the password management feature, even if they choose not to change their password while logging on.
I have written an article for a workaround to this, the KB article is now available on the Microsoft Knowledge Base (
KB555958) and also on
my website.
by
Shijaz Abdulla on 14.06.2007 at 19:51
I decided to sharpen my skills on Exchange 2007 and Windows PowerShell.
So I got my 32-bit eval copy of Exchange 2007 and put it in on my virtualized test lab based on Microsoft Virtual Server 2005 R2. I built two machines, one a Windows Server 2003 domain controller running Exchange 2003 and another running Windows Server 2003 with Exchange Server 2007 (with Mailbox Server, Hub Transport Server, Client Access Server roles) joined to the same domain.
When I installed Exchange 2007, setup automatically placed Exchange 2007 in its own administrative group in the Exchange 2003 organization named “Exchange Administrative Group (FYDIBOHF23SPDLT)”.
Ever wondered what FYDIBOHF23SPDLT means?? Look at those letters again. If you replace each letter in FYDIBOHF23SPDLT with the previous letter in the alphabet, you get EXCHANGE12ROCKS. And boy, does it rock!!
Setup also creates a new routing group inside this new administrative group, and it is named “Exchange Routing Group (DWBGZMFD01QNBJR). Now guess what that means! Yes, replace each letter in DWBGZMFD01QNBJR with the next letter in the alphabet and you still get EXCHANGE12ROCKS! I guess it rocks both ways, huh?!
A routing group connector between this new routing group and your existing Exchange 2003 routing group enables mailflow between Exchange 2003 and Exchange 2007.
by
Shijaz Abdulla on 27.05.2007 at 08:09
Microsoft has officially announced that it will no longer support SQL Server 2000 Service Pack 3 from July 10, 2007. Microsoft Customers who are running their systems on SQL Server 2000 Service Pack 3a or an earlier Service Pack (*yikes!*) should consider upgrading to Service Pack 4 or better still, SQL Server 2005.
“That Microsoft again, forcing customers to buy new software”, I hear you say. Well, there comes a time when you just need to give away with the old, and bring in with the new. 
SQL Server 2005 without any Service Pack installed will also be “not supported by Microsoft from July 10, 2007″.
Other products joining the “not supportable” bandwagon include SUS 1.0 and SUS 1.0 Service Pack 1 on July 10, 2007. Microsoft will stop supporting Microsoft Business Solutions Great Plains 8 from October 9, 2007.
Microsoft has also announced that Exchange Server 2003 Service Pack 1 support will cease on January 8, 2008. So those of you out there still running Exchange 2003 Service Pack 1 will need to install SP2 to get Microsoft to support you.
Windows XP (Pro, Home, Media Center, Tablet, Pro x64), Office 2003 and Exchange Server 2003 will transition from ‘Mainstream support’ to ‘Extended support’ starting from April 14, 2009, which means you need to pay extra to Microsoft if you want them to continue supporting you past this date. There’s still enough time 
Happy upgrading!
by
Shijaz Abdulla on 21.04.2007 at 08:06
So you went ahead and installed Windows Server 2003 Service Pack 2 on your Exchange 2003 cluster because it’s a “good thing” (Not that service packs are not good things, they really are!).
Everything went well until all of a sudden, your users report that they can’t access their mailboxes through OWA. They complain that they get the dreaded “500 – Internal Server Error” message in their browsers.
Its time to dig into the Microsoft Knowledge base. KB article 841560 suggests that you install Exchange Server 2003 Service Pack 1 on your cluster and install hotfix 841561.
And then… you should find your problems melting away.
Next posts >
