Digital event: Windows Server Summit on September 16
Discover the latest Windows Server innovations and capabilities. Register now for the Windows Server Summit—your first in-depth look at Windows Server 2022. You’ll come away from this free digital event with a thorough understanding of how to use the newest Windows Server innovations to modernize your IT environment and simplify management. Join us at this digital event to: Get the latest news and announcements about Windows Server 2022. See hybrid infrastructure solutions in action with product demos. Learn how to maximize your existing investments with Azure—the trusted cloud for Windows Server. Get answers to your questions from product experts during the live Q&A. Register now > Windows Server Summit Thursday, September 16, 2021 10:00 AM–11:30 AM Pacific Time
WAC and Azure Hybrid center errors - Couldn't get token
On Edge 91.0.864.41 and Chrome 91.0.4472.77 when navigating to Azure Hybrid page and signing into azure results (after a small delay) in: msft.sme.shell -- AzureService msftsme.core.e0fc3e91008e508b9a82.js:1 logLevel: Error msftsme.core.e0fc3e91008e508b9a82.js:1 timestamp: 2021-06-09T19:40:48.690Z msftsme.core.e0fc3e91008e508b9a82.js:1 message: Couldn't get token. Error: {"errorCode":"token_renewal_error","errorMessage":"Token renewal operation failed due to timeout.","name":"ClientAuthError"} main.3a4857bc60669b47b465.js:1 msft.sme.azure-center -- AzureCenterComponent main.3a4857bc60669b47b465.js:1 logLevel: Error main.3a4857bc60669b47b465.js:1 timestamp: 2021-06-09T19:40:48.728Z main.3a4857bc60669b47b465.js:1 message: Error reading service items: Error: Couldn't get token. Error: {"errorCode":"token_renewal_error","errorMessage":"Token renewal operation failed due to timeout.","name":"ClientAuthError"} In Firefox 89.0 the Azure Hybrid page loads fine but when you select Update Management you get: Type Error Message Unexpected error occurred while detecting Update Management setup: Object reference not set to an instance of an object.Azure AD Authentication (WAC) - unable to assign role other than Default Access
When you turn on Azure authentication and add a user, the documentation states that you should be able to assign them a role; Configuring user access control and permissions | Microsoft Docs "In the Users and groups tab, select Add user. You must assign a gateway user or gateway administrator role for each user/group added." Unfortunately role assignment is not possible as the only role available is "Default Access". The roles "Gateway User" and "Gateway Admin" or any other role for that matter are not there. This results in inability to access WAC using Azure AD authentication as it results in this message: "You are not authorized to access this site. Please contact your administrator." How can Gateway User or Admin roles be assigned when you assign the application to users through Azure - currently they are missing - is this a bug or am I missing a step? Thank you in advance.Deploy and Install Windows Admin Center in an Azure VM
The great thing about Windows Admin Center (WAC) you manage every Windows Server doesn't matter where it is running. You can manage Windows Servers on-prem, in Azure or running at other cloud providers. Now if you want to use Windows Admin Center to manage your virtual machines running in Azure, you can use either an on-prem WAC installation and connecting it using a public IP address or a VPN connection, or you can deploy and install Windows Admin Center in Azure. This blog post will show you how you can deploy and install Windows Admin Center in an Azure virtual machine (VM). Check out my blog post to read more: https://www.thomasmaurer.ch/2019/10/deploy-and-install-windows-admin-center-in-an-azure-vm/
