GarthMJ

Based on your screenshots alone, your boundaries are like miss configured.

So CM12 runs a local system account. This account will NOT have access to that share. Personally I would create a package/program to this this and deploy that to your DPs. It would take about "two seconds" to do this and would save you a ton of head aches.

Your best bet is to talk to a MS Lic specialist. They can review your environment and give you the cost.

You need to install the CM client on them and make sure that is it working correctly.

I’m willing to bet that you have ~120 computer listed in the unknown column. Therefore 242/(242+120) = ~67% Having unknown computer will affect your compliance numbers.

Hi Everyone, I wanted to let you know that this month's free report giveaway is Patch Compliance Progression by Collection For each PC within a collection, the Patch Compliance Progression by Collection report will provide you with a count of missing software updates (patches) and the last hardware inventory date. The deployed state report parameter allows you to select the deployed state of the software update. The deployed states are: Yes – The effected software update is deployed within your environment No – The effected software update is NOT deployed within your environment Both The status count parameter allows you to select whether or not expired software updates are included in the status count. In ConfigMgr, software updates that are expired are still listed. When complying with standards such as the Payment Card Industry Data Security Standard (PCI DSS), expired software updates should always be excluded from status counts. Yes – Expired software updates are included within the status count No – Expired software updates are NOT included within status count The classification report parameter enables you to select which software update classification to display within the report. The update classifications, listed in order of severity, are: Critical Updates, Security Updates, Definition Updates, Service Packs, Update Roll-ups, Updates, Tools, and Feature Packs. Click here to read more about update classifications. To learn more about it see our website. http://www.enhansoft.com/resources#current-monthly-report

Here is an example on how to limit a query to a collection. http://smsug.ca/blogs/garth_jones/archive/2014/01/13/limiting-a-report-to-a-collection.aspx

Yes you can pick up the ebook from the publisher. http://www.informit.com/store/system-center-configuration-manager-reporting-unleashed-9780672337789

If you are seeing "lagg" issues then you are likely having a network issue between CM12 and your console VM OR WMI performance on either computer.

How much memory does you CM12 Server have? are you Jumpstations Physical or Virtual?

What is a jumpstation? Where is CM12 Site server compared to the jumpstation? Where is your SQL server?

It not just you, I'm not seeing an export button for custom policy. Where re you seeing that?

No you can't export them. You might be able to create a PowerShell script to import the setting for you.

Yes have a remote SQL server is troublesome, hence why I never recommend it. However I doubt that remote SQL is your problem. You will need to give more details to your problem.

There is little difference between CM07 and CM12 with respect the app deployment. What do you mean by Pull? Optional Advertisement??? Pull DP (Branch DPs)???

The reports are always correct. The console can be update to 31 days our of sync but general 1-7 days out of sync.

So unless your CM12 is a single server (aka SQL and Primary site on the same VM) I wouldn't even look at VM snapshots. If they are and you are preforming a full CM12 backup then you are good. I have used this before but there are caveats with clients that you will have to watch out for. Aka force full inventories on all clients.

You might be able to set that be it is complete irrelevant in CM12, clients can only be assigned to Primary site. It has been this way for several version of CM/SMS.

You do know that VM snapshots ae NOT supported as a backup.

I don't know what parameter you are talking about nor do I understand what you mean by your last sentence, can you explain a bit more?

Yes, You can do both.. in a nutshell if the data exists within CM database you can do anything with it.

Clients are always assigned to primary site.

Keep in mind that MW will never be greater than 24hours. If you ever set a MW for these PCs, they will never install anything as the download time is greater than the MW itself. Honestly I would force reboot them at 2pm on Friday afternoon and start the deployment on Monday @ 10am. No client can say they didn't get enough time to install the SU with that much time.

Yes that is a good idea to use Security groups and no it should no re-deploy the application to those computers.

Yes you can delete the zip file. it is not need any more.