How to redirect an HTTP connection to HTTPS for Outlook Web Access clients and how to redirect the Default Web Site to point to the Exchange virtual directory
Wednesday, June 17th, 2009This is a Microsoft solution! - Official Link: http://support.microsoft.com/kb/839357
We recommend that you require a Secure Sockets Layer (SSL) connection for your OWA users. An SSL connection encrypts the information that is sent to or received from the Microsoft Exchange Server computer. However, when you configure IIS to require SSL for all incoming OWA requests, OWA users who try to connect by using HTTP receive the following error message:
SSL required
Internet Information Services
After the OWA user receives the error message, the user must manually type https:// at the start of the URL to connect to the Exchange Server computer. You may want to configure IIS to automatically redirect the OWA user’s HTTP request to HTTPS to minimize user interaction and to make sure that all incoming requests are enabled for SSL.
MORE INFORMATION
To configure IIS to automatically redirect HTTP requests as HTTPS requests, foll…
Important If the following conditions are true, you must mount and start the mailbox store before you can successfully complete these steps:
- Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 is installed on a front-end server.
- The mailbox store has been dismounted.
Note Follow these steps on an Exchange front-end server that communicates with a clustered Exchange back-end server.
- Create an Active Server Pages (ASP) Web page that contains the following code:
<% If Request.ServerVariables("HTTPS") = "off" Then Response.Redirect "https://" & Request.ServerVariables("HTTP_HOST") & "/Exchange" End If %> - Name the Web page “Owahttps.asp.”
- In Windows Explorer, create the Inetpub\Wwwroot\CustomErrors folder, and then save the Owahttps.asp Web page file to that folder.
- Start the IIS console.
- In Windows NT Server 4.0 (IIS 4.0)
Note Follow these steps if you are running Microsoft Exchange Server 5.5 OWA on Windows NT 4.0 Server together with the Windows NT 4.0 Option Pack. If you have an Exchange Server 5.5 mailbox server, and if the OWA component is installed separately on a dedicated Web server, follow these steps on the Web server only.
- Click Start, point to Programs, point to Windows NT 4.0 Option Pack, point to Microsoft Internet Information Services, and then click Internet Services Manager.
- Expand Internet Information Server, expand Computer Name, and then expand the Web site that the OWA users use to access their Exchange server. By default, this Web site will be the Default Web Site.
- Go to step 5.
- In Windows 2000 Server (IIS 5.0)
Note Follow these steps if you are running Exchange Server 5.5, Exchange 2000, or Exchange 2003 OWA on Windows 2000 Server.
- Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.
- Double-click Computer Name to expand the computer object.
- Expand the Web site that the OWA users use to access their Exchange server. By default, this Web site will be the Default Web Site.
- Go to step 5.
- In Windows Server 2003 (IIS 6.0)
Note Follow these steps if you are running Exchange 2003 OWA on Windows Server 2003.
- Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
- Expand Computer Name, and then expand Web Sites.
- Expand the Web site that your OWA users use to access their Exchange server. By default, this Web site will be the Default Web Site.
- Go to step 5.
- In Windows NT Server 4.0 (IIS 4.0)
- Right-click the CustomErrors folder, and then click Properties.
- Under the Application settings section, click Create.
Make sure that CustomErrors is displayed in the Application name box.
Note For Exchange 2003 running on IIS 6.0, click ExchangeApplicationPool in the Application Pool list.
- Click the Documents tab, and then add the Owahttps.asp file to the Enable default content page. Move the Owahttps.asp file to the top of the list.
- Click the Directory Security tab, and then click Edit under Authentication and access control.
- Click to select Enable anonymous access, and then click OK.
- Under Secure communications, click Edit.
- Click to clear the Require secure channel (SSL) check box, and then click OK two times.
- Right-click the Exchange virtual directory, and then click Properties.
- Click the Custom Errors tab, and then double-click 403.4.
- In the Message Type list, click URL.
- In the URL box, type /CustomErrors/Owahttps.asp, and then click OK.
- Click the Directory Security tab.
- Under Secure Communications, click Edit.
- Click to select the Require secure channel (SSL) check box.
Note If you want to require 128-bit encryption, click to select the Require 128-bit encryption check box.
- Click OK two times.
Note The Exchange virtual directory and the Public virtual directory are the only virtual directories that you have to configure to require SSL. If you have other virtual directories for which you want to require SSL, enable SSL on each virtual directory individually.
After you follow these steps, visit the http://<server_name>/exchange Web site. In this address, server_name is the name of the Microsoft Internet Information Service (IIS) server.
You should be automatically redirected to https://<server_name>/exchange and to the Logon.asp page.
Additionally, if you want to modify the IIS Default Web Site so that clients can access the OWA logon page by typing only http://<server name> instead of typing http://<server name>/exchange, follow these steps.
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Start the Microsoft Management Console (MMC) IIS snap-in.
- Right-click Default Web Site, click Properties, and then click the Home Directory tab.
- Under When connecting to this resource, the content should come from, click A redirection to a URL.
- In the Redirect to box, type /exchange.
- Under The client will be sent to, click A directory below this one.
- Stop and start the Default Web Site.
For more information about how to simplify the OWA URL, visit the following Microsoft TechNet Web site:
Back to the top
Have you ever tried to join an R2 server to a non R2 domain controller? A classic example is having a SBS2003 server and needing to add an additional 2003 server to your domain, however this 2003 server will be an R2 version. At first you will get an error about not being able to join the domain, the reason being is the R2 Active Directory structure is different from the non-R2 structure. At first it would appear there is no solution to this problem, and the main problem i had was preparing the sbs2003 (32bit) AD for a Windows server 2003 R2 (64bit) server. Ok there is hotfix available from Microsoft that you need to run on the SBS2003 32bit server, this will allow you to join the 64bit R2 server to the domain, even thou sbs isnt R2.
Ok this is going to be a short post but i know there are alot of people out there who are trying to run a 64but server on top of a 32bit host (ok so the host is the server that will run the virtual server, the guest is known as the virtual server). Some people are saying “ooo it cant be done, if you want the guest to be 64bit then the host has to be on a 64bit o/s…bzzzzzzzz wrong). Anyway the possibility of running a 64bit guest on a 32bit host is simple in most cases, and this is what needs to be done.
Ok so im not paying for anti-virus, im not dumb enough to download crap that contains viruses, so i never needed the need, until later on things starting slowing down and thought, ok maybe, just maybe i need to check for a virus. So i did the google thing and looked for free anti virus. Well firstly i hate AVG, i just dont like the layout of the software, system hungry and just sucks, but i stumbled across AVAST free anti-virus. Easy to install, simple to use, good options (and plenty of things to choose), and well so far it has just worked without fuss, o and yes it found a virus (trojan) and deleted it for me. Ok so no worries, i would recommand this to people who are home users and looking for an easy to use security system for there home needs. Well thats all for now, you can visit there website 
Just another small post, we needed an external hard drive, we didnt need anything massive in size (eg. Terrabyte), and we were thinking 320GB would be enough for now. Two reasons why we wanted this size, 1. we only had about 150GB of info to backup, 2. With hard drives moving into the terra’s now, we knew we could get something quality at a good price. Ok so it was a toss up between the LACIE 320GB (product code = 301284A) and the Western Digital “My Book”, both fantastic products, however we went for lacie simply because it had the metal casing, compared with the my book. Its quiet, comes with usb cable and power supply and is just perfect for our needs. The 1 click backup software works easily enough (very very basic software, pretty much a copy and paste style software with no features), but who cares it is backing up our primary work folder without any problems. Cool little device thats only cost about $120 AUS. O and we bought a leather binder as well, its good, has a calender for 2008 and 2009 and its called “the executive series” haha, ok cheers
This entry is going to be short and sweet, only because we have not played with the product to its full potential. Im writting this entry because there were 2 things that impressed me about this products. 1. It easy way to install both via its console and its remote options. Microsoft are really pushing there command line interface powershell, and i can guarantee this will make so many tasks alot quicker to do, espicially when you can write scripts. 2. was the powershell itself. As some of you might have seen with Exchange 2007, the powershell provides an east to manage console to manage the server and its features, once you have set the server up to its normal stat, an administrator can control and manage the server via a network connection to perform daily admin tasks, or run complicated scripts. Anyway thats my first impressions on the product, i look forward to seeing it out of beta and in a working production.
When i first looked at the Thecus box i was impressed with its simple but yet effective design. For those who dont know what a NAS box is, it is a network-attached storage device that holds information and can be accessed from a network device as it become part of a, well a network, hence being called a network attached device. ANYWAY, the version we purchased came with 4 
Well we needed a simple USB wireless device to replace the PCI wireless card in some of the desktop computers. We also liked the idea that there was an extension to sit on the desk of the pc. The belkin usb network adapter looked like a pretty cheap solution to our problem, and hey, its just a wireless device right? wrong. far from it, so we plugged it into a vista machine and all hell broke loose. To start with it installed itself with a set of drivers it downloaded from the windows update site, but for some reason were the wrong one. then when we rebooted the pc, it wouldnt boot back into vista. We found we have to boot into safe mode, delete the drivers and software. So we went to the belkin website and downloaded the vista drivers, ran the install program and for some reason failed. now we are stuck in limbo and cant install this simple network device. it shouldnt be this difficult and has annoyed the crap out of us. sure we could spend the next week trying to solve the problem but nop, to crap with it. RUBBISH. do not purchase this item if you use VISTA!!!