At customer location we want to implement software metering. This component in ConfigMgr tracks how many times an executable is started per user. You can access reporting to see how many times a program is started for multiple users. Peter Daalmans has a blogpost available on how to configure software metering in your organization. Problem is, it wasn't working in my installation because of multiple reasons. Looking in "mtrmgr.log" and "SWMTEReportGen.log" the following errors and warnings are shown:
-OpenProcess failed for process 4, error 80070005
-No usage will be tracked for proces 4, as failed to get owner info or executable file name 80070005
-GetShortPathName failed for \SystemRoot\System32\smss.exe, error 3
-GetFileVersionInfoSize failed for file \Systemroot\System32\smss.exe, error 2
-Program might not match metering rules, as version header was not read
-No usage data found to generate software metering report
We did the following changes to implement software metering successfully:
-Disable User Account Control (UAC) on the client(s)
-Remove existing files in <ConfigMgr>\Inboxes\Policypv.box folder
-Start runmetersumm.exe <Site code> on the SQL server where the ConfigMgr database is found. This tool is part of the ConfigMgr 2012 R2 Toolkit
The purpose of this tool is to run the metering summarization task to analyze raw metering data. (runmetersumm.exe)
After that you will see that reports will be filled with information!
Sources used:
Clients not receiving new Software Metering Rules
Software Metering Reports Not Working
System Center 2012 R2 Configuration Manager Toolkit
"-Start runmetersumm.exe on the SQL"
ReplyDeleteNot correct!
\ServerTools\runmetersumm.exe" /?
This program will run the File Usage Summary and Monthly Usage Summary
Software Metering data summarization tasks. It will summarize all existing
meter data without the usual 12 hour waiting period. It must be run on the
SQL server computer for the SMS site. Log entries will be sent to the console
if logging is turned on for SMS_SQL_MONITOR component. The exit code will be
set to 0 if summarization was successful and 1 if there was an error.
Usage: runmetersumm [sms database name]
I keep getting "Logging is turned off, turn on logging for the SMS_SQL_MONITOR component for more detail." I go to look for SMS_SQL_Monitor component and I can not find it. I am running Build 1910.
ReplyDelete