Sonus CCE admin guide

https://gallery.technet.microsoft.com/office/Cloud-Connector-Configurati-521b533f

-->

http://www.uclabs.blog/2017/01/cloud-connector-edition-set-automatic.html 

http://www.uclabs.blog/2017/02/tenant-update-time-window-for-cloud.html 

Quickly check user phone assignment in Lync or Skype for Business

Get-CsUser | where {$_.LineURI -eq "tel:+59625431255" -or $_.PrivateLine -eq "tel:+59625431255"} | format-table -property displayname,LineURI,privateline

DPM system state backup error

Type: Consistency check
Status: Failed
Description: DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code:  0x98ED90). (ID 30229 Details: Internal error code: 0x80990ED0)
More information
End time: 06.02.2017 10:24:38
Start time: 06.02.2017 09:18:17
Time elapsed: 01:06:21
Data transferred: -
Cluster node -
Source details: Computer\System Protection
Protection group members: 1
Details
Protection group: Protection Group
Items scanned: 0
Items fixed: 0

in the WBS inside the server we can see it actually corresponds to low space error. indeed we have 12GB free on the drive E: and backup size is 14GB.

As we decide not to touch the drive E: (it is IDE VHD drive on that server, we add new VDHX file attached to SCSI adapter - this way we can alter disk space online. Which is not possible with VHD attached ove IDE interface. You will have to shutdown server and then change.

Now new drive F: can take the load.

go to C:\Program Files\Microsoft Data Protection Manager\DPM\Datasources and in the file PSDataSourceConfig.xml locate E; - drive short in space in section FilesToProtect and replace by F:  new drive.

Rerun consistance check in DPM.

Exchange 2016 onPrem mailbox restore error TooManyMissingItemsPermanentException

Hello, if you get this error

TooManyMissingItemsPermanentException
Error: This mailbox exceeded the maximum number of corrupt or missing items
that were specified for this request.

while running a powershell to restore mailbox from recovery DB:


New-MailboxRestoreRequest -SourceDatabase "RMLB05" -SourceStoreMailbox 86a3500a-53aa-4124-9661-76bab9d2fd15 -TargetMailbox  username@domain.com –TargetRootFolder Recovery -SkipMerging FolderRules 


try to add a switch -BadItemLimit 1000


  

Exchange 2016 VM slow boot and no network after HyperV guest services update or KB3063109

Boot VM in safe mode and set Exchange services start to manual. Then install guest services and once done, restore automatic start.

http://blog.scng.si/exchange-server-vm-becomes-unresponsive-while-updating-hyper-v-integration-services/