Thursday, June 1, 2017

Issue : The Content Index catalog on all Server copies shows as failed.
Server : Exchange 2013 RTM

Fix : Required AD group was missed while ADPrep ran, to setup all Groups "Content Submitters", 

1. Active Directory Users & Computer > Create a "Security Enabled Group" in Exchange Group
2. Properties of "Group" > Security Tab >Allow "Administrators" & "NetworkService" Accounts "Full Control"
or from Powershell
Add-ADPermission -Identity "ContentSubmitters" -User “Network Service” -Access Rights GenericAllAdd-ADPermission -Identity "ContentSubmitters" -User “Administrators” -Access Rights GenericAll

3. Force or wait Active directory Replication

4. Stop "Microsoft Exchange Search" & "Microsoft Exchange Search Host Controller" on Mbx Server

5. Delete "Content Index" wrt to the Database
6. Restart "Microsoft Exchange Search" & "Microsoft Exchange Search Host Controller" on Mbx Server

Reference : MS KB

Uneditted : Outlook Hangs after migration Office 365 (cloud)

Outlook hangs after Mailbox migrated to Microsoft Cloud (Office 365)


https://blogs.msdn.microsoft.com/modonovan/2015/04/30/outlook-profile-doesnt-resolve-via-autodiscover-for-user-mailbox-moved-to-office-365/


Troubleshooting Steps.
> How many users are facing this issue
 > Outlook Version and update to the latest patch, SP
> Outlook is connected to "Online Mode" or "Cached Mode"
 > Check the Target address of the users from Portal

> Check the "Test Email Auto-Configuration" from Outlook


> Check the  "Connection Status"

> Check the logs in the Outlook Sync folder
> If Outlook is
              been added as Another users Mailbox or using the Shared Calendar
              Cached Mode

> How to disable "Cache Mode"
  1. On the File tab, click Account Settings in the Account Settings list.
  2. In the Account Settings dialog box, click the E-mail tab and then double-click your Microsoft Exchange Server account.
  3. In the Change Account dialog box, click More Settings.
  4. In the Microsoft Exchange dialog box, click the Advanced tab.
  5. Click to clear the Download shared folders check box.

> Then
Action >

> On the problematic machine, logging to check the if the issue is with the Office Portal like License
from this link https://portal.office.com/support/help.aspx?sid=sara#/

> how to check the Outlook Version





  • Start Outlook.
  • On the Help menu, click About Microsoft Office Outlook.
  • Verify the version information and the build number to determine the version of Outlook that is installed on your computer.

  • > Remove AutoMapping, use the MS Support article to AutoMap

    > Download the OffCat software on the client Machine

    > Enable outlook Troubleshooting Log

    > Simple test would be, can the user, via their web browser, access these autodiscover end points?

    > Perhaps their proxy server is preventing access to one of them e.g. *.outlook.com. 

    >to disable SCP i.e. just add ExcludeScpLookup as Dword and set to 1

    >Fiddler is a great friend.



    Autodiscover
    =============



    Tuesday, May 30, 2017

    Enable modern authentication for Office 2013 clients

    Enable modern authentication for Office 2013 clients

    REGISTRY KEY
    TYPE
    VALUE
    HKCU\SOFTWARE\Microsoft\Office\15.0\Common\Identity\EnableADAL
    REG_DWORD
    1
    HKCU\SOFTWARE\Microsoft\Office\15.0\Common\Identity\Version
    REG_DWORD
    1

    Disable modern authentication on devices

    REGISTRY KEY
    TYPE
    VALUE
    HKCU\SOFTWARE\Microsoft\Office\15.0\Common\Identity\EnableADAL
    REG_DWORD
    0

    IMPORTANT: Modern authentication is already enabled for Office 2016 clients, you do not need to set registry keys for Office 2016.


    Article from:
    https://support.office.com/en-us/article/Enable-Modern-Authentication-for-Office-2013-on-Windows-devices-7dc1c01a-090f-4971-9677-f1b192d6c910



    Enable modern authentication in Exchange Online


    1. Connect to Exchange Online PowerShell as shown here.
    2. Run the following command in Exchange Online PowerShell:
      Set-OrganizationConfig -OAuth2ClientProfileEnabled $true
    3. To verify that the change was successful, run the following command in Exchange Online PowerShell:
      Get-OrganizationConfig | Format-Table -Auto Name,OAuth*

    Monday, May 1, 2017

    Scenario :
    Error while running command O365 "Connect-ExchangeOnline.ps1"

    Issue :
    Following Error received

    New-PSSession : [outlook.office365.com] Connecting to remote server outlook.office365.com failed
    with the following error message: The WinRM client cannot process the request. Basic
    authentication is currently disabled in the client configuration. Change the client
    configuration and try the request again. For more information, see the
    about_Remote_Troubleshooting Help topic.
    At C:\Scripts\Connect-ExchangeOnline.ps1:2 char:12
    + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri ht ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New
       -PSSession], PSRemotingTransportException
        + FullyQualifiedErrorId : -2144108321,PSSessionOpenFailed
    Import-PSSession : Cannot validate argument on parameter 'Session'. The argument is null.
    Provide a valid value for the argument, and then try running the command again.
    At C:\Scripts\Connect-ExchangeOnline.ps1:3 char:18
    + Import-PSSession $Session
    +                  ~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Import-PSSession], ParameterBindingValidationExc
       eption
        + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.ImportPSSessionCommand


    Resolution :

    1. Check the Service "Windows Remote Management (WS-Management)

    Get-Service "Windows Remote Management (WS-Management)"
    If this service is stop, Start "WinRM"

    2. From Registry i.e RegEdit.exe

    Locate the following
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client]

    find the Dword, if it is set to "0", Enable it to 1
    "AllowBasic"=dword:00000001