none
User based Mandatory deployments are not getting through for some clients RRS feed

  • Question

  • Hi All,

    I am experiencing an issue with User based "Required" deployments of application.  for some users it gets installed but for some its not.  On the problematic systems, I could not see any entries related to the application the appdiscovery.log as well. 

    The requirement for the application is only operating system version and both working and non working systems are running on the same version of OS.

    Also on these systems none of the user based "required" deployments work but same application will work if its deployed as user based "Available deployment" or Machine based Required or Available deployment.

    Could anyone please help in getting some hints on the probable causes.

    Please note that the UDA is enabled based on usage time but the deployment is not having the mandate to have primary device. 


    Regards Nikhil S

    Tuesday, October 15, 2019 4:23 PM

All replies

  • What happens if you or the user manually refreshes the user policy?

    Do the deployed applications shown in Software Center?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, October 15, 2019 4:48 PM
  • Hi Jason,

    Manually refreshing the policy also not making any change.


    Regards Nikhil S

    Tuesday, October 15, 2019 4:53 PM
  • Just to clarify, how *exactly* did you refresh the policy?

    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by S Nikhil Wednesday, October 16, 2019 9:49 AM
    • Unmarked as answer by S Nikhil Wednesday, October 16, 2019 9:49 AM
    Tuesday, October 15, 2019 7:40 PM
  • Hi,

    Please try to check the deployment status for the application in the Monitoring workspace under the Deployments node.
    If the deployment status is "Unknown", it usually means that the client hasn't received policy, please follow the article below to manually refresh client policy to see if the client receives it. 
    https://docs.microsoft.com/en-us/sccm/core/clients/manage/manage-clients#BKMK_PolicyRetrieval
    If these actions don't resolve the issue, check the client status.



    Best regards,
    Larry

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, October 16, 2019 2:39 AM
  • Hi Jason,

    Invoked User policy Retrieval and Evaluation Cycle from ConfigMgr Actions. 


    Regards Nikhil S

    Wednesday, October 16, 2019 9:52 AM
  • Hi Larry,

    Yes, the deployment status is "Unknown" for those users.  As I mentioned in the original post, the issue is only if I deploy the application as "Required".  Same application deployed to same user as "available" is working fine.  I believe, if the problem is with user policy retrieval, both deployments should be affected. 


    Regards Nikhil S

    Wednesday, October 16, 2019 9:58 AM
  • Hi,

    Please try to check the client status, there may be a deeper underlying problem with the client. For more information, see How to monitor clients in Configuration Manager:

    https://docs.microsoft.com/en-us/sccm/core/clients/manage/monitor-clients

    You may also need to check if the corresponding management point is healthy. The following post may be helpful to you, I hope this will show you some troubleshooting ideas.

    https://social.technet.microsoft.com/Forums/en-US/76045c07-dda4-4a9a-b007-fd3a94d2c3b2/application-deployment-monitoring-pcs-stuck-in-status-unknown?forum=ConfigMgrAppManagement


    Best regards,
    Larry


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Thursday, October 17, 2019 9:47 AM
  • Hi Larry,

    thank you for the response.  

    Another observation from one of the problematic systems is:  I could see only policy ID under ROOT\ccm\Policy\User_SID\RequestedConfig:CCM_ApplicationCIAssignment

    The Policy Instance ID, ruleID etc are missing

    It seems to be a WMI corruption, but still not convinced since user based "Available" deployments are working fine.  Any help in finding the root cause of this?


    Regards Nikhil S



    • Edited by S Nikhil Saturday, October 26, 2019 11:44 AM
    Thursday, October 24, 2019 2:02 PM