I just had to share this one for my fellow Exchange guys. We just finished the MSG205 Microsoft Exchange Server 2007: The Next Generation of Exchange presentation by Terry Myerson of the Exchange team. During his presentation he said (and DO NOT quote this, I am paraphrasing):
“And Public Folders are present in 2007. They will be present in the future versions too.”
Forget the PF controversy for a moment. As he said the above about two people cheered it, followed by a second of silence and then a resounding boo from the entire room. Right now in the presentation on SharePoint 2007 and looking at the technical overview…. can we just let PFs die? I’m sorry if you hired incompetent programmers that designed information management software on top of public folders but its time to get modern.
Update: Thanks for all the emails folks. Glad you're enjoying the updates. Blog comments are off, will remain off till I get back to Orlando with time to moderate them.
Second Tuesday of the month and yup, you've got patches to deploy. It's a pretty nasty month in patchville with real products getting exploited instead of the usual IE problems. This month it's Exchange on the chopping block:
Microsoft Exchange Server does not properly handle the vCal and iCal properties of email messages. Exploitation of this vulnerability may allow a remote, unauthenticated attacker to execute arbitrary code on an Exchange Server. (CVE-2006-0027)
Unauthenticated attacker to execute arbitrary code. Ouch. Check out the Microsoft Security Bulletin Summary for May 2006 and get to patching.
Earlier tonight I was trolling the PSS newsgroups to find some new issues/resolutions to feed into my Exchange wiki. That beast is getting quite a bit of traffic and Google really seems to like sending people there so I figured I ought to write something on the keywords that the people searched for to end up in my wiki. So there I am trolling for ideas and one of my favourite topics is being discussed: IMF. Familar issue (user didn't RTFM, steamrolled Exchange SP2 without removing IMFv1 first) and I was curious to see if the Chinese PSS reps had lost it with these support requests. They lost it alright. Number one on the list of responses to the partners question is a link to....... tada: Vladville.com. My articles have gained enough prominence to be quoted by Microsoft support personnel in a positive light. I immediately proceeded to ask Chris to kiss my MVP ring: "Who yo MVP daddy?"; Poor Chris, now Microsoft can't kill me because I'm in the support food chain. Chris on the other hand is fair game. Watch out for that chair boy!
The release notes for Exchange 2003 SP2 have been updated to reflect the changes in Exchange SP2 in more detail. Judging by the traffic on Vladville.com, I'm sure that both of the guys that read the Release Notes will be extatic to hear about this news. Download updated Exchange 2003 SP2 Notes Joke aside, looks very thorough and each of the subsections is a good Vladville article on Exchange as far as I'm concerned. If you'd like me to explore some of this stuff in more detail please let me know. In the meantime, check out the articles section.
SenderID has been on my plate for quite some time and despite so many objections (by unknowledgeable people who claim it will never work) I've decided to publish an article on how to implement SenderID for your domain. You know how Exchange SP2 includes the ability to drop messages that fail SenderID checks? Well, this is how you actually determine which servers send mail as your domain, how you create the record, how you publish it through DNS. It's a 4 step process that will take you less than two minutes to create: Publishing SenderID records for Exchange SP2 IMFv2 There is also an Inside SBS podcast being recorded as I type this message so give them a listen, I asked Mark and Peter to talk about IMF. 
Leave it to Microsoft to brag about how fast a server can reboot. :) Joke aside, this doesn't seem to be news at all but it has come in my inbox about 50 times over the past few days so here is the summary. Famous Microsoft MVP, Daniel Petri, has produced a knowledge base article 555526 which basically explains that Exchange 2003 SP2 will reboot faster on a domain controller (read: SBS, if you're running Exchange on a DC in any other setup you need help) because Windows will notify Exchange that the box is about to shut down and Exchange services are shut down prior to Windows services (Active Directory) are shut down. This will automatically make your reboots faster. The news here is that Microsoft finally implemented a process that has been used in production servers for years. I have yet to see a production server where Exchange was allowed to shut down on its own - there is always a script that stops Exchange services and then calls for the box shutdown. So if you were freaked out by the reboot performance enhancement and the subsequent KB article, welcome to Exchange system administration :)
I talked about the IMF going to bi-weekly upgrades with Exchange 2003 SP2 and here is the update from the man that was brave enough to kick them around at Barcelona's IT Forum this year:
"Microsoft has informed me that those updates will start appearing on Microsoft Update in mid-December. I’m also told that the Exchange team will be writing about this shortly on their blog and that a Webcast on this subject is scheduled on January 17th."
So keep your eyes on the blog. These are just IMF definition updates but the faster you get the definitions the more spam you can kill. If you want it realtime, you know what will defend your Exchange the best. ;)