Friday, February 13, 2009

The Microsoft Windows Server 2003 Scalable Networking Pack release

http://support.microsoft.com/kb/912222

To turn off TCP Chimney by using the Netsh.exe tool, follow these steps:
Click Start, click Run, type cmd, and then click OK.
At the command prompt, type Netsh int ip set chimney DISABLED, and then press ENTER.

Keywords: TCP Chimney

Tuesday, February 10, 2009

Thursday, February 5, 2009

Exchange Server 2003 mailbox store does not mount when the mailbox store database reaches the 16-GB limit

http://support.microsoft.com/kb/828070

Exchange 2007 Store Related Changes and Improvements

http://msexchange.org/tutorials/Exchange-2007-Store-Related-Changes-Improvements.html

Exchange Server 2007 comes in two flavors, a standard edition and an enterprise edition, just like previous versions of Exchange. The Mailbox Server when talking about the Exchange Server 2007 Standard edition supports a total of 5 Storage Groups and 5 databases. Unlike Exchange 2003 and previous versions of Exchange there’s no longer a database storage limit in the standard edition. The Mailbox server in the Exchange 2007 Enterprise edition supports up to 50 Storage groups and a maximum of 50 databases per server. Exchange 2007 allows you to create up to 5 databases in each Storage Group as is the case with Exchange 2003, but best practice is to create 1 database per Storage Group. So why should you have a one to one relationship between storage groups and databases? Well primarily because you’ll be up and running a lot faster considering disaster recovery scenarios, etc.

You may experience slow client performance if the version store runs out of memory in Exchange Server 2003

http://support.microsoft.com/kb/893599

Wednesday, February 4, 2009

How do I move the System Attendant mailbox to another store in exchange 2003

1) Open up adsiedit.msc

2) Connect to the configuration context using the pdc/gc (it should be automatically selected for you when you choose the configuration context)

3) Navigate to Services / Microsoft Exchange / Organisation Name / Administrative Groups / Administrative Group / Servers / Server Name / Microsoft System Attendant

4) Right click on the "Microsoft System Attendant" object and choose properties

5) Choose "HomeMDB" and click edit

6) Change the CN of the mailstore to the one you wish to move the System Attendant into

7) Click ok and exit adsiedit

8) Restart the System Attendant service

9) In Exchange System Manager, right click on the Mailboxes folder of the mailstore that used to house the system attendant and choose "Run Cleanup Agent" (you should see the old System Attendant mailbox turn into a disconnected account ready for purging)

10) Right click on your Exchange Server and choose "Start Mailbox Management Process" (this should force the Exchange system to create the new System Attendant mailbox)

11) Check to make sure the new System Attendant account has been created in the correct mailstore, also open Outlook and attempt to conduct a Free/Busy search in the Calendar, if both of these are fine then you can purge the old System Attendant account

Recipient Update Service Did Not Process All Changes

http://technet.microsoft.com/en-us/library/aa998435.aspx