Cannot process argument transformation on parameter 'Identity' running Set-ClientAccessArray

I tried to change FQDN for Client Access Array in Exchange 2010 by running the command:

Set-ClientAccessArray -Identity 'Array Name' -Fqdn and got following error:

Cannot process argument transformation on parameter 'Identity'. Cannot convert value 'Array Name' to type "Microsoft.Exchange.Configuration.Tasks.ClientAccessArrayIdParameter". Error: 'Array Name' is not a valid value for the identity.
...

I double checked the Identity parameter for Client Array.

Get-ClientAccessArray | fl  Identity

Results:

Identity: 'Array Name'

Turns out that Guid should be used in the Set-ClientAccessArray in the Identity field.

ie.

Get-ClientAccessArray | fl  Identity, Guid

Results:

Identity: 'Array Name'
Guid:

Running following command:

Set-ClientAccessArray -Identity -Fqdn

allowed be to change Fqdn for the Client Array.

Certificate for Exchange 2010

When importing certificate using Exchange Management Console (EMC) for POP3 protocol, run EMC on the server you import certificate to.  Otherwise it may lead to POP3 protocol not working properly using SSL (port 995) on remote Exchange server.

Auto discover slowness Outlook 2016

Microsoft has a vague article about it: https://support.microsoft.com/en-us/kb/2212902

From the list of keys they have to our disposal following is to our experience:

·         ExcludeHttpsRootDomain – no affect

ExcludeHttpsAutoDiscoverDomain – no affect

·         ExcludeScpLookup

ExcludeLastKnownGoodURL

After I added ExcludeScpLookup and ExcludeLastKnownGoodURL auto discover started working fast. One of these two keys added to the registry with the value of 1 is the fix of the issue.

Giving Helpdesk Full access to Rooms

Get-MailBox -Resultsize Unlimited | Where-Object {$_.ResourceType -eq "Room"} | Add-MailboxPermission -User Helpdesk -AccessRights FullAccess

Helpdesk - security group name.

Windows 2012 R2 cluster - confusing error message

Following error is found in the cluster log:

000002e4.000016b8::2015/12/16-06:00:51.667 WARN  [QUORUM] Node 1: weight adjustment not performed. Cannot go below weight count 3 in a hybrid configuration with 2+ nodes

This error does not mean that hybrid configuration can't survive weight count going below count 3.  Windows 2012 R2 2 physical node cluster + File Share Witness (FSW) properly surviving failure of one of the physical nodes (therefore having the weight count going to 2).

Exchange Transport Queues at glance

Modified Exchange Transport queue powershell command: displays only queues that have emails in them:

Get-ExchangeServer | ?{$_.serverrole -eq 'HubTransport'} | Get-Queue | Where-Object {$_.MessageCount -ne 0} |Select-Object Identity, DeliveryType, NextHopDomain, MessageCount | Sort-Object MessageCount -Descending

Powershell Tip: how to analyze many text files in the folder

For example, IIS Logs of Exchange CAS servers:

Get-ChildItem | Select-String -Pattern "emailaddress@yourdomain.com"