GarthMJ

There is no tool, you can hire MS to do this for you. Start by reviewing the Client Status and Component status

What does application categories have to do with DPs? If you have to draw this report what would it look like? What would the prompts look like?

The simple answer is no. The long winded answer is: sure, if you put a ton of effort into it. But at that point I would say why not merge the reports for the various WSUS server into one place?

I'm not following you, what are you trying to do? Why do you care about Admin categories?

I'm curious, why you wouldn't do this with AD directly? Why add CM07/CM12 into the mix?

Have you looked at the built-in reports for this information?

That attribute is not collected by default, so you will not be able to create a collection on it. Why question is why do you want to do this?

There is no way to do that. However you can determine what Packages are not on the right DPS. See the built-in reports under Task Sequence - References.

Have you looked at the built-in report under the Software Distribution - Content category?

The last time I checked was for CM07 and you could not have a MW greater than 24 hours and MW would not cross over midnight. To my knowledge nothing has changed in CM12. Nothing will get cut off but the installs they might get delayed for a few hours. aka any that will take longer that 4 hour on Friday night (count down+ reboot time + Install + user countdown) The Saturday MW should allow you to install anything. If not then you have bigger problems.

IMO, your MW are incorrect. You MW should be: Friday should be 20:00 - 23:59 Sat should be 00:00 - 23-59 Sun should be 00:00 - 05:00 I assume that you want the MW from 8pm Friday until 5am Sunday.

try this. http://smsug.ca/blogs/garth_jones/archive/2012/12/31/list-new-cm-clients-within-the-last-14-days.aspx

This error has nothing to do with CM12 it has to do with either your proxy server and how it is configured or how the client proxy setting are configured. I would look at the client proxy setting first. Keep in mind that Proxy setting are user driven and therefore you will need to local at the local system account proxy settings.

I just cut and pasted it.

I just tested the query there is nothing wrong with it, it work perfectly for CM12. The SMS_UpdateComplianceStatus is no exposed via the wizard but is available to be used within your queries.

I would contact the company directly and ask them, it is in their best interest to help you with this.

If you are only using AD boundaries, exactly what subnet (full details) do you have listed within AD Sites and Services.

What exactly have you setup for Boundaries? what exactly is the IP address and more importantly the subnet mask of an affected PC?

I don't have to look at the logs, your issue is going to be boundaries 99% of the time and they have not been setup correctly.

There was not way to do this in CM07 that I'm aware of short of creating a Collection and adding the PC/User to the collections and Advertising the package out to that collection. The process is the same in CM12.

It might be possible to do this, read these blog AND particularly the TechNet docs listed within the blog post. http://be.enhansoft.com/post/2014/01/14/Upgrading-SCCM-2012-R2s-Site-Server-Operating-System.aspx http://be.enhansoft.com/post/2013/12/05/Upgrading-Configuration-Manager-2012-Database-From-SQL-2008-to-SQL-2012.aspx If not then you will have to rebuild you site from the ground up.

Why do you have ISS file on a UNC share? Why not included it with the packages? It will cause you problems if you don't.

It means that the role is already installed. and Please stop yelling in the forums.

Check the log file to ensure that CM12 Client is health, Reinstall the client if necessary. And Please stop yelling in the forums.

This simple answer is people don’t configuration their SQL server correctly. If you have a remote SQL server it should be dedicated to CM12, with a dedicated fiber connection between the two servers. It is added complexity and in 99% of all cases slower performance. There are long winded answer but you will find that most senior CM Administrators will highly recommend that you keep SQL local. Heck the biggest CM12 environment (400K) is using Local SQL.