Hello all,

I'm trying to install a few applications, but we'll use the MBAM Client as an example, as it's small.

I have a couple of VMs and test machines, and can verify that the computers are installing applications from the deployments I set up, but they are not reporting back their status to the deployment statistics. They all just sit there with the Client Check Passed/Active status in the unknown tab.

I can even uninstall the app again, force the Application Deployment Evaluation Cycle, and watch it re-install. Is there something I'm missing, or should be checking?

Thanks,

Rob

Hi,

Please download ConfigMgr 2012 toolkit and use the Deployment Monitoring Tool to see the status for a given application on a client.

System Center 2012 R2 Configuration Manager Toolkit

http://www.microsoft.com/en-us/download/details.aspx?id=36213

So it would seem it's a Server-side issue. If I reboot the SCCM server, the statistics update, but eventually the the stats will stop updating again, until I reboot the SCCM server.

I'm getting an error on the SMS_STATE_SYSTEM also.

"The State System message file processing processed one or more files that contained errors or invalid data. Review the statesys.log file for further details."

and

"Microsoft SQL Server reported SQL message 50000, severity 16: *** Unknown SQL Error!"

Hi,

Have you installed DotNet updates recently.

Please refer to the following blog.

Unknown SQL error in ConfigMgr after installing DotNet updates

http://henkhoogendoorn.blogspot.com/2013/07/unknown-sql-error-in-configmgr-after.html

Note:Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact inform

I don't believe so. We are running SCCM 2012 R2 on Windows 2012 R2 Server and SQL Server 2012 on a Server 2012 R2 box also. I saw these solutions earlier today, but it's my understanding they don't apply to 2012 R2 boxes.

Hey, Rob. I know your thread is old and you may not see this, but did you ever figure out what was causing this behavior? I'm seeing it on an application deployment today, but haven't started troubleshooting yet. Thanks.