UPDATE: Spence posted a great comment pointing out some issues with this post. Richard then restored our Community Server DB to a point in time before the post, so it’s been wiped. Post again, Spence, please, as I didn’t get chance to copy the text of the comment, I’m afraid.
I’ve been meaning to write this up for a while, simply because it’s not quite as straightforward as with Server 2005.
To configure incoming email on SharePoint when running on Server 2008 you’ll need to run through the following steps:
NOTE: We use a wildcard SSL certificate which makes our life much easier when dealing with multiple hostnames. I have not tested this approach with multiple SSL certificates for specific sites.
We were in early today, looking forward to a session on SharePoint with Bill Engolish. Sadly, that was cancelled so Andy and I sat in on the Server 2008 R2 overview session presented by Iain McDonald. That was very interesing, and we learned a bit more about BranchCache. It doesn’t look like it will replace WAN accelerators like Riverbved, because it doesn’t appear to function at their low level. However, it does a similar thing at the file level. The client requests a file from the remote server, which instead replies with hashes. The client PC the requests those hashes from the local cache, improving performance. The cache itself is built on request so does not need to be pre-populated (which is good). I think WAN accelerators have nothing to fear from this, but for smaller organisations or ones which aren’t able to put the accelerators in (perhaps their servers are hosted, for example) BranchCache looks like a very promising technology.
A big thanks to everybody who came to the Server 2008 launch event last week. Andy and myself had a great time presenting to such an enthusiastic crowd. In the end we ran long because of the amount of dialogue around the new features of Server 2008 and I hope everyone went away having got something useful.
