Introduction to Microsoft Small Business Server 2003

A few weeks back, I attended a Microsoft Event which was supposed to provide a technical overview of Microsoft Small Business Server (SBS) 2003. I was a bit disappointed with the quality of the event (and it looks like I wasn’t the only one) but it did at least give me a chance to see SBS, a product to which I have had very little exposure, mostly because my work tends to be with medium and large corporate environments and SBS is aimed at smaller businesses.

Despite its small business focus, SBS does seem to have quite a following and there were clearly many people in the audience with significant experience of the product – some of the links at the end of this post may also be useful for further information.

The principle behind SBS is the provision of an environment which runs on a single server, encompassing many of the facilities which would more typically be spread across a number of servers in a corporate environment, but which remains easy for a small business to deploy and manage. This does cause some complications (e.g. likely resource conflicts from the presence of SQL Server and Exchange Server on the same physical server) and also means that some of the product versions on which SBS is based are not the latest versions available as a standalone product (e.g. ISA Server 2000 – not 2004).

SBS is available in two editions – standard and premium. Both versions have the same base components (Windows Server 2003 Standard Edition, Exchange Server 2003 Standard Edition, Windows SharePoint Services Business Intranet, routing and remote access services, mobile user/device support, remote web workplace, shared network resources, backup/restore and task based management), but the enterprise edition is extended to include ISA Server 2000, SQL Server 2000 and FrontPage 2003.

From a management perspective, SBS is intended to allow a small business to be self-sufficient, with separate Administrator and Power User management consoles allowing easy management of users and computers along with wizards to assist in backing up and restoring data (including monitoring and reporting). Remote access is simplified with a number of wizards and the remote web workplace (http://servername/remote/) whilst intranet creation is handled with the WSS-based business intranet (http://servername/companyweb/), e-mail capabilities are provided through Exchange and enterprise edition users have access to SQL Server databases and improved internet security through ISA Server (SBS standard edition includes the standard Windows Firewall, which may be adequate for many small businesses but might not be flexible enough for others – having said that, I would probably place standard edition behind an Internet router with its own firewall capabilities).

Overall, SBS looks good, but the co-hosting of so many components on a single device (and Microsoft’s deliberate restrictions on scalability) mean that there are many gotchas to watch out for. To find out more, check out the following links:

Making Firefox pretend to be IE (user agent spoofing)

Our corporate intranet doesn’t always play nicely with browsers that it doesn’t recognise. I’ve previously written about making Internet Explorer (IE) 7.0 pretend to be IE 6.0 but today I needed to change the behaviour of Firefox 1.5 to trick the intranet into thinking I’m using IE (I have IE installed, but as its not my default browser, clicking a link in an e-mail, for example, opens in Firefox), thus avoiding messages like the following:

Browser requirements
Internet Explorer 4 (or later) is required
Your current browser, Default 0.0, does not support the features and security requirements of this site

Thankfully, John Bokma’s article on changing the user agent in Firefox answered that question for me and after I’d entered a new general.useragent.override string in my about:config page everything jumped into life. For reference, my original (Firefox) user agent string was:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
and the override (mimicking my Internet Explorer configuration) is:

Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1)

If you want to check your string, there’s a history (including why Microsoft Internet Explorer user agent strings pretend to be Mozilla) and detection script on Dan Tobias’ Web Tips site. Further information (including common user agent strings) can also be found on Wikipedia.

On a slightly different note, whilst I was researching this, I stumbled across an article on how to make Firefox look like Internet Explorer (i.e. visually, not programmatically).