Exchange 2007 / 2010 OWA Blocks attachments
Note this is for Outlook Web Access, for Outlook CLICK HERE KB ID 0000088 Problem There are certain reasons that OWA blocks particular file extensions, this is a good thing and I DO NOT RECOMMEND you change those settings, however there are situations where you need to, if you have to do this, I strongly suggest you change things back to how they are set up by default when you are finished. The error message you will see when OWA has...
Your Out of Office Settings cannot be displayed
KB ID 0000197 Dtd 04/03/10 Problem Seen on Outlook 2007 and Outlook 2010 talking to Exchange 2007 (Note this fixes Outlook 2007 but NOT 2010.) When opening the “Out Of Office Assistant.” Your Out of Office Settings cannot be displayed, because the Server is currently unavailable. Try Again Later Other Symtoms 1. You see hash marks in the Scheduling Assistant. 2. You see “Object reference not set to an instance of an...
Exchange 2010 – Blank OWA Page?
KB ID 0000429 Problem When trying to access Outlook Web App (or Outlook Web Access for those used to earlier versions of Exchange), you see a blank white page and nothing else. The certificate and IIS works but no OWA. Solution This is usually due to an exchange pre-requisite that is missing, or one of them is not working. 1. Launch the Exchange Management Shell, (Start > All Programs > Microsoft Exchange Server 2010 >...
Exchange 2010 – Working with Certificates
KB ID 0000453 Problem Exchange 2010 installs with it’s own (self signed) certificate. To stay free of security errors and warnings, the best bet is to purchase a “publicly signed” digital certificate and use that. The following process uses the Exchange Management console to create a CSR (Certificate Signing Request). Then what to do with the certificate, when it has been sent back to you. Solution Certificate...
Exchange – Redirect OWA (HTTP to HTTPS)
KB ID 0000697 Problem Out of the box, Exchange (quite rightly) secures Outlook Web Access so that you have to access it via https. The problem is some of your users are used to accessing websites via http, (or simply typing a URL in their browser, without typing any prefix, so it defaults to http). If you try and access OWA via http://server.domain.com/owa.. There are a number of ways to get round this, the simplest is to redirect...