ISA 2004 – Updating Firewall Client

With SBS 2003 SP1 Premium, you also get ISA 2004 as an upgrade. A requirement is to uninstall the ISA 2000 Firewall client first. Someone asked whether you could use Group Policy to deploy the new Fireewall Client.


As usual, Chad Gross — our ISA man on the spot — had the answer:


How to Add Firewall Client via Group Policy:
http://msmvps.com/kwsupport/archive/2004/06/06/7670.aspx

If ISA is installed on SBS, then you’re going to want to be able to turn on
auto-detection as well:
http://isatools.org/sbs_wpad_2.zip

Spamcatcher and changing Exchange port

I like it when I learn something new. Recently a user posted the following problem:


I’m trying to install Mailshell’s SpamCatcher, it seems to be a pretty simple setup, there’s not too many variables, but I’m doing something wrong. We have Small Business Server 2000.

For Destination SMTP Server, it asks for Server and Port.  I put in what I thought my server’s name is.  when I clicked Add, Port 25 came up automatically. The description says: “Specify where you want your email routed to.  The proxy will round robin from your list of server entries.”  We only have the one.

Inbound Listening Port also says 25.  The description says: “This specifies the port that the Proxy will listen to for incoming connections.”

When I click Apply, I get the following error message in the event log: Could not bind to port: 25 on address: ALL.
 
 We also run Symantec Mail Security for Exchange.  I’m thinking I maybe should disable this to see if that makes a difference, but I hate to turn this off.  This program finds and filters virus-attachments quite frequently.

Does anyone have any suggestions?


Michael Jenkins answer provided the solution to the problem:


I suggest you change your Exchange port to 6000 (it will now be 25 and in use for exchange) and then set the spamcatcher to point to the servers IP on port 6000 but listen on 25. It looks like you have two apps listening on port 25. This will fail.

In the Exchange smtp service propertis, click advanced and edit the port.

Sharepoint and Full Text Indexing and Searching

With SBS2003 Standard, Sharepoint uses WMSDE. But if you have SBS2003 Premium, and have installed SQL you should consider upgrading your Sharepoint site to SQL. Besides better performance as you add more users, you also gain the ability to enable full text indexing and searching!


Instructions for upgrading Sharepoint to SQL and enabling fulltext search can be found in KB article 837367: http://support.microsoft.com/?kbid=837367

SmartHost and Outgoing Authentication

If you are setting up your SBS 2003 Exchange to send your outgoing email through your ISP, you need to set up your SMTP connector for using Smarthost. Also, many ISP’s now require outgoing verification. Here’s how to do it:


1. Open up Server Mgmt, click on Advanced Mgmt > Exchange > Connectors
2. Right click on SmallBusiness SMTP Connector, and click on Properties
3. Click to enable the option: ‘Forward all mail through this connector to the following smart hosts’
4. In the field below, you can enter either an IP address or your ISP’s outgoing SMPT server name
- If entering an IP address, you must include the square brackets. Example: [12.33.44.1]
- An example of an ISP’s SMTP name is Verizon’s, which is: outgoing.verizon.net
5. Next, click on the Advanced button, then click on Outbound Security
6. Click ti enable basic authentication, then click Modify, and enter the username and password you received from your ISP for sending mail through them.