04 Dec 2007 06:34:41 pm
When you re-partner Cisco Unity 5.x with your Exchange 2007 mailbox server the reconfiguration guide states that a PowerShell script, Ex2k7Script_<servername>.ps1 should be created. However when doing a re-partner this weekend this script was never created nor could I find any documentation about what the script is and what it does.
If you find this page because you run into the same issue you should first contact Cisco TAC. If the script is not created there is probably a reason for it (in our case I’m assuming because the objects were already created). But so you have some background information the script creates 3 user accounts with the New-Mailbox commandlet; the 'Unity_NAME01' account, the 'USbms_NAME01' account and the 'EAdminXXXXXX' account (that’s it). So check to see if these accounts already exist and have mailboxes on your Exchange 2007 mailbox server.
07 Dec 2007 06:01:36 pm
I’ve seen quite a few articles lately talking about SCR and referring to it (or putting it in the same bucket as) High-Availability solutions. Even Microsoft has done this with some of their documentation (i.e. http://technet.microsoft.com/en-us/library/bb676571.aspx). Yes if you delve deeper into the documentation you’ll see that they refer to SCR as a ‘resilience’ feature (which is much more accurate) however I don’t think a lot of their customers are receiving or understanding this message.
Because of this I’ve actually run into several customers who were “waiting for SP1 to be released” because they wanted to build “highly available solutions” (obviously this was prior to its release last week).
SP1 does introduce one multi-site high-availability “feature”, and that is support for Server 2008 (due to be released Q1 '08 ). Server 2008 adds in MSCS support for multi-site clustering so you could extend your CCR Cluster across the WAN*, but this is really a Server 2008 feature and not so much an Exchange 2007 SP1 feature. If this is what those customers are after they need to be waiting for Server 2008!
That said why do I say it’s not a “High-Availability” feature, a couple of very important reasons:
• It requires manual ‘failover’ to your standby server
• Legacy Outlook clients (i.e. Outlook 2003) will not automatically reconnect to the standby server, they would need to have their profile updated
So, if you want High Availability continue use of your CCR and SCC clusters for mailboxes. If you want Disaster Recover/Resiliency look into SCR.
*There are some caveats here with a CCR or SCC cluster in Exchange 2007, for example they must be part of the same AD Site.