Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Nectarios Gritzalis

My feedback

  1. 1,249 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  23 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
  2. 103 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    Nectarios Gritzalis supported this idea  · 
  3. 22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » Client Settings  ·  Flag idea as inappropriate…  ·  Admin →
    Nectarios Gritzalis shared this idea  · 
  4. 1 vote
    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 →
    Nectarios Gritzalis 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 » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Nectarios Gritzalis supported this idea  · 
  6. 82 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Updating status to completed – see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of each value.

    Our 1906 release is now available and includes pre-cache support for OS Images, Driver Packages & Packages in addition to OS Upgrade Packages.

    Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Update-1906-for-Configuration-Manager-current-branch-is-now/ba-p/775553

    Docs: https://docs.microsoft.com/sccm/core/plan-design/changes/whats-new-in-version-1906

    Nectarios Gritzalis supported this idea  · 
    Nectarios Gritzalis commented  · 

    Since Pre-Caching is already being validated/actioned for OS Upgrade packages in the TS, why not just also have an option that flags the pre-caching need in the "Run Command Line", "Install Package ", and "Install Application" step to allow these particular TS steps to also be pre-cacheable if desired, assuming the WMI condition is matched.
    This would simplify everything greatly since customers like us with 40+ HW models don't have to run separate TSes just to pre-cache the appropriate drivers, packages, etc..to the different models and not everything for all hardware models as "Download all content before starting task sequence" currently does.

  7. 152 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  5 comments  ·  Ideas » Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  8. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Nectarios Gritzalis commented  · 

    Indeed, this feature would be tremendously helpful and would even be more beneficial than what is already describes here.
    If the installation deadline for a "Required" deployment was "relative" to when the resource received the assignment (i.e.: scheduled to install after x hours or x days or x period"), the user and administrative experience would be significantly better.

    Here a practical scenario:
    - A collection for Office 2013 and a "Required" deployment for it is created with an fixed installation deadline of the end of the week
    - Currently, resources that are added to the Office 2013 collection during that week, based upon daily requests, will have to the end of the week before it is forced on them (although the window would be shorter for those resources added toward the end of the week, which is already demonstrating the issue).
    - However resources that are added to the collection after that installation deadline have absolutely no choice but to face this installation when their machine receives the assignment policy.
    - Sure, the installation deadline could be constantly modified, but when you have 1500 applications and their respective collections with deployments, this is not realistic.
    - Leaving the deployments as "Available" only forces the user to initiate the installation, which they often don't do, generating needless calls to the service desk asking where their application is.
    - Allowing the option for the deployment deadline to be relative to when the machine received the assignment policy would help greatly here.

    Here's another practical scenario:
    - We want to stagger a deployment of Office 2013 over a period of a few months but want each weekly group of resources assigned to be forced to install it within a week after they receive the assignment.
    - A collection for Office 2013 and a "Required" deployment for it is created with an fixed installation deadline of the end of the week
    - Currently, resources that were added to the Office 2013 collection at the start of that week, will have to the end of the week before it is forced on them, assuming they are online. If they are not, and come online later in the week, the user will have less time to schedule the installation themselves before Office 2013 is forced on them.
    - Resources not online at all that week that conect to the network following the installation deadline have absolutely no choice but to face this installation as soon as their machine receives the assignment policy.
    - To add to the problem, in order to manage such a deployment scenario, a new collection and deployment would need to be created each week during the course of the staggered rollout. More administrative work and complicated reporting ensues.
    - Sure, the new resources could be added to the existing collection and the installation deadline for the deployment could, again, be constantly modified, but that could leave resources from the first week of deployment never being forced to install the application until the final week of the Office 2013 deployment because the deadline is constantly changing.
    - Allowing the option for the deadline to be relative to when the machine received the assignment policy would, again, greatly help here, simplifying the deployment by allow us to simply add resources to the same collection each week and allowing this feature to handle deadline.

  9. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Client Discovery  ·  Flag idea as inappropriate…  ·  Admin →
    Nectarios Gritzalis shared this idea  · 
  10. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Ideas » Software Center  ·  Flag idea as inappropriate…  ·  Admin →
    Nectarios Gritzalis supported this idea  · 
  11. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Ideas » Content  ·  Flag idea as inappropriate…  ·  Admin →
    Nectarios Gritzalis supported this idea  · 
  12. 266 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    30 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Nectarios Gritzalis supported this idea  · 
  13. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  3 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Nectarios Gritzalis supported this idea  · 

Feedback and Knowledge Base