Month: January 2017

New installed Outlook 2016 cannot log on to Office365 Mailbox

After installing an fresh copy of Outlook 2016 and trying to connect to an Office 365 mailbox the following error messages pop up:

Outlook cannot log on. Verify you are connected to the network and are using the proper server and
mailbox name. The Microsoft Exchange information service in your profile is missing required
information. Modify your profile to ensure that you are using the correct Microsoft Exchange
information service.

This seems to be an issue with Windows 10 and autodiscover in Office versions 2010 and later. To fix this use the following workaround.

Set the ExcludeHttpsRootDomain registry key on all affected clients to a value of 1.

  1. Open the registry editor
    • Click the start menu and type regedit
  2. Navigate to HKEY_CURRENT_USERSoftwareMicrosoftOfficex.0OutlookAutoDiscover
    • Note – x.0 corresponds to your installed version of Office: Office 2013=15.0, Office 2016=16.0
  3. Change the DWORD: ExcludeHttpsRootDomain to Value: 1
    • If the DWORD doesn’t exist, create it.
  4. Close the registry editor and launch Outlook. Reconfigure the profile.

Ref: https://support.microsoft.com/en-us/kb/2212902

By RZM 0 Comments

Windows 2012R2 Hyper-V Server looses Network connectivity

Recently I had two Dell Servers running Hyper-V on Windows 2012R2 that would loose network connectivity on a more less regular bases. All available NIC’s were teamed as all VM’s were still running and could connect to each other. However, there was no outbound or inbound traffic to the actual Hyper-V host (ping the subnets gateway fails). Both servers had Broadcom NetXtreme 1-gigabit network adapters that use the b57nd60a.sys driver in version 16.2. Apparently, this is a known issue with Broadcom NetXtreme 1-gigabit network adapters that use the b57nd60a.sys driver, when VMQ is enabled on the network adapter. (By default, VMQ is enabled by the Broadcom network driver.)

This issue is resolved in Broadcom driver b57nd60a.sys version 16.8 and newer. This mean one way of solving the problem is to upgrade the driver to version > 16.8. However, this will require some downtime in a maintenance windows and ultimately this should be scheduled.

To fix the issue in a running production environment the VMQ can be simply disabled running a PowerShell command.

First lets have a look at what the current settings are fro all installed NIC’s by running the following PowerShell command:

[codesyntax lang=”powershell”]

Get-NetAdapterVmq –Name "*" | Where-Object -FilterScript { $_.Enabled }

[/codesyntax]

This will list all VMQ capable network adapters where VMQ is enabled.

To get around this issues without updating the drivers we can disabling VMQ on each affected Broadcom network adapter by using the Set-NetAdapterVmq Windows PowerShell command.

In our case we have 5 and need to run the following:

Set-NetAdapterVmq -Name “NIC1” -Enabled $False
Set-NetAdapterVmq -Name “NIC2” -Enabled $False
Set-NetAdapterVmq -Name “NIC3” -Enabled $False
Set-NetAdapterVmq -Name “NIC4” -Enabled $False
Set-NetAdapterVmq -Name “TRN-HYP-01″ -Enabled $False

Once done lets verity that VMQ is disabled on all of the above network adapters. Running

[codesyntax lang=”powershell”]

Get-NetAdapterVmq –Name "*" | Where-Object -FilterScript { $_.Enabled }

[/codesyntax]

should return nothing as we have have no NIC’s left with VMQ enabled. Running the next command will list all network adapters with there current settings.

[codesyntax lang=”powershell”]

Get-NetAdapterVmq –Name "*"

[/codesyntax]

By RZM 0 Comments
Send a Message