Comments for EighTwOne (821)

Comment on Limiting Exchange 2010 Database Cache by Antonio Arienzo the blog | Exchange 2010 Store.exe using up all the available RAM (High Memory Usage ) :

Wed, 30 May 2012 08:49:53 +0000

[...] http://eightwone.com/2010/03/25/limiting-exchange-2010-database-cache/ [...]

Comment on Toolkit by Duck

Duck — Tue, 29 May 2012 20:33:14 +0000

Awesome!!!!

Comment on Thoughts on "VMware Zimbra vs Microsoft Exchange" by mdrooij

mdrooij — Tue, 29 May 2012 13:27:58 +0000

True, but ignoring (3rd party) tools may directly affect time spent on migrating while you could have achieved the same result faster and in a more controlled fashion using proper tooling. The out of the box stuff isn’t always the cream.

Comment on Thoughts on "VMware Zimbra vs Microsoft Exchange" by mohana

mohana — Tue, 29 May 2012 13:13:36 +0000

At the end of the day, Migration is going to be a one-time activity. You don’t want to spend too much on the 3rd party tools. Ofcourse, it is critical and as Zimbra supports this activity, there is nothing to worry.

Comment on Automatic archive creation with Cmdlet Extension Agents by mdrooij

mdrooij — Fri, 25 May 2012 14:24:06 +0000

Identity isn't a parameter to be used with New-Mailbox; Identity is used in Get/Set by ANR (ambigious name resolution) to look up the provided 'identity' value using fields like GUI,DN,DisplayName,UPN,alias, etc. So, what you need to use is the provided Name parameter, e.g. $Name= $provisioningHandler.UserSpecifiedParameters["Name"] I overlooked you are using it for Enable-Mailbox, not New-Mailbox. However, I have a gut feeling it has to do with the reason provided in the earlier reply; could you provide the XML?

Comment on Automatic archive creation with Cmdlet Extension Agents by frdt

frdt — Thu, 24 May 2012 07:33:33 +0000

Hi thanks for your post
I try to enable the same extension with “enable-mailbox” as follow
but I always has the following error
Cannot bind parameter ‘Identity’. Cannot convert the “user.name” value of type
“Microsoft.Exchange.Configuration.Tasks.UserIdParameter” to type
“Microsoft.Exchange.Configuration.Tasks.MailboxIdParameter”.. —>

any idea ?

If($succeeded)
{
$Name= $provisioningHandler.UserSpecifiedParameters["Identity"]
If ((Get-Mailbox $Name).archivedatabase -eq $null)
{
$MailboxDatabase= (Get-Mailbox $Name).database
if($MailboxDatabase -eq “NOM_SYS”){$ArchiveDatabase= “ARCH_MGMT”}
elseif($MailboxDatabase -eq “NOM_SUPPORT_01″){$ArchiveDatabase= “ARCH_MGMT”}
elseif($MailboxDatabase -eq “NOM_MGMT_01″){$ArchiveDatabase= “ARCH_MGMT”}
elseif($MailboxDatabase -eq “NOM_MGMT2_01″){$ArchiveDatabase= “ARCH_MGMT”}
else{$ArchiveDatabase= ( $MailboxDatabase.Name)}
Enable-Mailbox $Name -Archive -ArchiveDatabase $ArchiveDatabase
}
}

Comment on Thoughts on "VMware Zimbra vs Microsoft Exchange" by VMWare Zimbra almejando o mercado do Microsoft Exchange Server « Aldo Alves

VMWare Zimbra almejando o mercado do Microsoft Exchange Server « Aldo Alves — Wed, 16 May 2012 00:17:22 +0000

[...] Artigo: http://eightwone.com/2012/03/21/thoughts-on-vmware-zimbra-vs-microsoft-exchange/ [...]

Comment on Minimum HA Exchange 2010 configuration by SysCo/al

SysCo/al — Mon, 14 May 2012 12:49:41 +0000

If you are creating a CAS array with the FQDN of the cluster node name, your failover will works automatically without any other additional software or DNS changes ! The virtual cluster IP will stay the same, but will balance between the first and the second server (just be sure that the Windows clustering is configured with at least a witness network folder and a shared IP address as ressource).

New-ClientAccessArray –Name “CAS Array” –Fqdn “exchange.domain.com” –Site “Default-First-Site-Name”

Set-MailboxDatabase DatabaseName -RpcClientAccessServer “exchange.domain.com”

Tested, it works !

Regards,

André

Comment on Thoughts on "VMware Zimbra vs Microsoft Exchange" by mdrooij

mdrooij — Sun, 13 May 2012 21:33:44 +0000

There are supported options which don’t require 3rd party tooling. There is 3rd party tooling available designed for migration scenarios. However, most of the times – especially in large co-existence scenarios – costs involved with such tools outweigh (i.e. are cheaper) the costs of a labor-intensive, manual process. Those tools are in no way comparable with the “free” Zimbra functionality you’re referring to.

Comment on Thoughts on "VMware Zimbra vs Microsoft Exchange" by Mohana

Mohana — Sat, 12 May 2012 12:22:21 +0000

Zimbra has migration tools built-in to the admin console at no extra cost. Migration is also very easy for PSTs. More importantly, Zimbra will support migration activity.
However, if you want to migrate from any other solution to MSE, then you would need to buy 3rd party tools…..and more importantly, MS will not support this migration activity.