Thanks for the replies.

For clarity (apologies for not mentioning) I am querying sys.indexes, following this https://www.dbaservices.com.au/how-to-fix-very-large-msdb-database/

Everything else from that query is showing OK.

Thanks for the quick reply.

There's only one site listed in AD
No subnets have been added to AD
Some subnets have been manually added as SCCM Boundaries (as IP ranges)

I know SCCM has the concept of an actual 'Subnet' for a Boundary, this isn't what I mean.

In this particular environment, they have loads of subnets across the LAN, and the ones that are added in SCCM are as individual /24 IP ranges, even contiguous ones. This is what I've inherited!

PS: Because of this we believe devices are either;

going to the internet for updates if the "go to internet if no boundary group" option is enabled
not installing any updates if the "go to internet if no boundary group" option is disabled

Hi,

Thanks for the quick reply :)

"If so, we just deploy the latest feature update to the client." the problem, at least for us, is Software Center is presenting all Feature Updates and appears to be trying to install them all - if we click 'Install All' in the GUI all feature updates stat spinning into action.

Because of this, deployment runtimes/maintenance windows are being missed, because runtimes are being quadrupled in some cases!

I did still think specific build targeting Device Collections was the answer but just wondered if there was now a more intelligent way built in to the Software Center Client.

Thanks for reply.

That example I gave was a "test" library. Our real libraries have 10s of sub-links which would become really messy really quickly if we promoted them all, because of the vertical scrolling required. Each user will have different libraries they visit the most but what you suggested will apply to all users.

Microsoft dropped a massive ball here by the sounds of it!

OK, so I have built a Server 2019 KMS Host and even this one doesn't accept the 2019 GVLK keys.

Thankfully I found a load of pirated keys online so I'm all good now.

Way to go Microsoft for not allowing your customers to use your own keys!

Any ideas?

This is the error I actually get when trying to install a product key from VAMT:

Should not be this hard in this day and age to import a ****ing product key from Microsoft, to Microsoft.

Any ideas anyone?

Hi,

Thanks for the reply.

This 2016 KMS server is updated to January 2022 CU. Just to confirm, I'm having trouble adding the GVLKs to VAMT, not the CSVLK (I had to add the 2019 ones via slmgr.vbs).

This is the error in VAMT:

You can see 3 keys in the GUI. The first one is Windows 10 Enterprise LTSC 2015 and the second and third keys are the Server 2019 ones. None of these 3 can be added:

As mentioned, I have added the Server 2022 GVLK.

I have now managed to add the 2019 KMS Host key to the KMS Server with slmgr.vbs. Don't know why it wasn't working earlier. But I still cannot add the GVLK.

However the GVLK for Server 2019 can be manually added to a Server 2019 KMS client with slmgr.vbs, and then successfully activates against the 2016 KMS Server. This isn't ideal as I have hundreds of Servers in my estate so was hoping to be able to add them all in the VAMT > select them all > Update product information > right click again > add product key > automatically choose a GVLK.

But that process from VAMT fails because it cannot find a suitable key, because the GVLK is not there.

I have downloaded the "latest" ADK from here https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install and installed only the VAMT component.

By "latest", I mean the Windows 11 one, based on this note: "If your environment has a mix of Windows versions, use the ADK version that matches the latest operating system in your environment."

Weirdly the Server 2022 CSVLK and GVLKs are perfectly fine!

Hi,

Thanks for the reply.

However as I said, I currently only have 2 of the 12 nodes installed, to Server 2019 level, and clustered. So it is a 2 node cluster only.

I am looking to add in the other 10 nodes and was asking if I can put those straight to Server 2022 and add them in to the existing 2019 Cluster, then migrate VMs to these 2022 Servers, evict the 2019 Servers to clean install them to 2022 and add them back to the original cluster.

If I have to add those 10 Servers running 2019, only to then evict them and upgrade 1-by-1 to 2022, that is stupid. I currently don't have enough compute on either of the 2 current cluster nodes to evict even one of them to clean install to 2022.

Thanks, I had started to look at those Cmdlets but how can I determine if the definitions are up to date for example? It just tells me the current version. Is there an online URL / API I can compare against?

Also they seem to apply to Defender AntiVirus? Is that explicit or is it just a generic term for Security Center. I support a dozen different AV vendors so can't write a dozen different things that do basically the same thing!

Also want to interrogate Defender ATP, for things like overall health status and onboarding state etc.