We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Comments
Aye, an exclusion list is indeed missing. One possible workaround would be to use Authorization on your software assets. In this scenario, you could assign your test servers/computers to have an Organization (or cost center, or Location) of "TEST". Then, you could assign your software assets to only have authorized organizations other than "TEST". This would assume that your Windows Computer objects have related Hardware Assets, which have Organizations assigned.
It does have a bit of overhead to set up for an exclusion, but does work fairly well.
Another solution would be to exclude test servers from the ConfigMgr connector collection, so the asset data never gets populated. Of course, if MS ever came knocking for an audit, you would then have to prove that all servers\PC's in that collection fell under a different license agreement etc.
We have around 600 servers so there are a lot of changes and it would easily get outdated = unreliable.
The different server types gets placed in different OU's in AD - Prod or Test, so if the authorized computers could be automated / auto-discovered it would solve lots of the problems, like being AD OU-based.
Worst-case is to have custom powershell-scripts to automate the population of this, but it's of course not a desired solution.
To have an auto-discover solution set up per software assets authorized computers is perhaps also not a desired solution from a Service Manager performance point of view?
Out of what we've seen in audits so far is that the same groups of test computers reappear in license after license. Perhaps there could be a "common" groups of test computers that can be defined, that you could select to exclude from the license counts of certain licenses?
Like one common group of test computers for Microsoft licenses, one for Adobe, etc.
Just a thought if an auto-discover route wouldn't be possible..
I can see where you are going with this though.... so lets thin of a generic solution together.
What if there was a check box (Boolean control) on the Hardware Asset class that was something like "Exclude from License Calculations"
This automatically adds this Hardware asset to the Excluded list for Software Assets.
PC's that are developer machines, SOE test boxes, Dev servers or contain MSDN licenses will then never be counted.
It would then not be hard to automate a listing from an AD Group to auto check that value for the hardware asset.
Just spit ballin'
Thoughts?
That could then either be managed manually or be fairly easily automated with SCO/Powershell and would instantly cover all SW assets.
If this feature would be implemented..
..it would be nice to also have the excluded ones appear on the SoftwareAsset/RelatedAsset tab under a new view - RelatedComputers-ExcludedFromLicenseCounts. Just to show that the computer has the software asset, but is not counted.
That view should perhaps not be editable, just for information purpose to instantly give a complete picture for the SW responsibles.
Interesting conversation
To next to the checkbox on the Computer Asset also have a small text-field for a short justification would be extremely helpful. Why was it excluded.. Helps when backtracking as well.