GarthMJ

You and me both, the SW is 18 years old and nothing is supported anymore. Even 2012 is 13+ year old now and nothing is supported either. It just doesn't make any sense.

Just for Clarity, you are looking for a PowerShell script to update each application with a Repair option? What have you tried so far? what is not working for you?

You really want to do this via CI and Not use SW inventory. Once the CI is in place and reporting you can easily create a collection using its results.

How did you change the PW for the default datasource used by ConfigMgr? Did you do something like this? Changing ConfigMgr Report Account Password, How do I do it?

Yes, you can do that. See this post. https://askgarth.com/blog/adding-an-all-option-to-your-prompt/

So just to be clear did you change the default ConfigMgr datasource? if so it will get reset, in the future.

It appears that site (now redacted) is an brain dump site. There are illegal to use. You should only used official testing materials. Measureup for example. https://www.measureup.com/microsoft-practice-test-ai-102-designing-and-implementing-an-azure-ai-solution.html

I was just looking up the logs for you. ClientLocation.log will show you which site you are assigned to. Until that shows at site you will have only two actions. BTW I you ask about what logs, to look at where, this is my go to for logs and what they do. https://learn.microsoft.com/en-us/intune/configmgr/core/plan-design/hierarchy/log-files Glad that you found the issue.

Did you review the logs to see what boundary? Did you trigger the machine policies.

90% of the time if you only see two action on the device, it is because your boundaries are wrong. Are you ONLY using IP Ranges for boundaries? BTW you log file looks fine.

Compliant = The SU has been installed correctly. Non-Compliant = the SU is needed and not installed or not rebooted to complete the install. Compliance State Unknown = The SU scan results have not occurred and therefore the status is unknown.

You should open a support case with Microsoft directly, it is not supported to delete anything within the database like this.

Unless you have any custom reports that you don't have backup for. I would deleted the Db and start over.

You need to extend disk 1 then you can extend your F:.. However, I personally would take the time to clean up all the chop up drives on one VHD per drive letter. I would also look at extending your c Drive and 100GB is on the smaller side.

How are you getting the files to d:\? And yes you can do it and there are no tricks. Do it exactly the same why do do any other program/application. Just make sure your part is correct.

First off how are the files getting to d:\vs? if you are manually putting them their then you are using SMB which is not network aware and there are other ways to get the data within the cache before a user click install. You can run any command you like with ConfigMgr. There are no tricks to this, just enter the execute the command line with the program or application.

Do you have SW inventory enabled? How often is it enabled? What do the log say when you trigger the Heartbeat discovery on the client?

Are those software titles user installed? If so you will not see them within the built in ARP reports. You will need to use 3rd party addon to inventory them. Here is more reading on the subject. https://www.recastsoftware.com/resources/user-installed-software-and-why-you-should-care/

Yes you can do that and there are no tricks to this.

Start with the built in reports, find the one that gives you the closest to what you need and make changes to it.

Just as a note, OU data will get returned to ConfigMgr via Heartbeat discovery. This means by default it will take 7 days or longer for the details to get returned.

No SMSID is not the same as Windows SID. Try running this query. select * from sms_g_system_SYSTEM as g INNER JOIN sms_gh_system_SYSTEM as h on g.ResourceId = h.ResourceId where g.Name <> h.Name

Without looking at the logs, we are guessing but duplicate SMSID, Collection membership rules issues are places to look.

Did you review the log? Did you test the problem using the local system account?

0x87d00213 = Timeout occurred Did you review the log file that you create? did you test this MSI as the local system account? https://www.recastsoftware.com/resources/how-to-access-the-local-system-account/