GarthMJ

it is all done in the security role. There are no tricks to this, only grant them access to the SW metering reports + site (read) + Collection (read + red resourses), there maybe a few other minors thing that you need to grant them access too but... all

I understand the problem, I just don't know what you have done. I even test this in another lab that I have access to, it worked.

I'm not sure what you have done, But I would try to return everything back to what is was before.

So it is sneaker net... CM12 can't solve a sneaker net issue. Try looking for ways to have a PC Boot from an ISO from within itself.

If you use the steps that I define above, this what you will get. What exactly have you setup for the security role?

I should have said that I restricted this use to SU only.

yes it is.

Your client seriously have a 1bit subnet mask. You broadcast domain is huge, I hate to see the network traffic. What is there to tell based on what you stated you are forcing each client to assign themselves to your site. This might mean that your clients are having problem with deployment too.

If you used the un-edit Report reader security role, it will grant them access to ALL CM12 reports assuming that you grant that Sec role all systems collections. So you edit to edit it to only grant access to SWM reports. + a few extra one. Exactly what collection(s) did you grant the AD security group access too? Have the users logon after being added to the security group?

What exactly did you setup for the Security role? what does this have to do with Software Metering?

You have not listed that you are using a 16bit subnet mask for your boundaries before. And that will be exactly your problem. Boundaries 10.10.234.123 255.255.0.0 =10.10.0.0 Client 10.10.234.123 255.255.255.0 = 10.10.234.0 10.10.0.0 != 10.10.234.0 Hence why none of your client are getting assigned

Start by answering the question, How do you do this manually?

So you want to grant permission to SW metering reports. OK Create a AD security group. Create a CM12 for only the SWM reports + a few extra permission. Assign the AD security group to the CM12 Security Role. with access to all systems. These blog will get you started. http://www.enhansoft.com/freetools/enhansoft-report-reader-configmgr-2012-r2 http://www.enhansoft.com/blog/new-tool-for-creating-configuration-manager-2012-report-reader-ad-security-groups http://www.enhansoft.com/blog/creating-configuration-manager-2012-report-reader-ad-security-groups

Exactly what reports are to trying to grant access too?

First off, what exactly are you trying to grant access to? Name 1 report for each folder, if there is more than one folder.

Are these custom folder or default folders?

Set the permission on one report. wait 10 minutes. Does the permission on the report get updated?

see this blog post. http://www.enhansoft.com/blog/disappearing-permissions-for-ssrs-reports-in-system-center-2012-configuration-manager

Again, I'm asking exactly what do you setup for boundaries?

Simple you are force overriding the site assignment. It is not use the automatic site assignment.

First off a 2 hour MW, IMO is to small, I recommend nothing less than 4 hours. Secondly the only way a follow-up SU will apply is in there is another deployment during that MW, otherwise that is the expected. Even then it is rare to an a follow up SU during a particular monthly SU cycle. So yes in a nutshell you gut is right. if you need "proof" then you will need to get your TAM to provide it.

What exactly is IP Network? is the IP range or IP subnet? What exactly are the subnet masks of your clients? What exactly is the IP subnet mask for your AD subnets?

BTW if you are coming to MMS http://mmsmoa.com/, feel free to stop by and say Hi.

That sound like your boundaries are not right. What type of boundaries are you using?

No, there is no place to see this.