Windows Admin Center not connecting to feeds?

[Greg_E]

I'm fighting a problem with Windows Admin Center (WAC) v2.4.0 that has been going on since I updated to the latest version around a year ago... It will not connect to the two default feeds:

https://aka.ms/sme-extension-feed
https://aka.ms/wac-public-extensions

The server can visit those pages if I open a browser, but nothing ever updates and I can't install any of the optional extensions (DCHP, DNS, AD, etc.).

Anyone have this problem and find a solution to fixing it? I'm thinking I need to just install this on a fresh server and start again. Host for this is Server 2022 updated with each cumulative so should be up to date.

This is one of the pages if I browse to the feed address:

<service xmlns="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xml:base="https://pkgs.dev.azure.com/WindowsAdminCenter/723d1322-c0f7-45a4-9d3e-739a0ac52bca/_packaging/wac-public-extensions/nuget/v2">
<workspace>
<atom:title type="text">Default</atom:title>
<collection href="Packages">
<atom:title type="text">Packages</atom:title>
</collection>
</workspace>
</service>

Should I change the feeds to the dev.azure site?

 

[gregsachs]

Mine shows current version is 2.4.1, and is on the https://aka.ms/wac-public-extensions feed and updates.

 

[Greg_E]

So mine isn't updating either... I guess I need to start fresh on a different server (because I need to move this anyway). I'll probably wait, I'm going to be changing my VMware lab into a Hyper-V lab and I'll get WAC running in my lab to help work with the cluster. Then I can look into getting my production system working properly.

My current production WAC was upgraded from a previous version and was broken since that upgrade.

 

[gregsachs]

So mine isn't updating either... I guess I need to start fresh on a different server (because I need to move this anyway). I'll probably wait, I'm going to be changing my VMware lab into a Hyper-V lab and I'll get WAC running in my lab to help work with the cluster. Then I can look into getting my production system working properly.

My current production WAC was upgraded from a previous version and was broken since that upgrade.

Updating it has been frustrating. I think the key for me was to use the self-signed certificate generated at install.

 

[Greg_E]

I think I remember a gotcha, it hangs during install if you are using RDP to access the machine to install. Tried it on my lab DC through RDP and it hung. I'll get a local kvm connected tomorrow and try again.

 

[Greg_E]

OK, my problem might be solved... It should not be installed on a DC and that's the only machine I have in my lab up right now. I'll have to put up a VM on my XCP-ng system that I use for longer term stuff or get another mini-PC to build a member server that can be up all the time. I'll come back to this when I figure out which direction I want to go, going to be days at this point.

 

[DavidRa]

This is a good time to remind readers that a DC should be dedicated to the role of DC and GC. The only additional services you should consider hosting on a DC are DNS and perhaps DHCP.

Running other services (e.g. as SYSTEM) will end up with your additional services having full access to the entire domain.

 

[Greg_E]

Sadly, after several years of being in preview, no work has been done on the DNS extension, and the DHCP doesn't even load data from either of my servers.

 

[Greg_E]

Also every time it updates the main program, it seems to reset all of the computers it was watching. Had this happen on both lab and production recently and had to go through AD and find everything again.