SBS – Alert – ‘The following disk has low idle time’
KB ID 0000583 Problem I got this alert forwarded to me, from a client that I’d put in new hard drives for a few week ago. Alert: The following disk has low idle time, which may cause slow response time when reading or writing files to the disk. Disk: {Number} {Drive Letter}: Review the Disk Transfers/sec and % Idle Time counters for the PhysicalDisk performance object. If the Disk Transfers/sec counter is consistently below 150...
SBS – No Incoming Mail ‘421 4.3.2 Service not available’
KB ID 0000803 Problem While testing mail flow on a new SBS 2011 Server, outbound mail worked fine, but no mail would flow in. When I attempted to Telnet in from a remote host this was what I saw; 421 4.3.2 Service not available Connection to host lost. Solution Normally I’d expect to see an error like this if the Exchange ‘Receive Connector’ was misconfigured, (if you’re not using SBS 2011 create a new default...
SBS 2011 Missing Netlogon Share (Post Migration)
KB ID 0000809 Problem Whilst performing an upgrade from SBS 2003 to SBS 2011, I went on-site this morning to be told, “The new server does not have a NETLOGON share!”. As a result the clients who had authenticated to the old server had successfully ran their logon scripts. But the clients who had authenticated to the new server had not. Solution 1. On the original (SBS 2003) server > Start > Run > cmd {Enter}...
OWA (Outlook Web Access) “Red X” Error
KB ID 0000196 Problem Usually seen on IE7 and IE8, when you try and reply to an email you see a red X in the body of the Email window. Solution Option 1: The simplest fix (Exchange 2000/2003 only – Including SBS2003). 1. Go to http://support.microsoft.com/?kbid=911829 and install that hot fix on the server. Note: This also fixes the error where OWA simply says “Loading”. Option 2 : Whilst In OWA 1. Click...
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...