Network Audit and Documentation, CENTREL Solutions Blog

This post has been updated here: https://www.centrel-solutions.com/blog/exchange-online-powershell-window-handle-error While you're here why not check out our  Exchange audit and documentation tool ? If you're using the Exchange Online Management PowerShell cmdlets you may notice that the following error: A window handle must be configured. See https://aka.ms/msal-net-wam#parent-window-handles This error appears in version 3.7.0 (and persists in version 3.7.1) when the following change was made. Integrated WAM (Web Account Manager) in Authentication flows to enhance security. You notice that this error occurs in PowerShell ISE but not in a PowerShell, the issue also appears in any Windows based applications - for example a WinForms application that tries to execute Connect-ExchangeOnline PowerShell ISE A .NET console application does work correctly. .NET console application While you're here why not check out our  Exchange audit and documentation tool ? The error occurs be...

 While you're here - Why not check out our  Group Policy Audit and Documentation Tool ? The "Show recently used files in Quick access" and "Show frequently used folders in Quick access" settings can be found in the Folder Options in Windows. These are user based values and are stored in the following registry values. HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer ShowFrequent (REG_DWORD) ShowRecent (REG_DWORD) Microsoft does not provide a Group Policy ADMX template for these settings however a custom template can be created or a Group Policy registry preference can be used.

When you try and start Windows Admin Center v2 you might find that the "Windows Admin Center" service starts and then stops and the following error is logged in the event viewer. Exception Info: System.Net.Sockets.SocketException (10013): An attempt was made to access a socket in a way forbidden by its access permissions. This maybe because there is another application running on port 443 (the default Windows Admin Center port). You can check this by running the PowerShell cmdlet and note the process identifer (in my case this is running the Hyper-V virtual machine replication service). Get-NetTCPConnection -LocalPort 443|SELECT LocalAddress, OwningProcess Edit the configuration file C:\Program Files\WindowsAdminCenter\Service\appsettings.json And edit the following two locations And... Setting these values to an available port (in this example 8443) and restart the service. While you're here why not check out our  IT documentation tool ?

You might find when you try to copy and paste to or from a VMware workstation virtual machine that it doesn't work on your Windows host machine or that it stops working intermittently. There's a few things you can try... Close and re-open VMware workstation (but select to Run in Background so that your virtual machines are not stopped in the process). This will often resolve the issue. Stop and start the VMware tools service on the guest machine. Reinstall (or upgrade) the VMware tools on the guest. Using a version of VMware tools that is not aligned with the version of VMware Workstation will often cause issues. Reboot the guest machine. Reboot the host machine. While you're here why not check out our  IT documentation tool ?

We've recently had an issue trying to connect to PowerShell remoting on a certain machine. Connections resulted in the following issue: Connecting to remote server machine name failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic. The firewalls (both Windows Firewall and external firewalls) were configured correctly and running  winrm enumerate winrm/config/listener  showed the listener was correctly configured. However, running the following command doesn't show it listening on all IP address...