Thursday, June 1, 2017

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


    Tuesday, November 22, 2016

    lync control panel 2013 "microsoft silverlight is not installed or is blocked by security settings"

    Issue : On Server "Lync 2013", Lync Control panel is showing error "Lync control panel 2013 "Microsoft SilverLight is not installed or is blocked by security settings" on IE

    Resolution :

    Open IE
    > Select "Tools" option from Menu
    > "Internet Options"
    > "Security" Tab
    > Highlight "Internet" from "Select a zone to view or change your security Settings"
    > Customer Level
    > Select "ActiveX Controls and Plug-ins"
    > "Run ActiveX Controls and Plug-ins"
    > Select option "Enable"
    > click "Ok"
    > Apply

    and refresh or reopen CSCP

    Saturday, November 19, 2016

    Fileshare is accessible by IP address not by hostname on Windows server 2008 R2 machine

    Fileshare is accessible by IP address not by hostname on Windows server 2008 R2 machine

    1. On machine, shared folders are accessible on  the machine using self hostname
    2. Shared folder was accessible from the same domain machine
    3. Unable to accessible machine from another client/server using FQDN but was accessible through IP

    Resoultion
    On the machine where the folder was shared, checked the DNS Settings in the NIC card and removed the DNS suffix which was entered a wrong domain in "DNS Suffix for this Connection".

    Friday, September 9, 2016

    Troubleshooting/Logging Exchange 2010 SP3 RU6 issue

    Troubleshooting Exchange 2010 SP3 RU6 issue
    Run following from the command line

    Exchange<2010>-<KB2936871>-x64-en.msp /lxv* <E>:\<RU6InstallLog.log>

    Eg. 2936871 is the number
    Exchange2010-KB2936871-x64-en.msp /lxv* E:\RU6InstallLog.log


    Reference from
    https://technet.microsoft.com/en-us/library/ff772434%28v=exchg.80%29.aspx?f=255&MSPPError=-2147217396

    and
    https://blogs.technet.microsoft.com/exchange/2008/07/08/exchange-2007-managed-services-might-time-out-during-certificate-revocation-checks/

    Resolution: 
    Tried running many times, revoke Security check from the IE and tried opening Microsoft website but site was not opening, it kept circling without any page response/error message.
    Then ran command from the "Command Prompt"

    c:\>Exchange2010-KB2936871-x64-en.msp /lxv* E:\RU6InstallLog.log

     /lxv* is a switch and file name can be change.
    One thing you will notice that after adding swtich in the above RU6 Installation will go slow and finally i was able to resolve the issue


    Event id pasted below were received in the Application Log




    Event ID : Received in the Application Log



    Log Name:      System
    Source:        Microsoft-Windows-WAS
    Date:          9/9/2016 3:20:24 PM
    Event ID:      5002
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MachineName
    Description:
    Application pool 'MSExchangePowerShellAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />
        <EventID Qualifiers="49152">5002</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2016-09-09T09:50:24.000000000Z" />
        <EventRecordID>5716</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>ComputerName</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="AppPoolID">MSExchangePowerShellAppPool</Data>
        <Binary>
        </Binary>
      </EventData>
    </Event>



    Log Name:      Application
    Source:        MsiInstaller
    Date:          9/9/2016 3:55:03 PM
    Event ID:      1024
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          domain\DomainAdmin
    Computer:      MachineName
    Description:
    Product: Microsoft Exchange Server - Update 'Update Rollup 6 for Exchange Server 2010 Service Pack 3 (KB2936871) 14.3.195.1' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1024</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2016-09-09T10:25:03.000000000Z" />
        <EventRecordID>4119</EventRecordID>
        <Channel>Application</Channel>
        <Computer>MachineName</Computer>
        <Security UserID="S-1-5-21-2569593454-2199529718-41506070416-1109" />
      </System>
      <EventData>
        <Data>Microsoft Exchange Server</Data>
        <Data>Update Rollup 6 for Exchange Server 2010 Service Pack 3 (KB2936871) 14.3.195.1</Data>
        <Data>1603</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Binary>7B34393334443145412D424534362D343842312D383834372D4631414632304538393243317D207B33323533393433312D303236432D343637452D393841442D3939333243414334423330347D2031363033</Binary>
      </EventData>
    </Event>












    Resolution in the same series
    event Id 2280 because, re-installed Exchange 2010 Hub role on a different Location so it while installing first time, it registers its custom modules with IIS and for this it makes entries in the IIS root config file i.e. applicationHost.config at this location 
    C:\Windows\System32\inetsrv\config. 

    These enties are made under the <globalmodules> section. 
    You will see one such entry for kerbauth.dll.
      <add name="kerbauth" image="C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll" />

    so replace the location of the current installation file at "Kerbauth" and save the file.

    Log Name:      Application


    Source:        Microsoft-Windows-IIS-W3SVC-WP
    Date:          9/9/2016 3:20:15 PM
    Event ID:      2280
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MachineName
    Description:
    The Module DLL D:\Microsoft\Bin\kerbauth.dll failed to load.  The data is the error.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-IIS-W3SVC-WP" Guid="{670080D9-742A-4187-8D16-41143D1290BD}" EventSourceName="W3SVC-WP" />
        <EventID Qualifiers="49152">2280</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-09-09T09:50:15.000000000Z" />
        <EventRecordID>3999</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer> MachineName</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="ModuleDll">D:\Microsoft\Bin\kerbauth.dll</Data>
        <Binary>7E000000</Binary>
      </EventData>
    </Event>
    Resolution : Change the path in the Application log from the location

    Monday, September 5, 2016

    DataBase Portability

    Exchange 2010
    -------------------
    Moving Mailboxes between DAG (between DAG havn't tested Yet)

    1.  Mailboxes will be offline, since we have to dismount the Database

    Sequence of tasks that need to take place:
    • Dismount mailbox database on old server
    • Run eseutil /MH NAME.edb to confirm you have a clean shutdown.
    • Create new mailbox store on New Exchange server and mount it.
    • Dismount the new mailbox store
    • Manually copy the old database to the new mailbox store database location (make sure it is the same name)
    • Run the following command on new server Set-MailboxDatabase DBNAME -AllowFileRestore:$true
    • Delete the transaction log files and checkpoint files for that database.
    • Mount the store.
    • Finally modify user account settings so user access points to the new mailbox server
      Get-Mailbox -Database OLD_DB | where {$_ObjectClass -NotMatch '(SystemAttendantMailbox|ExOleDbSystemMailbox)'} | Set-Mailbox -Database NEW_DB
    Referenced from
    http://serverfault.com/questions/463104/fastest-way-to-migrate-exchange-2010-mailboxes-to-another-exchange-2010-server-i

    2.Create the databases on the new exchange server and issue mailbox moves to the new database. You can batch it up pretty quickly though in powershell.