After you replace the indicated hardware memory module the PRTG ESXi Hardware Status sensor error still does not clear.

If you check in Vcenter under the esxi host -> Monitor -> Hardware Health -> Storage Sensors it lists the message “Memory The physical element is failing”.

To fix go to System Event Log tab and select “RESET EVENT LOG”.

Then refresh the PRTG sensor and it should now return the correct status.

More info on VMware KB article: Warnings in the Hardware Status tab of an ESXi host fail to clear (2061093) - https://kb.vmware.com/s/article/2061093

Azure Application Proxy – Login looping
Office 365 (Azure Application Proxy) Thursday, 30 December 2021 by paul

When trying to access a Azure Application Proxied app the Microsoft login prompted is repeatedly presented to the user and they cannot access the website.

To fix:

  1. Go to Azure Active Directory
  2. Select “App registrations”
  3. Select the affected app
  4. Select “Authentication”
  5. Under “Implicit grant and hybrid flows” tick the boxes:
  6. Save the app
  7. Try to login to the site again

The app should then allow you to access the website after entering your Microsoft credentials.

Azure Enterprise Apps – Unable to update application proxy settings
Office 365 (Azure Application Proxy) Thursday, 30 December 2021 by paul

When trying to change an Enterprise App -> Application Proxy -> External Url to a custom URL it displays the error message “Application proxy settings Unable to update application proxy settings” when trying to save it.

To fix:

  1. Go to Azure Active Directory
  2. Select “App registrations”
  3. Select the affected app
  4. Select “Authentication”
  5. If the domain is the list of URIs then delete it
  6. Save the app
  7. Try to change the External Url again

The app should then allow you to change the External Url and save it.

When running Outlook it displays the error message “We are unable to connect right now. Please check your network and try again later” and does not connect to Exchange Online.

Running the PowerShell command “Get-NetConnectionProfile” returns the following Ipv4Connectivity value:

Name             : ethernet1
InterfaceAlias   : Ethernet
InterfaceIndex   : 10
NetworkCategory  : DomainAuthenticated
IPv4Connectivity : LocalNetwork
IPv6Connectivity : NoTraffic

Issue was due to a problem with the Network Location Awareness (NLA) service being unable to access the URL http://www.msftncsi.com/ncsi.txt or (changed in later Windows 10 builds) http://www.msftconnecttest.com/connecttest.txt

After fixing the connectivity issue (proxy certificate issue) the command then updates the connectivity to:

Name             : ethernet1
InterfaceAlias   : Ethernet
InterfaceIndex   : 10
NetworkCategory  : DomainAuthenticated
IPv4Connectivity : Internet
IPv6Connectivity : NoTraffic

Then when Outlook is run it connects to the Exchange server as expected.

If the client can already access the test URLs then it may be due to network adapter settings.

Running the PowerShell command:

Disable-NetAdapterChecksumOffload -Name "*" -TcpIPv4

Disables the checksum offloading to the network adapter. It applies instantly.

Then running the PowerShell command “Get-NetConnectionProfile” lists the connection connectivity:

IPv4Connectivity : Internet

Then when Outlook is started it connects to the Exchange server as expected.
 

Thanks to https://purepcs.co.uk/kb/microsoft-connection-test-ncsi-and-office-365/ for the Checksum Offload command.

Teams client show devtools
Microsoft (Teams) Tuesday, 14 December 2021 by paul

If you left click on the Teams icon, in the system tray, multiple times (3+) then it changes the menu to show the Chrome devtools for the Electron embedded Chrome browser.

Can be useful tracing how the client is accessing the Internet and where it is download resources from.

Page 1 of 91 (457 Articles) << 1 2 3 4 5  Next >>