Either that or the Connect-viserver cmdlet will also take a credential object which you can create in a similar way to what i do for the windows one.

The cred file is just for accessing the windows side of the vCenter, it will not help if you are not running the script as a user with credentials to the vCenter itself, if this is the case you will need to adjust the connect-viserver statement in the script to add a -user and -password parameter.

With VMware vCenter 4.0 we can now disable alarm actions per host.
Very easy during installation or patching, to prevent alarm actions from firing.
But it is also very easy to forget to enable the alarms again, after maintenance is done.

Added 2 sections for Hosts and Cluster Alarm Actions:

# —- Cluster Alarm Actions Disabled —-
If ($ClusterAlarmDisabled){
If ($vSphere -eq $true){
Write-CustomOut “..Checking Cluster Alarm Actions status”
$actions = $clusters | get-view | where {$_.AlarmActionsEnabled -eq $False} | Select Name, AlarmActionsEnabled
$clusteralarmsactions = @()
$clusteralarmsactions += $actions
}

If (($clusteralarmsactions | Measure-Object).count -gt 0) {
$MyReport += Get-CustomHeader “1″ “Cluster(s) with Alarm Actions Disabled”
$MyReport += Get-HTMLTable $Clusteralarmsactions
$MyReport += Get-CustomHeaderClose
}
}

# —- Host Alarm Actions Disabled —-
If ($HostAlarmDisabled){
If ($vSphere -eq $true){
Write-CustomOut “..Checking Host Alarm Actions status”
$actions = $VMH | get-view | where {$_.AlarmActionsEnabled -eq $False} | Select Name, @{N=”Cluster”;E={get-vmhost -name $_.name | get-cluster}}, AlarmActionsEnabled
$hostsalarmsactions = @()
$hostsalarmsactions += $actions
}

If (($hostsalarmsactions | Measure-Object).count -gt 0) {
$MyReport += Get-CustomHeader “1″ “Host(s) with Alarm Actions Disabled”
$MyReport += Get-HTMLTable $hostsalarmsactions
$MyReport += Get-CustomHeaderClose
}
}