Configuring Trend CSM

Thanks to Les for this information!


False positives are not uncommon, but you are getting way too many. I will say that it does take some time to tweak eManager settings for a given environment.

First thing, have you updated your eManager engine and rules ? Do this from within eManager | Update tab – there is an update button. I’m not sure if the automatic update feature is set by default (don’t think so).

On the Anti-Spam tab, I’ve got my settings at High, with action Quarantine. You might select low for the first while, and gradually bring it up as the system is tweaked.

Have a look at the email that is getting blocked, try and find some common patterns – i.e. are they coming from the same domain(s). Use the Approved senders list to add ones that shouldn’t be blocked.

On the Content filter, I have Anti-spam, hoaxes, chainmail, and melissa virus checked (selected) the others are blank. It would seem that one would want to block profanity, racial discrimination, and sexual discrimination, but in my experience the definitions for these are very broad and much mail is blocked :-0.

On the Log Files tab, I have my log files set to daily, with 30 day deletion. Using the log file report, you can see what rule is responsible for blocking every email, and then decide what action should be taken to change the behaviour.

Unfortunately, stopping spam isn’t a set and forget task. The spammers need a good knackering.

Can’t access some web sites

If you or your users are having problems accessing some external web sites, check out these links:


832223 Some DNS Name Queries Are Unsuccessful After You Upgrade Your DNS
Server
http://support.microsoft.com/?id=832223

828731 An External DNS Query May Cause an Error Message in Windows Server
2003
http://support.microsoft.com/?id=828731

828263 DNS query responses do not travel through a firewall in Windows
Server
http://support.microsoft.com/?id=828263


Installing Exchange 2003 SP1

Be sure to install the GZIP patch first:
http://blogs.msdn.com/exchange/archive/2004/05/28/143941.aspx


Then follow Susan’s notes:
http://www.sbslinks.com/exchange.htm


After installing Exchange SP1 you may need to make these changes:
http://www.sbslinks.com/domain.htm


Also, if using RPC over HTTP, be sure to review updated deployment notes that reflect Exchange 2003 SP1:
http://www.microsoft.com/downloads/details.aspx?FamilyID=ef58395d-3710-49cf-9698-938e2bef39e8&DisplayLang=en


http://blogs.msdn.com/exchange/archive/2004/05/28/143941.aspx

How to use Iomega REV disk for backups

The Backup Wizard won’t write to REV drives b/c IOmega set them to look like CDs, and the Wizard looks at whatever that attribute is. NT Backup looks at the drive just fine, though. Since the Wizard actually configures NT Backup, the best workaround to allow you to use the Rev with the Wizard is:

Use the wizard to configure the backup to a hard drive, then open up regedit to:

HKLM\software\microsoft\smallbusinessserver\backup and change the key
“Backup Location Path” to the Rev Drive.


-Eliot

If you have problems joining computer to SBS2003

Built a brand new XP box – joined domain fine… Obviously, problem with old box – seems that what worked fine with W2K may not work so well with SS2k3! Could it be  security issue?  Found MS KB 313222 – applied, didn’t work.

Then found beaut summary by one K. Hollis – many thanks!!!!

 

1.  Change the computer name to “whatever” and then join the PC to the workgroup “WORKGROUP”
2.  Restart the computer and log on locally as the administrator
3.  Make sure the OS has all the latest patches.
4.  Start>Run>mmc> then add “Security Configuration and Analysis” and “Security Templates” snap-ins.
5.  Click on the Security Configuration and Analysis node and follow the instructions on the right to “Create a new database.”
6.  Import the Setup Security Template
7.  Apply the template, reboot

8.  Now try to Join the PC to the new Domain
9.  If you continue to get the error, restart the PC and rerun steps 4-8.

 

Thanks to all who offered suggestions – and no, of course you don’t need to run “connectcomputer” wizard on the ws as suggested when creating new computer accounts; join the domain manually.  Sure, your browser won’t default to companyweb but, heck!

 

Norm Hughes 

Problems with OWA

At the server:
1. Apply 831464
831464 FIX: IIS 6.0 Gzip Compression Corruption Causes Access Violations
http://support.microsoft.com/?id=831464
2. Clear the IIS server files follow these steps:
    a. Go to your %windows%\IIS Temporary Compressed Files directory
    b. Select all of the content in this directory and delete it.
3. Go to a command prompt, type “iisreset”.

At the client:
1. Go to Tools -> Internet Options
2. Select Delete Files and click OK to confirm that you want to delete the
content.

Ray Fong
Microsoft SBS Product Support