Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

Christoph Voigt

My feedback

  1. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Ideas » PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Christoph Voigt commented  · 

    The issue is that the commandlets to create and modify Deployment Types (e.g. New-CMDeploymentType and Set-CMDeploymentType and all other versions) do not include a parameter to add or modify the list of running processes that should be closed before the application installation can proceed. The process that's documented in https://docs.microsoft.com/en-us/configmgr/apps/deploy-use/deploy-applications#bkmk_exe-check

    Because the tab is called "Installation Behavior" this is often times confused with the installation behavior in the "User Experience" tab (Install for System/User/detect type based on deployment).

    To provide you with the scenario: we're including the process information in our install wrapper so our automation can create applications based on the metadata. We want to include the list of well-known processes per application/deployment type but currently this is only possible through human interaction with the console (haven't looked at WMI yet, but will probably have to).

    I'd love to see the official commandlets to:
    - read the "Installation Behavior"/combination of exe file name & display name
    - pass a hashtable to the commandlets that includes Executable Name/Display Name and replaces the existing list of executable files.

    This way we could properly automate the application creation/maintenance and NOT require human interaction with the console anymore.

  2. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Content  ·  Flag idea as inappropriate…  ·  Admin →
    Christoph Voigt shared this idea  · 
  3. 136 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.

    Christoph Voigt supported this idea  · 
  4. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Christoph Voigt shared this idea  · 
  5. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » Power Management  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Christoph Voigt commented  · 

    That's an interesting idea.
    Afaik ConfigMgr uses WOL (Wake on LAN) to achieve the wakeup - which is possible because desktops and their NICs are still connected to power. But with laptops you'll usually end up either in Standby, Hibernation or Shutdown states. As far as I remember only standby is able to supply (a tiny bit of) power to hardware functions (including your WiFi functionality) - not including Modern/Connected Standby options (which the hardware also must support).

    Looking at https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/wi-fi-power-management-for-modern-standby-platforms and https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/modern-standby-wake-sources I think there is an option to send a WOL package to devices in "Connected sleep" mode, but you'd also have to enforce this mode for your laptops and prevent students from completely shutting down the system.

  6. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Admin Console  ·  Flag idea as inappropriate…  ·  Admin →
    Christoph Voigt shared this idea  · 
  7. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Christoph Voigt shared this idea  · 
  8. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Christoph Voigt shared this idea  · 

Feedback and Knowledge Base