Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

Koenraad Rens

My feedback

  1. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Koenraad Rens shared this idea  · 
  2. 0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
    Koenraad Rens shared this idea  · 
  3. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Koenraad Rens shared this idea  · 
  4. 30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Ideas » Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Koenraad Rens supported this idea  · 
    An error occurred while saving the comment
    Koenraad Rens commented  · 

    I also encountered several problems which were fixed by rebooting the sms agent host service.
    Let ccmeval restart the service when it hasn't restarted in X days. This would also fix issues that aren't explicitly detected with ccmeval.

  5. 22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Koenraad Rens commented  · 

    You don't need to deploy your patches to the collections you use to configure the maintenance windows. Create a seperate collection with all the servers and deploy your patches to that collection.

  6. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  3 comments  ·  Ideas » Compliance Settings  ·  Flag idea as inappropriate…  ·  Admin →
    Koenraad Rens supported this idea  · 
  7. 80 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Noted  ·  sangeev responded

    Updated by bobmn for sangeev/OSD

    An error occurred while saving the comment
    Koenraad Rens commented  · 

    A simple popup Task Sequence Step would give flexibility.
    I'm currently using a Restart Step to give the messsage, but it times out after 9999 seconds.
    (Or don't count down when I enter 9999 seconds :-))

    Even better would be a popup with a Yes/No or OK/Cancel option and a TaskSequence variable that contains the choice.

    Koenraad Rens supported this idea  · 
  8. 138 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Updating status to started. See https://docs.microsoft.com/en-us/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.

    Configmgr 2003 Technical Preview released today and has a new SDK method for task sequence progress.

    For more info:
    Doc: https://docs.microsoft.com/en-us/configmgr/core/get-started/2020/technical-preview-2003#bkmk_tsapi
    Blog: https://techcommunity.microsoft.com/t5/configuration-manager-blog/onboard-clients-to-microsoft-defender-atp-using-memac-and/ba-p/1266085

    This should address some of the asks here, please try it out and let us know your feedback.

    Koenraad Rens supported this idea  · 
  9. 95 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  4 comments  ·  Ideas » Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Koenraad Rens supported this idea  · 
  10. 411 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  18 comments  ·  Ideas » Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Koenraad Rens supported this idea  · 
    An error occurred while saving the comment
    Koenraad Rens commented  · 

    To me it seemed strange this used the maintenance window.
    We are upgrading from 1511 to 1607 and using the automatic upgrades for the first time. We gave the upgrade 14 days.
    Clients wait until the maintenance window. But at that moment ccmsetup only creates the Upgrade Task which will be started somewhere in the future. It didn't seem this task respected the Maintenance Window.
    In our site with maintenance windows once every week, most upgrades will be started at the end of the 14 days period.

Feedback and Knowledge Base