GarthMJ

I doubt that it still replicating. You need to dig deeper into the error by looking at the logs but you might have to restore you site to before the replication issue occurred.

A collection create at a primary site will ALWAYS be replicated to CAS and any other primary site. So you should always create your collections on your CAS.

I hate to say it but this doesn't answer my questions. It will be faster for me to fix it that keep bounce back and forth. Send me your RDL. I need to know what version of SSRS you have and what you are using to edit the RDL. As an aside and completely self promotion. I wrote a book on reporting that will walk you though all the steps to create great reports. https://www.amazon.com/System-Configuration-Manager-Reporting-Unleashed/dp/0672337789/

Since you have a CAS, all management tasks should occur at the CAS itself and not on the primary site. Depending on how long the CAS/Pri link was down, a full sync might have occurred and as such all of the collections maybe lost.

How exactly are you creating your prompts? Exactly what changes are you making to the main query so that it can be used within the SSRS report? As it sits, you will have problems using it for a report.

Windows 10 pro is fully supported.

Your queries look good.... So what exactly is the problem?

Nice solution.. I just tweeted it out too. :-)

Using UNC connection will mean you are using SNB and therefore there is NO network throttling involved or the ability to use branch cache for this. Therefore it will use 100% of the network connection forcing other applications to not be as responsive. Additionally this will increase your changes of an install failure due to networking issues. I would serious reconsider this particularly if you are install two or more computers on the same network and have branch cache enabled.

Ok, I will byte, why do you want to install it form a UNC, vs downloading it to the cache?

Do you seriously have 450,000 computers? Why are you building a CAS?

This will be a problem with you image. How exactly was it created? Have you confirm that you image is ok.

When you re-push them do you tell the client what site to be assigned to? 90% of the time it is a boundary issue. are you using IP Ranges only? if not exactly what is the IP and subnet mask of the client and What boundaries are you using and which one do you think it should be assigned too?

I have been keeping quite on this thread since I work for Enhansoft but if you have any questions about how our solution works, let me know.

yes, if you plan to use Client push.

First off, you should removed Admin right from end users. Secondly, CM will automatically push out the SU again during the next deployment cycle, default is every 7 days.

Ok, but it is needed. So..... What do you expect?

I would think it was more a duplicate certificate than an issue with the db. Did you look for client with the id of E19C9C5C-5D8C-408D-A4BB-B7BD4A1441A4 ?

First off, I would never inventory all EXEs. This will have problems and give you unreliable results. Secondly, use HW inventory to collect this data. https://www.mnscug.org/blogs/sherry-kissinger/330-internet-explorer-version-information-via-hardware-inventory

Why do you think that there is an issue with SQL?

As long as the folder permissions are correct, there is not reason why they will not show up. Again remember that reports will run faster in web interface. As for your data source it depends, if the report runs then the DS is correct, if it doesn't run then you need to change the DS.

So it is unclear to me, does the C$ share exist or not?

Where exactly is the new folder that you created? if it is not within the ConfigMgr_<sitecode> folder, CM will never see the folder. Also keep in mind that accessing the report will be faster from the web interface vs from the CM console. Additionally, made sure that you are using the CM MS data source for your reports.

I hate to say it but if CSS wants you to have the CLE then they can easily get it for you and send it to you.

First off, why not query SQL directly using PowerShell? This would be far more efficient than accessing any data via WMI.