Tech Community Live: Endpoint Manager edition
Jul 21 2022, 08:00 AM - 12:00 PM (PDT)

required deployment to install during maintenance window prior to deadline

%3CLINGO-SUB%20id%3D%22lingo-sub-2394216%22%20slang%3D%22en-US%22%3Erequired%20deployment%20to%20install%20during%20maintenance%20window%20prior%20to%20deadline%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2394216%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%20Currently%20we%20have%20a%20two%20deployment%20system%20for%20installing%20updates%20on%20our%20end%20user%20devices%20which%20we%20have%20used%20for%20a%20long%20time.%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3E%26nbsp%3Brequired%20deployment%2C%20that%20goes%20during%20maintenance%20window.%26nbsp%3B%20This%20deployment%20is%20our%20main%20update%20and%20normally%20gets%20around%2070-75%25%20of%20devices.%26nbsp%3B%20(targeted%20collection%20is%20query%20based%20and%20removes%20updated%20devices%20as%20they%20get%20the%20software%20install%20via%20regular%20collection%20update%20schedule.%26nbsp%3B%20).%20this%20one%20is%20set%20to%20expire%20before%20deployment%20two%20deadline.%26nbsp%3B%3C%2FLI%3E%3CLI%3EThen%20for%20all%20remaining%20devices%20that%20aren't%20contactable%20during%20the%20maintenance%20window%2C%20we'll%20have%20a%20secondary%20deployment%20that%20is%20made%20available%20at%20the%20same%20time%20as%20the%20first%20deployment%20but%20has%20a%20deadline%20of%20a%20few%20days%20in%20the%20future%20and%20is%20configured%20to%20run%20outside%20maintenance%20window%20time%20frames.%26nbsp%3B%26nbsp%3B%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20way%20we%20get%20the%20majority%20of%20the%20machines%20with%20the%20first%20deployment%20and%20the%20remainder%20either%20the%20users%20do%20it%20when%20they%20see%20the%20prompts%20during%20the%20second%20deployment%20timeframe%20or%20it%20just%20happens%20when%20the%20deadline%20hits.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI'm%20thinking%20this%20is%20probably%20something%20I%20need%20to%20put%20on%20uservoice%20because%20I%20can't%20see%20it%20as%20an%20option.%26nbsp%3B%20Before%20I%20do%20that%2C%20I%20thought%20I%20should%20check%20I%20haven't%20missed%20something.%26nbsp%3B%20Is%20it%20possible%20to%20have%20a%20single%20deployment%20with%20the%20following%20config.%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3Estart%20today%2C%20if%20machine%20contactable%20during%20maintenance%20window%2C%20do%20the%20update.%26nbsp%3B%20Outside%20the%26nbsp%3B%20maintenance%20window%2C%20just%20do%20the%20usual%20prompts%20that%20an%20update%20is%20available%20and%20allow%20user%20to%20install%20outside%20maintenance%20window.%26nbsp%3B%26nbsp%3B%3C%2FLI%3E%3CLI%3Edeadline%20in%203%20days%2C%20if%20the%20software%20update%20hasn't%20happened%20by%20then%2C%20then%20allow%20the%20install%20to%20happen%20outside%20the%20maintenance%20window.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2394216%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApp%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECM%20current%20branch%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor

Hi,  Currently we have a two deployment system for installing application updates on our end user devices which we have used for a long time. 

  1.  required deployment, that goes during maintenance window.  This deployment is our main update and normally gets around 70-75% of devices.  (targeted collection is query based and removes updated devices as they get the software install via regular collection update schedule.  ). this one is set to expire before deployment two deadline. 
  2. Then for all remaining devices that aren't contactable during the maintenance window, we'll have a secondary deployment that is made available at the same time as the first deployment but has a deadline of a few days in the future and is configured to run outside maintenance window time frames.  

 

This way we get the majority of the machines with the first deployment and the remainder either the users do it when they see the prompts during the second deployment timeframe or it just happens when the deadline hits.


I'm thinking this is probably something I need to put on uservoice because I can't see it as an option.  Before I do that, I thought I should check I haven't missed something.  Is it possible to have a single deployment with the following config. 

  • start today, if machine contactable during maintenance window, do the update.  Outside the  maintenance window, just do the usual prompts that an update is available and allow user to install outside maintenance window.  
  • deadline in 3 days, if the software update hasn't happened by then, then allow the install to happen outside the maintenance window.

 

0 Replies