Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Alexandre Patenaude

My feedback

  1. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Alexandre Patenaude commented  · 

    The opposite is also true: I find it difficult to find in which tasks sequences a specific application is referenced. We are currently doing a cleanup of old applications from our console, and frequently I cannot delete an application because it is referenced in one or more TS. The problem is, the infobox only tells that the app is referenced in a number of TS, but not which ones. There definitely is something to be done on the console-side to view apps referenced by a TS, and in which TS an app is refered.

  2. 6 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 →
    Alexandre Patenaude shared this idea  · 
  3. 24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Troubleshooting & Support  ·  Flag idea as inappropriate…  ·  Admin →
    Alexandre Patenaude commented  · 

    Though it would be great to have a GUI to launch this action (either directly on the client device or from the console), one can force a state message reporting cycle by invoking a WMI method:

    wmic.exe /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000111}" /NOINTERACTIVE

    wmic.exe /node:<remotecomputername> /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000111}" /NOINTERACTIVE

    Can be put in a batch file for easier execution.

    If you use Recast RCT as an extension to your ConfigMgr console, this action is also included out-of-the-box and can be triggered graphically.

  4. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » Collections  ·  Flag idea as inappropriate…  ·  Admin →
    Alexandre Patenaude commented  · 

    I'm not very accustomed to phased deployments, but from what I've seen: when you create a phased deployment, you have to select existing collections for your various phases -- the phased deployment wizard won't create new collection. Using existing collections mean you can set various limiting collection per phases.

  5. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Client Settings  ·  Flag idea as inappropriate…  ·  Admin →
    Alexandre Patenaude shared this idea  · 
  6. 53 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Ideas » Software Center  ·  Flag idea as inappropriate…  ·  Admin →
    Alexandre Patenaude supported this idea  · 
  7. 22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Alexandre Patenaude commented  · 
    Alexandre Patenaude commented  · 

    I'm currently running in this situation right now. We have to uninstall a deprecated software which is integrated to multiple business applications and productivity applications (i.e. some Office addons). As the deprecated application is simply being decommissionned -- it's not critical if it stays installed, it is just unused and occupies disk space -- we would prefer it to only uninstall when the apps it integrated with are closed. Sadly, it appears the "Install Behavior" feature does not work the same way as it does when installing...

  8. 124 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Alexandre Patenaude supported this idea  · 
  9. 41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Ideas » Software Center  ·  Flag idea as inappropriate…  ·  Admin →
    Alexandre Patenaude commented  · 

    Consider the following scenario for deployments on users' computer devices:
    1. A user application deployment has been created as Required;
    2. The application is deployed on a user's computer device;
    3. Later, it is decided the deployment should not be Required anymore, and be Available;
    4. In the ConfigMgr admin console, an deployment manager deletes the Required deployment from the user collection, and creates a new Available deployment on that same collection.

    Once the Available deployment has been created, Software Center will not automatically launch an application deployment evaluation for the now-available app deployment.

    Instead, the application will appear as Available in the Software Center, even though it **is** installed, having been installed by the previous Required deployment.

    I feel the Software Center should evaluate app deployments even for Available applications, and:
    - if it has been found, show it as being installed in the Software Center;
    - if it has now been found, display it as available for installation.

  10. 87 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  3 comments  ·  Ideas » Deployment Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
    Alexandre Patenaude commented  · 

    @David Alvarez: it does not seem to work in my environment (Config Mgr version 1706).

    I did create a Required user deployment for an application. I did not tick the "Schedule the application to be available at" checkbox, and left installation deadline at "As soon as possible after the available time".

    In the Summary, it **is** written, though that the 'Deadline time' is Disabled.

    Still, once the deployment is created, the installation starts As soon as possible. And if I go check the deployment settings after the deployment has been create, I observe that the "Schedule the application to be available at" checkbox has been ticked, with available time auto-filled at the deployment creation.

Feedback and Knowledge Base