Windows Admin Center version 2306 is now generally available!
Published Jun 20 2023 12:38 PM 51.6K Views
Microsoft

Today, we are releasing our latest version of Windows Admin Center – version 2306! Thank you to our customers, partners, and fans for helping us to continue to improve and make Windows Admin Center better.

In this release, we have made improvements across our entire product! From updates to our platform, improving your core tool management experiences, introducing new features, and bridging some of the gap for the legacy tool parity. We hope you will read on and share our excitement for the new features we are introducing this summer. If you’re as excited as we are, you can download right away!

 

Platform updates

 

WDAC support for servers, client, and clusters is now GA

Last year, we introduced the preview for Windows Admin Center to manage WDAC-enforced servers, client machines, and clusters. After hearing your feedback, and making major improvements, we are excited to say that this support is now generally available!

With thousands of new malicious files created every day, traditional methods like antivirus solutions - signature-based detection to fight against malware – only provide one aspect of your defense in depth strategy.

 

In most organizations, information is the most valuable asset. Ensuring that only approved users have access to that information is imperative. However, when a user runs a process, that process typically has the same level of access to data that the user has. As a result, sensitive information could easily be deleted or transmitted out of the organization if a user knowingly or unknowingly runs malicious software.

 

Windows Defender application control (WDAC) can help mitigate many security threats by restricting the applications that users are allowed to run and the code that runs in the System Core (kernel). Application control policies can also block unsigned scripts and MSIs, and restrict Windows PowerShell to run in Constrained Language Mode. Learn more about Application Control for Windows.

Windows Admin Center now fully supports managing servers and clusters with Constrained Language Mode enabled (with the right WDAC policy in place). The experience in Windows Admin Center is no different – simply add your server, client, or cluster and use Windows Admin Center as you always do. Learn more.

 

Trung_Tran_0-1684949114555.png

 

 

Gateway registration and Azure sign-in improvements

In this release, we have improved a few scenarios with Windows Admin Center registration and Azure sign-in experiences, including fixing an issue with stale registration and sign-in data in the Azure Stack HCI registration workflow. We also added a longer delay between the creation of a new application ID and logging in to Azure to reliably finish gateway registration.

 

Tool updates

 

Improved Hyper-V virtual machine management 

The Hyper-V virtual machine management tool has improved multiple experiences. Our vision is make Hyper-V tool your go to tool to manage your virtual machines!

A few highlights include:

  • Ability to move virtual machine between clusters
  • Ability to move virtual machine with storage
  • Ability to download your VM list with the corresponding properties as a CSV file, so you are able to open and do data analysis to understand the usage of your VMs
  • Ability to pop out a VM’s RDP session, so you don’t have to switch context and leave your current view
  • Configure your un-clustered VM running on a cluster to be highly available

Check it, and let us know what you would like to see next on the virtual machine tool!

 

File editor 

We have heard that convenient file access has been a challenge, especially with .txt or .log files. You are now able to modify these files right here in Windows Admin Center and save your changes without ever having to leave this tool or switch context. Editable files will now have the button "Edit File" lit up under the “Files & file sharing” tool.

 

Trung_Tran_1-1684949399969.png

 

Azure Arc status 

Azure Arc-enabled servers lets you manage Windows and Linux physical servers and virtual machines hosted outside of Azure, using the Azure control plane. Windows Admin Center provides an Azure Arc for servers onboarding experience through our Azure hybrid center. In this update, you do not have to navigate to the Azure Arc for Servers blade in your server settings to view the status of your Azure Arc-enabled machine. There is now a new field on the Overview page that displays your Azure Arc agent status.

 

Trung_Tran_2-1684949444104.png

 

Context menu integration 

Accessibility is a constant priority for Windows Admin Center. We know that some users prefer to use the keyboard instead of the mouse to navigate Windows Admin Center, and that keyboard navigation can occasionally be inconvenient. That is why we’ve added a context menu. The context menu shows the extension actions by pressing the keyboard shortcut Shift+F11. From here, you can quickly perform extension actions and reduce the amount of time you must spend navigating the webpage. While this feature is not available for every extension just yet, we have expanded the context menu integration to cover more tools in this release, including:

  • Local users & groups
  • Certificates
  • Networks
  • Devices
  • Firewall
  • Apps & features
  • Registry

We will continue to roll out the context menu feature to additional extensions to ensure users who prefer keyboard navigation can get their tasks done efficiently.

 

Cluster management 

 

Cluster-aware event viewer

Recently we updated our Events tool for servers with an improved interface to better serve your management needs. We are continuing to invest in the ability to view and analyze the events from your systems in this release with the preview of the Events tool for clusters!


The cluster-aware version of the Events tool collects data from all nodes within a cluster and presents it in a unified interface. You can create, modify workspaces, save, and delete them, and open existing workspaces to pick up right where you left off. In addition to the filters that are present in the Events tool for server, including event sources, levels, and IDs, we have also added a filter to the cluster-aware version of this tool to filter by node in the cluster. We have also improved the tool to better handle larger volumes of data and load results quickly. This interface provides a consistent experience whether you are managing single servers or multi-node clusters.

 

Trung_Tran_0-1687283239052.png

 

Azure Stack HCI Cluster Updates tool

The current updates tool in Windows Admin Center based on Cluster-aware updates (CAU) will continue to be supported for clusters running 22H2 or older. There are several quality fixes to the existing CAU-based updates flow in Windows Admin Center to improve the reliability of this experience. We have now added support to upgrade single node 22H2 Azure Stack HCI clusters as part of this experience.

 

Move a volume to another server

The Volumes tool in Cluster Manager now contains a ‘Move’ button. This enables you to move a volume to another server in the cluster. You can verify which server currently owns the volume by adding the ‘Server’ column to the Inventory table. Learn more.

 

Trung_Tran_7-1684949778769.png

 

Storage Spaces and pools settings 

The Storage Spaces and pools Settings section in Cluster Manager now contains 3 new settings: Status, Health status and Capacity alert threshold. The Status and Health status values can help alert the user of unexpected storage or S2D issues. The Capacity alert threshold dropdown lets the user select a threshold between 50% and 100%. When the storage pool fills to this threshold, a notification will be displayed on the Dashboard.

 

Trung_Tran_8-1684949821179.png

 

Bringing consistency to deploying Azure hybrid services on Azure Stack HCI

Many of the Azure hybrid services offered in Windows Admin Center on-premises are not yet compatible with the Azure Stack HCI operating system. To represent the Azure Stack HCI management experience more accurately, we have made the following changes:

  • We have hidden all Azure hybrid services for server connections except Azure Arc for Servers and Microsoft Defender for Cloud
  • Azure Monitor and Azure Site Recovery have been hidden for Azure Stack HCI cluster connections
  • When you begin the onboarding flow for Azure Arc with an Azure Stack HCI node that is clustered, you will receive a warning explaining that the Azure Arc onboarding should be completed at the cluster level instead of the node level

 

Windows Admin Center in Azure

 

Windows Admin Center in Azure continuously releases new updates monthly, providing you with the latest and greatest that Windows Admin Center has to offer.

 

Check out our release history to see the new features we released every month.

 

AAD Authentication for Azure Stack HCI 

Last year, we introduced Azure AD authentication for Windows Admin Center in Azure for Windows Server machines, but Azure Stack HCI clusters still required you to enter your local administrator credentials for management.

 

We are happy to announce that Azure AD authentication is now supported for Azure Stack HCI clusters too! As long as your Azure AD identity is part of the “Windows Admin Center Administrator Login” role, that’s all you need to start managing your cluster using Windows Admin Center in Azure to manage your cluster. You can:

  • Reduce reliance on local administrator accounts 
  • Get SSO to your Azure Stack HCI cluster
  • Use all the protection and security with Azure AD Conditional Access and Identity Protection that are enforced for the Azure Portal (multifactor authentication, compliant device, user/sign-in risk, and others) to protect your Azure Stack HCI cluster
  • Use Azure RBAC to grant the appropriate access to clusters based on need and remove it when it’s no longer needed 

 

Partner Ecosystem

 

Windows Admin Center was built to be an extensible platform, and we value the contributions of our partners to the Windows Admin Center ecosystem. Several partners, including DataON, Lenovo, and Dell, have updated their extensions since the start of the calendar year.

 

SDK improvements

This release includes improvements and bug fixes that will elevate the developer experience and provide partners with a seamless workflow to develop new extensions. Here are the highlights:

  • SDK updates to address some blocking wac-cli bugs
  • Extension template fix to modify gulp processes
  • Updated extension development documentation

 

Lenovo XClarity Integrator

The Lenovo XClarity Integrator extension has been updated to version 4.3.7. Here is what has changed since our last release:

  • Support for XClarity Administrator 4.0.0
  • Support for the following new hardware:
    • Lenovo ThinkSystem SR630 V3 (7D72, 7D73, 7D74)
    • Lenovo ThinkSystem SR650 V3 (7D75, 7D76, 7D77)
    • Lenovo ThinkSystem SR645 V3 (7D9C, 7D9D)
    • Lenovo ThinkSystem SR665 V3 (7D9A, 7D9B)
  • Support for ThinkAgile MX Best Recipe versions 2301 and 2303
  • Refinement to the account requirements for system update, processor core enablement and call home features
    • An Active Directory domain account that’s also a member of the local Administrators group is required for cluster nodes
    • An Active Directory domain account that's also a member of the local Administrators group, or the built-in administrator is required for non-clustered servers
  • Enhancements to the cluster consistency function for supporting HBA adapter (ThinkSystem 4350) and NIC adapter (Intel E810) and optimizing the HBA and NIC adapters probing logic
  • Fixed the issue where extension failed to test AD users for system update functions and call home function
  • Fixed the issue where extension failed to download system update packages.
  • Added workaround for the system update packages in which the ThinkAgile MX system machine types are missing from the metafiles
  • Added workaround for the Broadcom network adapters with static IP address which sometimes becomes duplicated after the driver update is installed

 

Dell OpenManage Integration

The Dell OpenManage extension has been updated to version 3.1.0. Here are the major changes that this version has:

  • Onboarding Dell SCP policies to Azure Arc for PowerEdge server: Support for Dell Server Configuration Policy (SCP) onboarding to Azure Arc for monitoring server configuration
  • Configuration Recommendation for PowerEdge server: Enables support for configuration compliance and remediation options for 14G and above PowerEdge servers based on Dell Server Configuration Profile policies
  • Single Node HCI cluster feature enablement: Ability to validate and remediate (with manual reboot) single node HCI cluster using HCP policies to ensure that the cluster shows better resiliency and performance, and remains compliant with Dell recommended configurations throughout the life cycle of the HCI cluster. Support for Dell HCI Configuration Policy onboarding to Azure Arc for monitoring cluster configuration
  • Auto-handling BitLocker for server: Enabled support for automatic suspension of BitLocker and resuming back as part of any operation which involves rebooting of the AX node from Dell OpenManage extension running in Azure Stack HCI 22H2 and above
  • Warranty information for server and cluster nodes: Provides information on overall warranty status and entitlements of PowerEdge servers and AX nodes

 

Additional partner extension updates

  • QLogic Fibre Channel QConvergeConsole Extension by Marvell version 2.2.0 - Added Port level driver and firmware statistics display support, target link statistic display support, and “Link Uncorrectable FEC Count” display support in Port and Target USCM statistics
  • DataON MUST version 4.1.0 - Added CAU update parameters to fix updating bugs as well as registration email and alert email checking logic
  • DataON MUST Pro version 3.2.0 - Added CAU update parameters to fix updating bugs as well as registration email and alert email checking logic

 

Download today!

We hope you enjoy this latest update of Windows Admin Center, the various new functionality in preview, and all the extensions now available. Learn more and download today!

 

As always, thanks for your ongoing support, adoption, and feedback. Your contributions through user feedback continue to be vital and valuable to us, helping us prioritize and sequence our investments.

 

Windows Admin Center is continuously evolving and growing as a tool and a platform, and we are beyond thrilled to have you part of our journey.

 

To skill up on Windows Admin Center and Windows Server 2022, check out our Windows Server Hybrid Administrator Certification and other featured Learn courses.

 

Thank you,

Windows Admin Center Team (@servermgmt)

 

 

40 Comments

Thank you @Trung_Tran for Sharing this Great blogpost with the Community :stareyes:

Thanks for sharing :)

 

Happy Azure Stacking!!!

Hi @Trung_Tran ,

I accessed the download link and it is a preview download.
Is the download link correct?
I believe the following download link is correct
https://www.microsoft.com/en-us/evalcenter/evaluate-windows-admin-center

Amazed by this new release! Thanks for all your efforts. Still hope WAC is moved as public project on github. Code changes, issues, ideas and improvements could be requested by PRs from partners, users, OEM and fans of WAC.
I still hope most of the things are PowerShell under the hood, isn't it?


New features in 2306 that are not listed above:
+ ability to set S2D pool warning threshold
Feedback: the threshold should be a free integer, slider see also: Azure Stack HCI Warnung im Windows Admin Center - Storage Pool is running out of capacity – Thomas-K...
Usecase: setting the value manually, result into no visibility of the value set (empty dropdown in WAC).


+ ability to set Cluster-wide Live Migration settings: New Cluster-Wide Control For Virtual Machine Live Migrations In Windows Server and Azure Stack HCI -...

+ Storage Migration for VMs now unlocked (unlike Failover Cluster / Hyper-V MMC require CredSSP)


"Check it, and let us know what you would like to see next on the virtual machine tool!"

 

Thanks for asking, here we go @Trung_Tran  :) Generally speaking the improvements we received in the past 2 years already, are tremendously helpful. Context Menu, Domain Join, Cloning VMs (with a caveat, listed below)

Virtual Machine tool

- faster enumeration of (clustered) VMs. Currently this is my top priority demand from customers to leave failover cluster mmc alone.


- I have heard moving more than one VM (Live or quick migratrion) is not possible, is this true?

https://feedback.azure.com/d365community/idea/08ea5c95-cf2f-ee11-a81c-000d3ae37d1e

- dynamic progress on VM migration (optional column for progress in %, per VM, fetched from Hyper-V MMC)


- ability to edit VM paths for disks, configuration files, smartpage, snapshots

usecase: it could happen that CSV or paths get renamed and it is quite hard to fix this as the Hyper-V config files aren't xml or json based

- when cloning VMs all paths should be respecting the structure and naming of the new VM. I have heard this is not the case.
basepath\vm name\virtual machine + basepath\vm name\virtual hard disks etc
https://feedback.azure.com/d365community/idea/33a9fb51-06ab-ee11-92bc-000d3a037f01

- ability to add scsi controllers and attach virtual disks to a controller for better performance (disk queue)
> https://feedback.azure.com/d365community/idea/08c9fd7b-0eab-ee11-92bc-000d3a037f01

- force turn off (currently only doable via hcsdiag and vm id) - hypervisor competition offers this feature
> https://feedback.azure.com/d365community/idea/33a9fb51-06ab-ee11-92bc-000d3a037f01

 

Clustering

- ability to manage S2D disk and pool operations. some of these possible via Server Manager

   remove volume

   repair volume

   clear metadata of removed / stale devices (Microsoft Script Clear-PhysicalDiskHealthData.ps1)

   Add Disk / remove disk from S2D pool
   Ability to specify Livemigration networks (as in Hyper-V MMC, at best cluster-wide, as with MaxLivemigration count since Sept. 2022)

> https://feedback.azure.com/d365community/idea/4c7960b8-9d2f-ed11-9db0-000d3a1f4287

Volumes / CSVs

   - maintenance mode

   - test failover
   - repair / chkdsk for NTFS volumes (in maintenance mode)
   - see / set description (label) of a volume

   - add / remove disk from CSV
   - (re)name CSV mounting points (with consequences) when turning a disk to a CSV

   - consider formatting CSV volumes with 64k ReFS clustersize (better perf for VM, snapshots, SQL workloads etc)

   - show CSV ReFS Version (column, details)

   - (implemented in 2306) Adding a volume should mount the CSV with the same name in Clusterstorage, and also rename the NTFS / ReFS volume label accordingly

> https://feedback.azure.com/d365community/idea/4c7960b8-9d2f-ed11-9db0-000d3a1f4287

Some of these might be already addressed, as I am currently evaluating the changes of 2306.

Happy clustering / Azure Stacking ;) (like your term @cblackuk1)

Iron Contributor

Thanks  for sharing

Brass Contributor

Thanks for the great sharing from @Trung_Tran and @Karl_Wester-Ebbinghaus_business

 

I've tested in my AzSHCI 22H2 cluster with GPU and found out that GPUs extension doesn't working as per expected. The extension enabled but GPUs blade doesn't on the left panel of the WAC.

 

Currently roll back to 2211 to continue the GPU-P testing.

 

Kindly help to take a look, thanks.

 

Regards,

Kho  

Hi Lien @LCKho3693 unfortunate you haven't discovered this in the preview, but there is Microsoft support available for WAC, if you like to go down that route

Microsoft

Hey @Norio SASHIZAKI, thank you for finding this! I've updated it! :)

Microsoft

THANK YOU SO MUCH @Karl_Wester-Ebbinghaus_business!!

 

I'll work with my team to get you some answers for your questions. I've made a note of the feature requests in your list! :)

 

Looking forward to speaking with you soon! 

Microsoft

Hey @LCKho3693, I've already messaged the owners of the GPU-P tool to let them know. They'll investigate and figure out what's going on. 

Could you please let us know what you're seeing? Are there errors or what exactly isn't working as expected?

Brass Contributor

Hi. 

Great new features in this release!

There is already ClusterPerformanceHistory for cluster metrics like CPU, memory, disk performance etc, but I'm really missing history of disk utilization (% free space). 

Would it be possible to implement this in a future release?

Best regards! 

 

Brass Contributor

Thanks @Trung_Tran , no error when installing the GPUs extension, the issue is the GPUs blade doesn't not appear on WAC panel after installation.  

 

Would it be possible due the conflict of the "preinstalled" and "feeds" extension modules?

 

As it happened before at WAC 2211 on the "Updates" extension. I've to uninstall and reinstall the WAC to resolve the said issue.

 

Best regards.

"history of disk utilization (% free space).  Would it be possible to implement this in a future release?"

Enable Insights and CSV on host level via WAC @Anders Jensen 

@Trung_Tran you're most welcome.


I discovered a quirk that happened for a new feature. ReFS will gain feature to use inline compression 

  • Added post process compression with LZ4 & ZSTD, transparent decompression.
    Windows ReFS versions · GitHub

    The WAC team has released this in preview, which is great.

However since 2306 enabling DeDup and this feature is bundled in one workflow, this breaks to enable Dedup on Windows Server 2022 S2D. I can provide more in detail.

Current state is that one cannot enable dedup on S2D on Windows Server 2022 with WAC 2306 anymore. Also opening the CSV and then settings will result in various related issue due to the missing implementation of Compression when not on Azure Stack HCI (Preview).

 

Secondly,

Same as @LCKho3693 missing GPU-P in the new version, with 2306 on Clustered Hyper-V Hosts when accessing these hosts directly not via the cluster, the "settings" are gone missing on the left navigation pane.

If one searches for "settings" in the search it will appear, same one can access settings using the link /settings in the address bar. Hope you can follow me.

one to add:

I am not sure if this in the scope of WAC but for several versions there is a duplicate on Defender on the installed tab.

When "updating" the 3.0.1 the other one disappeares.

Karl_WesterEbbinghaus_business_0-1687521484349.png

 

Brass Contributor

Thanks @Karl_Wester-Ebbinghaus_business  :smile:

I would like to have the cluster features (CSV etc) visible in the cluster context

 

Regards,

Anders

Certainly, a good point, it might be possible in future to use Server insights data and populate (make them accessible) on cluster level, I agree with your great idea!
> https://feedback.azure.com/d365community/idea/7d98cf5d-10ab-ee11-92bc-000d3a037f01
@Anders Jensen @Anders Jensen 

Copper Contributor

@Trung_Tran Could you clarify this statement "The current updates tool in Windows Admin Center based on Cluster-aware updates (CAU) will continue to be supported for clusters running 22H2 or older."?

 

It sound like some other updates tool than "the current" one is in the works?

 

"Will continue to be supported" usually means "not for very long" - why else would you bring it up?

 

It sort of feels like this section implicitly references some other previous statements that I am not aware of.

 

Otherwise, looks like a good update. I will give it a try.  

Brass Contributor

 

Hi, would be good to have Intent renaming function available when creating networking intent using WAC with Network ATC during AzSHCI deployment.

 

LCKho3693_0-1687701025490.png

 

 

Copper Contributor

Thanks team,

I like to focus one of this feature which related to IAM.

We are unable to see option where we can give access to our client where they can only create VM with limited access.

Cross forest IAM , I am referring here.

A company host  hci infra and B company can create their workload VM with limited access.

Note:ARB still in preview mode

 

 

Iron Contributor

Hello,

 

It is nice to get another release, however, I cannot avoid to notice they are now coming slower and slower, and most features seem to focus only on clustering and Azure Stack HCI (which is welcome, as WAC was years behind decade-old MMC on those topics).
We could use some love on core WAC features and QoL improvements, like :

- Performance improvements when managing large amounts of servers

- Better extension update management (having to restart WAC for each extension update is crazy)

- Finer RBAC management

- Feature parity with Server Manager and other Windows MMC (altough it also depends on extensions)

- ...and many other issues plaguing WAC for years now.

As for Issues · MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback · GitHub, it seems to be devoid of any Product Team feedback for months, if not years.


I'm sure WAC team is trying as hard as they can to make WAC better, while dealing with limited resources - and I salute their hard work. But this is worrying.

 

Does anyone know how to cope with this error when trying to couple WAC 2306 with Azure? 

AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access



K_WesterEbbinghaus_0-1688846077589.png
That's what I found, but it wasn't an issue in the past. Of course my user is protected with MFA, since its the global admin.
https://learn.microsoft.com/en-us/answers/questions/1288552/how-to-fix-the-error-aadsts50076-due-to-...



edit: in fact something changed and onboarding with MFA does not work anymore.
Workaround:
create a user with no specific permissions in AAD

assign a random password

repeat the WAC registration
you will be prompted change password on logon

 

Copper Contributor

Will there ever be any updates to the UI side that allows better organization?  All servers just get dumped into on big bucket on import and there is no way to organize them by site, region, etc.

Copper Contributor

Thanks for the update :smile:
Since the update to 2306 I have a problem. The loading screen gets stuck at "Gathering environment info - this may take a few moments...":

obakuhl_0-1690217812945.png

This only happens in Firefox (regardless of version), Edge works. Is there a plan to fix this problem in Firefox or am i doing something wrong? The WAC versions previously worked without any problems. A new installation does not help, a rollback to 2211 fixes the problem.

Copper Contributor

Same issue here as @obakuhl - on Firefox, regardless of version, the Windows Admin Center gets stuck at "Gathering environment info—this may take a few moments...". Several errors in the console:

 

Cookie “XSRF-TOKEN” has been rejected for invalid domain. 2 <server hostname>.<domain>.local
Welcome to the Windows Admin Center debugging api. Type "MsftSme.help()" to see a list of available commands main.c65ecd813ed83fed7771.js:1:69745
Ignoring unsupported entryTypes: longtask. msftsme.core.3477e099f1994f4ea0fa.js:1:380450
Cookie “XSRF-TOKEN” has been rejected for invalid domain. 4 manifest.json
XML Parsing Error: not well-formed
Location: https://<server hostname>.<domain>.local/manifest.json
Line Number 1, Column 1: manifest.json:1:1
ERROR Error: Uncaught (in promise): TypeError: items is undefined
canActivate@https://<server hostname>.<domain>.local/19.c34c239d4b23fcc3e5c6.js:1:201583
sEIs/setupNavigations/rn</</</</s</<@https://<server hostname>.<domain>.local/vendor.angular.531f041ed66c890d22ca.js:1594:3276
i9xl/s/<@https://<server hostname>.<domain>.local/vendor.rxjs.c384f19b0681895f0df4.js:1:152444
_trySubscribe@https://<server hostname>.<domain>.local/vendor.rxjs.c384f19b0681895f0df4.js:1:85296
subscribe@https://<server hostname>.<domain>.local/vendor.rxjs.c384f19b0681895f0df4.js:1:85104
call@https://<server hostname>.<domain>.local/vendor.rxjs.c384f19b0681895f0df4.js:1:87147
subscribe@https://<server hostname>.<domain>.local/vendor.rxjs.c384f19b0681895f0df4.js:1:84982
s@https://<server hostname>.<domain>.local/vendor.rxjs.c384f19b0681895f0df4.js:1:162440
_innerSub@https://<server hostname>.<domain>.local/vendor.rxjs.c384f19b0681895f0df4.js:1:137601
_tryNext@https://<server hostname>.<domain>.local/vendor.rxjs.c384f19b0681895f0df4.js:1:137494
_next@https://<server hostname>.<domain>.local/vendor.rxjs.c384f19b0681895f0d…
Angular 19
r https://<server hostname>.<domain>.local/runtime.303e4f280a794e1c23a7.js:1
<anonymous> https://<server hostname>.<domain>.local/37.49801bc54d775413f36e.js:1

No problems accessing it through Chrome. I primarily use Firefox and avoid Chrome like the plague - I do not want to change this, so if anyone knows a fix, please let me know.

 

Thanks!

Brass Contributor

I can't get Windows PCs to show up as shared connections.  I can add Servers and Windows PCs as an admin.  The Servers show up for other users under 'Server Manager', but the Windows PC's do not show up for other users under "Computer Management".  And if go back as admin to Shared Connections, I dont see the Windows PCs I just added, only the servers.  Did something break?  

What i know is that the pane adding shared connections will not render correctly after importing files for shared connections. 

Otherwise, if the button "add" for computer shows up they'd also appear in shared connections. Just tested it, and works fine. I can add computers and this computer shows up in settings > shared connection and wac main page "all connection".

Selecting computer management it shows up aswell.
I would suggest to uninstall and reinstall WAC.

Deleted
Not applicable

@995Unknown 
use Firefox Developer Tools to replace "window.location.ancestorOrigins" to "window.location.origin" in the 19.c34c239d4b23fcc3e5c6.js,
and then refresh page.

but, you need to do this process every time when you restart Firefox ...

JimLin_0-1692776279860.pngJimLin_1-1692776287505.pngJimLin_2-1692776296501.pngJimLin_3-1692776307025.pngJimLin_4-1692776311580.png

 

Copper Contributor

@DeletedThanks for figuring that out, it works immediately, but it's just a workaround.

 

@Trung_TranI know Firefox is not officially supported, but why has a change been made so that Firefox no longer works, was that intended?

 

Copper Contributor

@Deleted Thank you for that, worked like a charm! Unbelievable that it's such a simple difference that makes or breaks the page lol. I will find some way to automate this change for future launches of Firefox to make it work well until an official fix is in place (if ever).

 

Thanks again!

 

EDIT: What I did was I looked for the 19*.js script everywhere on the WAC host machine - found it in 3 places:

C:\Program Files\Windows Admin Center\UX.zip

C:\ProgramData\Server Management Experience\Ux

C:\All Users\Server Management Experience\Ux

 

The last one there just takes you to ProgramData, so really only 2 places; find the JS script, change ancestorOrigins to origin and save - unzip, change and rezip the one in Program Files.

 

Now, I am able to close and open Firefox many times and still access WAC remotely. I don't know how permanent this "fix" is - likely with the next module update it will be erased, but its at least one way to ensure persistence between Firefox sessions. Hope this helps someone!

Deleted
Not applicable

$jsPath = 'C:\ProgramData\Server Management Experience\Ux\19.c34c239d4b23fcc3e5c6.js'
(Get-Content $jsPath).replace('window.location.ancestorOrigins', 'window.location.origin') | Set-Content $jsPath

 

$zipPath = 'C:\Program Files\Windows Admin Center\UX.zip'
Compress-Archive -Update $jsPath $zipPath

Copper Contributor

Thanks for this. Can anyone recommend a browser that doesn't do the browser credential prompt AND azure AD prompt if enabled? The docs say some browsers will do this, but never goes further in saying which dont! Both Chrome and Edge seem to do this.

Brass Contributor

@ez12a - have you tried adding the WAC URL to your local intranet zone? It works for AD authentication in Edge. 

Brass Contributor

If you connect to an Azure tenant with certain Azure subscriptions you get a prompt in WAC that the subscription does not support this and that.

Would it be possible to not iterate all subscriptions but just the one selected when onboarding WAC to Azure? Or have a subscription filter in which you can deselect unwanted subscriptions? 

@Anders Jensen Azure Portal has such filtering options but WAC does not seem to use them. I believe you can only narrow it down by proper IAM and Management Groups. 

 

What currently bothers me more is that logon to Azure in WAC is not permanent but rather depending the user / browser session and if another admin launches the gateway webpage of WAC the Azure logon is no more. It is not realistic that each (on-prem) WAC admin also has the permissions to logon WAC to Azure and it should be rather handled like shared connections or using a different method like a service account maintaining the Azure connection.

Copper Contributor

Thanks for sharing the new features with this release! :)

Copper Contributor

Hi @Trung_Tran 

Could you confirm what version number should show in add/remove programs when 2306 is installed? I'm seeing 1.5.6593.0. But when I launch WAC and click the "?" I see version "2306", then "build 1.5.2306.14001".

 

I'm only asking because our vulnerability scanner is flagging my installed version 1.5.6593.0 as has a critical CVE-2019-0813. Yet uninstalling and re-installing WAC returns the same version in add/remove programs. Can you advise please?

Copper Contributor

For anyone that's just updated to the '2311' version, the new name of the file that needs to be updated is: 709.3d1a3a6ad99e5cc6.js

So your script's first line needs to be updated to the following path: $jsPath = 'C:\ProgramData\Server Management Experience\Ux\709.3d1a3a6ad99e5cc6.js'

@DrKrieger is this in regard to the CVE? 

Copper Contributor

@Karl_Wester-Ebbinghausmy post was in regards to the issue of Firefox hangs at 'gathering environment info'.

Since WAC just updated to 2311, I figured I'd post the filename that needs to be tweaked in order for you to be able to administrate WAC via Firefox. :)

Version history
Last update:
‎Nov 09 2023 11:10 AM
Updated by: