Microsoft

Another note to self - basically you can use MetaEdit to change the default banner for SMTP so that you aren't advertising to the world what version of Exchange/Windows/etc you are running. I know, I know, security thru obscurity isn't really security since anyone worth a lick in hacking e-mail will just look for the XEXCH50 or X-LINK2STATE keywords returned from EHLO.

My main goal is to put "(NO UCE)" in the banner so legit spammers (yeah right) won't spam my hosts.

http://support.microsoft.com/?kbid=555080

There is also a KB for Windows 2000/Exchange 2000 but I don't have it handy at the moment.
Note to self: Put it in later

Thankfully with Exchange 2003 SP2, the limit goes up to 72GB but I still have quite a few customers that don't want to pony up the dough for the Enterprise edition so they play the 16GB info store dance.

I seem to be referencing this more and more so this is mainly a note for myself:

[snip]

Exchange Server Mailbox Store does not mount when the Mailbox Store database reaches the 16-GB limit
http://support.microsoft.com/kb/828070/

[/snip]

Patch Tuesday today.
A good time to manually sync your WSUS server now that they have been released and get those boxes up to date, at least your test network, before you go hog wild on your production boxes.

Thankfully nothing 'CNN crashing'-worthy this month.

http://www.microsoft.com/technet/security/bulletin/ms05-oct.mspx

Most people won't run into this until they start deploying more 64-bit servers and ASP.NET programs, but I might be running into this issue below on one of my newer 64-bit boxes.

[snip]

64-Bit Components

On a 64-bit version of Microsoft Windows, it is possible to run 32-bit applications using the WOW64 emulator. However, processes can only be 32-bit or 64-bit. You cannot have a process that runs both.

Internet Information Services (IIS) runs as a 64-bit application on 64-bit versions of Windows. The process type of a COM component must match the IIS worker process type. It is possible to run 32-bit components on the 64-bit version of IIS using one of the following solutions:

* Configure the COM component as a COM+ application so that it runs in Dllhost.exe.
* Configure IIS to run 32-bit applications. This option affects all applications on the IIS server. For more information, see Appendix D: Running 32-bit Applications on 64-bit Windows (IIS 6.0) in the IIS Deployment Guide.

It is recommended that you convert your components to 64-bit. In the case of Visual Basic components, this is not possible because there is no 64-bit version of the Visual Basic compiler.

[/snip]

I'm really tempted to apply my workplace but I don't think we're the right fit for the program and/or have the time to devote to it. I would love to have a headstart on the new Exchange though.

http://blogs.technet.com/exchange/archive/2005/10/10/412308.aspx