Hi
I have a monitoring software running on my Exchange 2013 mailbox role servers. The software uses Exchange 2013 cmdlets to report some useful data. Please see a sample script below. Likewise there are couple of scripts which runs periodically (say every 10 mins).
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn$dbs = Get-MailboxDatabase -Server $env:computername -Status
foreach($db in $dbs)
{
$mxcount = (Get-Mailbox -Database $db.name -resultsize unlimited).Count
$fspace = $db.AvailableNewMailboxSpace.ToMB()
$size = $db.DatabaseSize.ToMB()
$name= $db.Identity
$wpid = $db.WorkerProcessId
$mounted = $db.Mounted
$edbpath = $db.EdbFilePath
$replicationtype = $db.ReplicationType
$backupinprogress = $db.BackupInProgress
$mountedonserver = $db.MountedOnServer
$rpcclientaccesssvr = $db.RpcClientAccessServer
Write-Host $name,$size,$fspace,$mounted,$mxcount,$backupinprogress,$replicationtype,$wpid,$mountedonserver,$rpcclientaccesssvr,$edppath -Separator ";"
}
Remove-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn
Whenever these scripts run, the powershell.exe consumes lot of processing power and stays for couple of minutes (< 2 minutes) with 15-35% CPU utilization each.
What is the recommended approach to load the Exchange cmdlets in the above scenario (
Regards
-- Babu