Free/Busy Problems Exchange 2007 and Outlook clients

http://wadingthrough.wordpress.com/2006/07/31/unable-to-clean-local-freebusy-information/

http://forums.msexchange.org/m_1800424559/mpage_1/key_/tm.htm#1800424559

How to reset system folders in Exchange Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;822444

How to reset system folders in Exchange Server 2007
http://technet.microsoft.com/en-us/library/bb331972(EXCHG.80).aspx

Eseutil /Y Copy File Mode on non-Exchange Server

The ability of Eseutil to copy large files is a capability introduced in Exchange Server 2003 that has been imported from ESEFile. The copy file mode is optimized to copy very large files efficiently. You can use the switch to copy a database, streaming file, or log file. However, the mode is not suited as a general purpose copy utility.

You can use the Eseutil /Y switch to copy a database, streaming file, or log file. For best speed and stability, you should run Eseutil /Y from a local command prompt on the copy destination server rather than from an intermediate location

From Server 2

ESEUTIL /Y \\server1\d$\priv1.edb /D\\server2\d$\priv1.edb

NOTE! Don't forget to provide the file name at the destination. Otherwise, you will get an error message.

Copying c:\program files\exchsrvr\mdbdata\priv1.edb to c:\Foldername

FAILURE: CreateFile: Access is denied

Eseutil /D Defragmentation Mode
Eseutil /P Repair Mode
Eseutil /C Restore Mode
Eseutil /R Recovery Mode
Eseutil /G Integrity Mode
Eseutil /M File Dump Mode
Eseutil /K Checksum Mode
Eseutil /Y Copy Mode

To run ESEUTIL on a non-Exchange system, follow these steps:

1. Copy Eseutil.exe, Ese.dll, Jcb.dll, Exosal.dll, and Exchmem.dll from Exchange Server's Exchsrvr\bin folder to a folder on the non-Exchange server.


2. Run the desired ESEUTIL commands against the copied database.

Catch All Exchange 2007

http://catchallagent.codeplex.com

Installing Exchange 2007 - basics

Install Windows 2003 Ent x64

Install all Windows Updates - reboot

Install IIS

Check for more Windows Updates - reboot

Run Exchange 2007 setup.exe

MailFlow Settings - <Your old Exchange 2003 Server Name>

Readiness Check - all green? - click install

click yes - reboot - run the setup.exe again to Get Critical Updates for Exchange 2007

- mine found Update Rollup 9 for Exchange Server 2007 Service Pack 1 (KB970162)

install AdminPack

install Resource ToolKit

reboot

Open IIS - change directory security so that it does not require 128-bit encryption

Open Exhcange MMC - Server Config > Client Access - Properties of OWA

- - set the internal and external URLs - make sure that the S from the https has been removed.

- - The internal one I set for http://servername.domain.net/owa

- - The external one I set for http://owa.publicdomain.com/owa

After this part, you're ready to configure your proxy server to handle the incoming traffic to OWA and direct it to your new Exchange Server.

How to configure anti-spam agents Exchange 2007

Link HERE!

By default,  only the Journaling and Transport Rule agents are installed on the Hub Transport server role. The Anti-Spam Agent must be installed and enabled for you to use the associated transport feature. Only the agents that provide the messaging features that are designed to be deployed inside the organization are installed by default. Agents that are not installed are designed for use in the boundary network on a computer that has the Edge Transport server role installed. To view the agent configuration, run the Get-TransportAgent command in the Exchange Management Shell.

You can install the anti-spam agents on the Hub Transport server role by using the provided Install-AntiSpamAgents.ps1 script. The script is located in the %programfiles%\Microsoft\Exchange Server\Scripts folder. After you run this script, all of the anti-spam agents are installed and enabled, and the Anti-spam tab is available in the Exchange Management Console.

Open Exchange Management Shell

Set-Location "c:\program files\Microsoft\exchange server\scripts"
./install-AntispamAgents.ps1
Restart-Service MSExchangeTransport

Now, go do a Microsoft Update! This will ensure that you're running with the most recent Anti-Spam Filter Updates.

OK - back to Exchange Management Shell

get-TransportConfig

- if you'vge already configured your Intern SMTP Servers to include all of your SMTP servers that this server is going to talk to, then you're good.
- if not, then do the following:

Set-TransportConfig -InternalSMTPServers 10.0.1.10,10.0.1.11

Of course, use the IPs of your actual SMTP servers. :P

NOTE:
For all anti-spam features to work correctly, you must have at least one IP address of an internal SMTP server set on the InternalSMTPServers parameter on the Set-TransportConfig cmdlet. If the Hub Transport server on which you're running the anti-spam features is the only SMTP server in your organization, enter the IP address of that computer.

Of course, use the IPs of your actual SMTP servers. :P

Done

Exchange 2007 - sending out 25 blocked somehow?

Since, I'm using an ISP that blocks incoming ports like 80 and 25, etc., I have to work things a little differently. A friend of mine has a small datacenter and he's allowed me to use his SMTP server as a relay as well as his ISA server for proxying. So, for OWA, my ISA rule is pretty much a default Exchange OWA rule out-of-the-box with the only exception being that it's bridged on the back of the rule to port 81 on my router. Then my router forwards all port 81 traffic to my Exchange server.

Now, for some reason, my ISP also blocks port 25 in and out. Ugh,... I know... a total P.I.T.A.!!!

So, what do I do?

I run all my email through my buddy's SMTP server and Exchange via not just port 25 but also port 26. So, his router forwards all traffic from port 25 to 26 to his SMTP server (just a basic SMTP server and not an Exchange server).

So, as long as your recieving smtp server (in my case, my friend's SMTP server out there on the internet) is configured to recieve from you and it's an smtp server you control outside your network, you can fix this issue.

First - make sure your external smtp server can recieve on both port 25 and 26. And that it will allow relay of your public IP along with the domain name your using.

Then in your exchange server, set your send connector's smart-host to the public ip of that smtp server out there.

There isn't an option in the Exchange MMC to use another port other than 25. So, we will need to use the exchange shell command below:

set-sendconnector -identity "yourwackyconnectorname" -port 26

This will allow your exchange box to send your emails out on port 26 instead of port 25