GarthMJ

When you look on your CAS, do you see the devices? I hope you didn't use the same site code for the new server.

How do you know AD discovery is finding devices? Is the DNS entry correct? Where are you looking at the collection on your CAS? Is your replication healthy?

You should always use v_r_System_Valid. Otherwise you could bu looking at deleted computers too. Take a look at this blog, it also applies to CMCB too. https://www.enhansoft.com/get-the-most-accurate-and-up-to-date-data-using-the-v_r_system_valid-sql-query-in-configuration-manager-2012/

you need to use the count command. SELECT RV.Netbios_Name0 as 'Computer', Count(UP.localPath0) as '# of Profiles' FROM dbo.v_R_System_Valid RV INNER JOIN dbo.v_GS_USER_PROFILE UP ON UP.ResourceID = RV.ResourceID WHERE UP.localPath0 IS NOT NULL GROUP BY RV.Netbios_Name0 ORDER BY RV.Netbios_Name0

First off in AI I would turn ON USB and turn OFF Shortcuts, in any case these have nothing to do with SW inventory. Second, I would review the InventoryAgent.log on any computer to confirm that SW inventory is working. look for the text {00000000-0000-0000-0000-000000000002}. Personally, I would turn off SW inventory altogether as it is useless.

It is document in the CM docs that your site server must be SA within SQL/SSRS. So I don't see this as a problem or issue. Again, it is unclear if you have actually configured SW inventory. Post a screenshot. Again, it is not recommended that SW inv be used and there is no guarantee that it will return results, lots to read here https://www.enhansoft.com/?s=software+inventory

It will not be a permissions issue for SW inv., why because if HW inventory is working then SW inv will work too. So this thread started with SSRS problem and has move the SW inv. so is the SSRS problem fixed? for SW inv, have you confirmed that it is actually being inventoried on a client computer?

If you just configured it, now you have to wait several days for results to show up. However again, keep in mind that I NEVER recommend doing a *.exe. some light reading. https://www.enhansoft.com/?s=software+inventory

Did you configure SW inv? if so exactly what did you configure? aka why do you think it is unhealthy?

You can get the version number from ARP reports too. SW Inv is NOT configured when you first setup CMCB. until it is configured, it will never return anything. aka blank reports.

ok I will bite, Which of the SW inventory reports is useful? You can never know for sure that you are getting full true results with them. Your site server requires full permissions (SA and local Admin) to SQL/SSRS . The error says it doesn't have SA rights. This blog will help you fix that. https://www.enhansoft.com/updated-how-to-create-a-sql-server-computer-account-login/

Look at the report called Count of all instances of software registered with Add or Remove Programs.. this should give you what you want.

When ever you have any problem with report you always need to visit the SSRS website, plus ssrs is faster. to run reports If it is not working there then it is not a SCCM problem. The url is http://<server>/reports normally.

Did you restore or move or your SSRS site? Did you rename the server? if this was a clean setup, did you test SSRS before trying to install the RP?

There is still time to get this month free report giveaway from Enhansoft. https://giveaway.enhansoft.com/ Count of Users and Usage Time by Software Title Problem: There isn’t a built-in SCCM report that can help IT Asset Management (ITAM) Administrators keep track of the number of users that are using specific software titles. Oftentimes ITAM Admins end up creating their own software metering rules for each software title they need information about. They run their monthly reports (generally on the first of the month) and then merge them into another report (usually in Excel or Word) in order to review the data all in one place. Besides having to run all of these reports, ITAM Admins also have another concern. Due to the nature of SCCM, software metering details are only returned once a week, generally on Mondays. How can they be certain that they have all of the software inventory results for the previous month? Is that even possible? This problem was presented to the Enhansoft team. We needed to find a solution not only to help ITAM Administrators, but also to help SCCM Admins guarantee the accuracy of the software inventory results from the previous month. Solution: Count of Users and Usage Time by Software Title Our team reviewed what was needed and felt confident about coming up with a solution given that we’d recently completed a similar challenge. A few months back we re-created a software metering report called, Total Usage Trend Analysis for Collections. We decided to use this report as our base and then added extra columns for details such as: the number of users within each collection and the amount of time each user used a specific application. Next, we answered the question: How can you guarantee the accuracy of the software inventory results from the previous month? The answer turned out to be quite simple. Delay when the report is run. During our research, we determined that you shouldn’t run this type of report on the first of the month. By waiting an extra eight days, or longer, you can always ensure that the software metering details are the ones from the previous month. Simply waiting means that you don’t need to make any changes to your SCCM environment by having software metering data returned daily. We found that even when this data is returned on a daily basis, the results are often not reliable on the first of the month. Why? A number of computers could be turned off, or the results for some computers may not appear depending on the time of day when the report is run. We also concluded that you can run our report months after the software metering data is returned to SCCM and still get accurate results. By default, the previous month will always be selected, but you can simply change the month and year in order to review older data. By the way, our team thought this update would be a, “five-minute fix.” This proved not to be the case, but we think you’ll agree it was well worth it!