GarthMJ

have you seen this? http://www.enhansoft.com/blog/configuration-manager-2012-r2-ssrs-and-windows-authorization-access-group

Exactly what permission do you check? Do you get the same error within the Web interface? BTW I never recommend accessing SSRS from the console.

What is your Heartbeat discovery cycle set too?

CM12 MUST be installed in the EXACT same Domain/Forest (aka SIDs), if it is not it will fail. So unless this is an exact clone of your existing forest, (which I would never recommend doing) , the whole process will fail and is completely unsupported.

Are you sure you are seeing MW or are they Business hours? They are NOT the same thing.

You first query only finds x86 version of Visio. The report will find both x86 and x64. Create a second WQL query to find x64 copies of Visio.

The minimum is 1 GB for Windows 7 but honestly I haven't not seen anything less than 4GB (3.5GB on x86) in years! If you have a TAM tell him about your issue and get him to "look at it". They will then get the right person to work on it.

2GB is tiny amount of RAM. Point your CSS team to this blog. http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx

What happens when you manually download that SU?

To add to what Peter said, CM12 clients will randomly select a SUP to scan against, they ignore boundaries. Therefore a CM12 client might pick a SUP remote to them. Honestly once the initial SU catalog is download there is only minor traffic between the CM12 client and the SUP,.

If you look at your query you are explicitly saying that you only want to look at x86 computer and don't want to see any data from x64. "SMS_G_System_COMPUTER_SYSTEM.SystemType = "X86-based PC"" This will filter out any x64 computer with an x86 version of Office.

Why do you have a SUP on all of you DPs? It is generally not recommend to have too many SUP.

Keep in mind that your will NOT find any x64 computers with x86 version of Office.

Why don't you just turn off automatic pushing for the CM12 client? Use a start up script instead.

If you are already working with CSS (MS Support) on a SUP issue. You should talk to them about this before making any changes.

Let's be clear a 6GB laptop will never work.

I assume this is a POC but honestly your laptop will not even come close to handling the load. SM12 needs two servers for itself If I remember right. What exactly is you goal? why do you want to have both CM12 and SM12 running at the exact same time?

Your laptop does not have enough ram to do this. You should not install CM12 on a DC. SCSM require two servers to full setup.

What does you PowerShell Script look like?

Microsoft what not updated this data for these application yet. Why don't you create you own HW requirements?

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

If I had to guess, I would say duplicate GUIDS or bad client certs.

I personally just sort the columns within the console, then highlight the unapproved ones and approve them.

As I said in the other forum that you are posting too, There is nothing wrong within this log snip-it, the client is getting installed. Your problem sound like it is a boundary issue.

When did you create the SWM rule? What report is not work?