Tuesday, October 25, 2016

The ACE does not Exist on the Object- Office 365

Yesterday, when i was trying to remove full permission from one of the my online user's mailbox and getting below error "BECAUSE THE ACE DOESN'T EXIST ON THE OBJECT"


Root Cause of the warning is, orphaned SID is pending on the mailbox, which is conflicting with rest all delegate user's permissions.

Solution

Simply we need to remove the SID first, and you have permanently resolved the issue.

Below cmdlet which we can eliminate the things, Get the orphaned SID. Run below cmdlet.

Get-Mailboxpermission -identity abc@domain.com | select user | fl

Run below mentioned command, and remove entry of orphaned SID from User Beta's mailbox.

Remove-Mailboxpermission -identity abc@domain.com -user "SID which we got" -Accessright fullaccess

Once done, we have to give the time for sync to Office 365.

Happy Learning!

Friday, October 21, 2016

Network Assessment Tool-Skype for Business online

We are in cloud era and moving most of technologies into cloud such as Exchange Online, Lync Online aka Skype For Business, Share Point etc. before moving to cloud we have to check some pre-requisite task such as required Network, System Security etc.

In series of assessment tool Microsoft have released a Skype for Business Network Assessment Tool and it is free for public download from here

The Skype for Business Network Assessment Tool provides the ability to perform a simple test of network performance to determine how well the network would perform for a Skype for Business Online call. It’s aimed specifically at testing your connectivity to Skype for Business Online

The tool tests the connection to Microsoft Network Edge by streaming a set of packets to the nearest edge site and back for approximately 20s for a configured number of iterations. The tool reports:

Packet loss
Jitter
Round-trip latency
Reorder packet percentage

Installing and running the tool

First download the tool from here, it will be as zip file you need to unzip the files to directory



We need to use Windows Power Shell the run the tool from any of the computer such as Windows 7 etc.

Before we run this we have to have familiar with the configuration file that sets up the options for the tool to run.

The configuration file is called “NetworkAssessmentTool.exe.config” and is located in the same directory as the other files. You can edit the file if required. The defaults are as shown below:



Now time to run the tool with using the Power Shell command

now you can check the output from here :



The key configuration components are explained in the following table:

Configuration
Description
If Not Specified
Relay.IP
IP address to reach the relay server. MUST be a valid IP address string.
Tool will fail.
Relay.UDPPort
UDP port to reach the relay server for relay allocations. MAY be omitted if the user wishes to test TCP allocations only. If both UDP and TCP are configured, UDP will be preferred if the relay is reachable via UDP.
If UDP and TCP are not specified, tool will fail. Otherwise, allocate on TCP only.
Relay.TCPPort
TCP port to reach the relay server for relay allocations. MAY be omitted if the user wishes to test UDP allocations only.
If UDP and TCP are not specified, tool will fail. Otherwise, allocate on UDP only.
WMAFilePath
Path to valid WMA file to be used as an audio file for the audio call. File MUST exist and MUST be a WMA file.
Tool will fail.
NumIterations
Number of audio calls to make. These will be made serially (no concurrency).
Takes value of 1.
ResultsFilePath
Location to output the results to. This is typically a tsv or csv. The delimiter is specified by the “Delimiter” setting. The first line of the output describes what each column is.
Results will not be output to a file.
Delimiter
For the output file in “ResultsFilePath” (if specified), this is the separator for each column in the output file.
Takes value of .
IntervalInSeconds
Time to wait between consecutive calls.
Takes value of 5.0s.
WMAOutputFilePath
Path to where the audio received will be written.  If file exists it will be overwritten
Tool will fail.

Configuration

Following is the sample for configuration of the tool:

This the concludes a summary of installing and running the network requirements tool for Skype Online, hope it will help you to analyze the Network requirement for Skype for Business.

Happy Learning!

Thursday, October 20, 2016

VoIP Exchange UM service & Microsoft-diagnostics

This is the best diagnostic log when we troubleshoot voice mail issues, diagnostic log shows Ms-diagnostics which is valuable to look first and see what reason and response is with error id.

Which will give us the way to troubleshoot further, Here are the all error id and reason related to Voice mail.


ErrorId
Header
SIP Request, Response
Reason string
15000
ms-diagnostics
Response
User properties not readable.
15001
ms-diagnostics
Response
Unexpected exception sending to UM.
15002
ms-diagnostics
Response
Unable to determine dial plan.
15003
ms-diagnostics
Response
Dial plan is unknown.
15004
ms-diagnostics
Response
Dial plan has no servers.
15005
ms-diagnostics
Response
UM server 302 with wrong contact count.
15006
ms-diagnostics
Response
UM server sent unexpected 302 response.
15007
ms-diagnostics
Response
UM server did not respond to request.
15008
ms-diagnostics
Response
Routing to UM for Subscriber Access.
15009
ms-diagnostics
Response
Routing to UM for Auto-Attendant.
15010
ms-diagnostics
Response
Routing to UM for voice mail deposit.
15011
ms-diagnostics
Response
Attempting PSTN rerouting.
15012
ms-diagnostics
Response
PSTN re-routing is either not enabled, or not fully configured.
15013
ms-diagnostics
Response
No Hosted Voicemail Policy could be found for the user.
15014
ms-diagnostics
Response
Hosted Voicemail Policy assigned to the user is not fully configured. Destination or Organization might be null.
15015
ms-diagnostics
Response
ExUM Routing Application is in an unexpected state.
15016
ms-diagnostics
Response
Phone number is not properly configured for the AA/SA contact object.
15017
ms-diagnostics
Response
Exchange Server did not respond in time.
15018
ms-diagnostics
Response
Client transaction cancelled before final response from Exchange.
15019
ms-diagnostics
Response
Client transaction terminated before final response from Exchange.
15020
ms-diagnostics
Response
Too many 303 redirects.
15021
ms-diagnostics
Response
No contact header in 303 redirect.
15022
ms-diagnostics
Response
Invalid contact header in 303 redirect.
15023
ms-diagnostics
Response
Re-directing request to the destination in 303.
15024
ms-diagnostics
Response
Unexpected non-audio single-part SDP request targeted to voicemail routing.
15025
ms-diagnostics
Response
Unexpected non-audio multi-part SDP request targeted to voicemail routing.
15026
ms-diagnostics
Response
Unexpected non-audio non-SDP request targeted to voicemail routing.
15027
ms-diagnostics
Response
Unexpected dispatch failure.
15028
ms-diagnostics
Response
Target User is not Um Enabled.
15029
ms-diagnostics
Response
No diagnostic information found.
15030
ms-diagnostics
Response
Failed to route to Exchange Server.
15031
ms-diagnostics
Response
Exchange Server returned invalid redirection response.
15032
ms-diagnostics
Response
Re-directing request to the destination in 302.
15033
ms-diagnostics
Response
Failed to route call from public IM network to Exchange Unified Messaging servers.
15034
ms-diagnostics
Response
Failed to route to Exchange Unified Messaging server.