GarthMJ

One DP for 4500 computer is a lot! The spec is one dp for every 4000 computers. Secondly downloading is generally a boundary issue. Exactly what boundaries are you using? Are we talking apps or packages? Have you reviewed the logs on a problem client?

That download is for CM12 not for CMCB. So ... How exactly are you launching RBA viewer? Where exactly are you getting it from?

What exactly does this mean? What exactly did you set for right?

If you setup RBA correctly, you will only see the collections that you have access too.

The important thing to remember about SW inventory is if the computer hits the 4 hour timeout NO results are sent to CM and stale data will continue to existing within the CM db. You will need to review the inventory agent.log to confirm that it is hitting the 4 hour timeout. This is one of the reason why SW inventory is useless.

if you have two package sharing the same source files then yes it will clean up. and remove SU that don't below to the package. aka the other package. make sure that this isn't the case and everything will be fine.

There is a user voice for it, I would not hold my breath that it will happen anytime soon. As it only has 0 votes. https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/40878685-hardware-inventory-to-collect-certificates

Since Certs are not inventory by ConfigMgr, you will not be able to query on cert templates either.

There are no built in inventory task for Certs and therefore no reports for this either.

Since computer doesn't generally have email address, and there is not simple way to map a user to a computer. This will not be easy. It would be easier for you to create a report to locate user by user name. Like this one. https://www.enhansoftknowledge.com/knowledge-base/locate-computers-by-username/

If you think it is a bug open a support case and microsoft will fix it.

First off SW inventory is NOT reliable, you should be using CI for this. Secondly, if your SW inventory runs for more than 4 hours it will NEVER send up update results. Yes is it very common for SW inventory to run for more than 4 hours runtime (not real time). Third did you review the inventoryagent.log file to see how long it takes for SW? Did it complete? Are you sure?

Well that is the first problem, Windows 10 is NOT supported on SCCM 2012. You need to upgrade to Current Branch.

So Having IP Subnet and AD boundary can cause overlapping boundaries which can casuse problems for site assignment, Why cna the AD and IP subnet boundaries at all? Why are you not use IP Ranges only?

Exactly what boundary type are you using IP Ranges only I hope.

Have you confirmed that the Rules are collecting results on a computer by reviewing the log mtrmgr.log? Until you do this step it doesn't matter how old the rules are.

Has it been 30 days since you created those rules? That report will take time to populate.

When did you create your SW metering rules? if the has been under 30 days, don't expect anything useful for this report and even then you will really need to wait for 60+ days.

First off that report doesn't use HW inventory. It use SW inventory. SW inventory is disabled by default as it is useless. https://www.enhansoft.com/sccm-software-inventory/ Instead use the ARP reports to see what is installed on computers.

To answer your questions directly about one or two SQL instances for WSUS. Is that it will cause conflicts between the two WSUS Servers if they share a db. Aka if some deploys an software update (SU) on WSUS, it will get installed on CM clients too (outside of CM control). From the CM standpoint, CM will change that products and classifications existing within WSUS, including declining SU too. Thereby stopping any WSU deployment of that SU.

You need to give more details. Pen drive of exactly data what data? What is the other WSUS server used for, exactly?

This is very important details that was missing from your first post. How exactly are you updating your existing WSUS server now? Why exactly do you not want to use CM to deploy all SU to all computers? aka why have the second WSUS on the internal network at all?

Is the RAID drivers included within WInPE?

This will not be supported and you WILL have problem when you manage WSUS outside of SCCM for non-SCCM computer. There is NO problem having WSUS installed on the CM server with its own clean db.

Start with a Clean WSUS server using full SQL server.