Exchange 2007 Deployment
The majority of the month has been working on project documentation, hardware requirements, and investigating different archiving solutions.
One of the things that I realized needs more documentation in the messaging community is Public Folders. There really is very little guidance on sizing hardware for dedicated Public Folder servers. Here is what Microsoft has written on Scalability. I know in Exchange 2010 they are being deemphasized even more and Sharepoint is probably a better place for them, but when you have over 8,000 Public folders; I think we might have them for a little while.
One of the issues that has been plaguing the deployment has been that after Exchange Rollup-6 was deployed, Entourage clients were unable to see any messages in the inbox. The client would connect, but no messages were displayed. The rollup-6 rollout was a red herring, which coincided with a server rebuild, and mailbox migration.
After numerous hours of troubleshooting, a call to Microsoft Premier Support was made. Here is what I learned. (thanks Pawan Kapoor!)
It seems that even though all other clients do their authentication on the Client Access Server, but Entourage authenticates and uses ASP.net. on the Mailstore role This means that you will need to add the ASP.net feature along with the integrated and windows authentication features on each mailstore server you deploy.
Here are the two KB articles that the Technician sent to me.
Configuring Authentication in IIS 7.0:
You cannot connect to your mailbox on Exchange Server when you use Entourage for Mac:
Office Communication Server Deployment
The pilot is now in full swing. The adoption rate of this product is astounding.
It is really amazing to see the ease of extemporaneous collaboration that the new R2 release has achieved. Just tonight, I was sitting working on this report, when a colleague asked me to look over a document before he published the final version. I was able to see his desktop inside my Communicator client, make some word change suggestions, point the mouse to where I was referring to, and then being a second set of eyes to verify accuracy, All 131 miles apart. Through on top of that, that we were able to talk over a peer to peer VOIP connection and discuss the changes. This is truly where Unified Communications comes together.
FaxServer Replacement
The hardware named FaxSrv1 was decommissioned, and removed from the data center. The newer hardware formally known as FaxSrv2 was formatted and is currently being reloaded with Windows 2008 Standard on it. There seems to be an issue finding RAID controller drivers, this is where we currently are and looking for alternatives to this dilemma.