No problem Alex, I will look into your recommendation and provide you feedback.
Client Inactivity with MEMCM
There a few machines within the MEMCM environment where ConfigMgr Client is recognized within MEMCM environment but it showing inactivity status under Client status within Monitoring Workspace. Site and services and Boundary group with distribution point setup for these Windows Clients seem to be correct. Also, I attempted to repair and reinstall ConfigMgr client locally on machines. Issue is still showing. Also, attempted to do a Client Push to reinstalling ConfigMgr client within MEMCM environment to machines with inactivity issues. Issue is still existed. Is there any other recommendations or feedback that can be provided.
I did check the CcmNotificationAgent.log on some of the machines were in inactivity status in the network environment I'm working with. The status of CcmNotificationAgent.log looked normal. What I ended up doing was going into the machines with the inactivity status, going into Control Panel, then Configuration Manager, then in the Action Tabs, I ran all the cycles. After about 10 to 15 minutes, those same computers are now showing active in Client Status with Monitoring Workspace. But I have another issue, even with those computers that are in that status. Prior deployments delivered to those computers that were in inactivity status but are now active still having issues with waiting in content status, Is there a way I can force these prior deployments of active status receive software deployments to these newly SCCM client active machines?
Sign in to comment