Blog about messaging and collaboration, mostly Exchange Server and mobile based. Also a hint of snowboarding and kayaking for fun.
An new security notification regarding the ASP.NET vulnerability has been posted, http://www.microsoft.com/technet/security/bulletin/ms10-sep.mspx.
The Exchange team are recommending that you test and deploy this fix for affected servers, http://msexchangeteam.com/archive/2010/09/27/456453.aspx.
In August I blogged about the Hosting Deployment Guide for Exchange Server 2010 SP1 Beta, which was really just an incomplete CHM file.
The Microsoft Hosting Partner Technical Advisor Blog has a new post, Hosted Exchange 2010 Migration Guide. Download the ZIP file to get conceptual architecture, migration overview, migration guidance, HMC specific migration guidance and sample scripts to support your move to an Exchange 2010 SP1 Hosting forest.
You have a few standard requirements and limitations, but you will have to upgrade your control panel or services behind it. You may choose in house development, or join the increasing numbers of hosting providers outsourcing control panels to Ensim or Parallels.
If you missed it Update Rollup 1 for Exchange Server 2007 Service Pack 3 was released last Thursday (09/09/2010) http://support.microsoft.com/kb/2279665.
Download, test and deploy.
I recently rediscovered the Set-MailboxMessageConfiguration cmdlet (http://technet.microsoft.com/en-us/library/dd638117.aspx) which can be used with –SignatureHTML or –SignatureText to set a mailbox signature in OWA/ECP. There are plenty of tools out there to do this, my favourite being Exclaimer Signature Manager (http://www.exclaimer.com/products/outlook-email-signatures/outlook-email-signatures.aspx), but hey we can do this for free.
I created a HTML file for each mailbox with the signature and used PowerShell to set them.
$mailboxes = Get-Mailbox
$mailboxes| foreach {$file= "C:\signatures\" + ($_.alias) + ".html"; Set-MailboxMessageConfiguration -identity $_.alias -SignatureHtml "$(Get-Content -Path $file -ReadCount 0)"}
This is useful for me as I have lots of work on with OWA only organisations at the moment. With the Exchange Server 2010 Hosting Edition (multi-tenant) providers may choose to expose Remote PowerShell so a tenant administrator could run this remotely.
I’m planning to expand this further with a simple WYSIWYG editor hosted on SharePoint to allow the Cobweb marketing department to build or upload a template, a service to pull information from AD and update both OWA and Outlook.
It would be cool to see this type functionality making it in to some SharePoint/ECP hybrid in a future Exchange release.
Microsoft have released the Unified Messaging Troubleshooting Tool which used some new cmdlets to help configure testing and diagnose configuration errors with call answering and voicemail.
Whether the solution is on-premise or cross-premise, use OCS R2 2007 or MCS “14” the cmdlet will emulate and run diagnostic tests in telephone, UM 2010 SP1 and cross-premise deployments. You end up with some useful information in the form of a cause and possible solutions.
Download it here, http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=10d2e48f-0846-40b6-b08f-d282309811a2