Domain Commander: March 2015

Alternative to Changing an Executive's outgoing CID

Rather than changing our Executive Director's caller ID on outgoing calls or setting this user's personal operator an alternate approach I went with here is to use an inbound translation rule on the dial plan applied to the SIP trunk. If someone internal tries to call our Executive Director's DID they reach her as normal, but if she is dialed by someone external to our organisation the caller is connected to a response group containing the person or persons who you would normally set as the executive's personal operator.

New SANs Build

Custom built two new NAS/SANs. 16 x 4 TB SATA3 drives in RAID 10 ZFS, 64 GB of RAM, 4 hot swap 750w PSUs, 2 Haswell CPUs, 2 16GB USB3 drives with FreeNAS in read only mode. Attached storage to Xenserver through 2 LACP bonded connections per host and 4 pair LACP bonded connections from each NAS.

Update: We later switch to a Chelsio 10G fiber cards with two ports per card on each device for direct connect between each host and each SAN and used iSCSI multipathing. This yielded extremely better performance than the 4x1Gb nics in LACP.

Script to change Exchange/Lync 2013 User Photos

Can take a command line argument of the user's name otherwise it asks.

Powershell:

 param([String]$UserName)  
 $DefaultPhotoPath = “\\headstart.admin\share\redirect3\”  
   
 if (!$username) {  
   $UserName = "Username"  
   $UserName = Read-Host "Please place photo into" $DefaultPhotoPath"Username\ folder with naming format username.jpg and then type UserName into this script and press enter"  
 }  
 $DefaultPhotoPath = “\\headstart.admin\share\redirect3\” + $UserName + "\"  
 $PhotoPath = $DefaultPhotoPath + $UserName + “.jpg”  
 $photo = ([Byte[]] $(Get-Content -Path $PhotoPath -Encoding Byte -ReadCount 0))  
 Remove-UserPhoto $UserName -Confirm:$False  
 Set-UserPhoto -Identity $UserName -PictureData $photo -Confirm:$False  
 #Set-UserPhoto -Identity $UserName -Save -Confirm:$False

Last line commented out because it is no longer needed as of Exchange 2013 CU, CU3 I believe, but it could be an earlier CU. Uncomment if on and older build or if pictures don't actually populate.