none
Multiple deployments for the same application RRS feed

  • Question

  • Hello,

    When doing repetitive deployments for the same application what is the best practices:

    - Reuse the same collection by emptying it from the previous deployment

    Then adding new machine(s)

    ...

    - creating a new collection each time and removing the p[revious collection from the deployment tab'

    ISS - Server - SPLUNK Universal Forwarder 7.0.3 x64 - 2nd round

    ISS - Server - SPLUNK Universal Forwarder 7.0.3 x64 - 3rd round

    etc...

    Thanks,
    Dom


    Security / System Center Configuration Manager Current Branch / SQL


    • Edited by Felyjos Monday, December 2, 2019 5:16 PM
    Monday, December 2, 2019 5:05 PM

Answers

  • Then you can do one of two things:

    1. Create separate collections for each department and separate deployments for each collection with the deadline time specific to that department.

    2. Use a single collection and deployment adding systems from each department when its their turn to receive the software. There's no reason to remove systems from this collection though.


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by Felyjos Monday, December 2, 2019 7:38 PM
    Monday, December 2, 2019 7:12 PM

All replies

  • Hi Dom,

    It depends of you, there is no best practice to deploy an application on SCCM.

    Why not push directly the application on all servers ? If you have any risk, I suggest to you to create a collection for TEST servers and another for PROD, then you will deploy first to the TEST collection devices and once you make sure that all is OK, do the same for PROD collection.

    Regards,

    SAAD Youssef

    ______

    Please remember to mark the replies as answer if they help, thank you!


    Monday, December 2, 2019 6:48 PM
  • Why do you want or need multiple repetitive deployments of the same application? If it's the same application, re-deploying it has no effect.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, December 2, 2019 6:49 PM
  • Hi Dom,

    It depends of you, there is no best practice to deploy an application on SCCM.

    Why not push directly the application on all servers ? If you have any risk, I suggest to you to create a collection for TEST servers and another for PROD, then you will deploy first to the TEST collection devices and once you make sure that all is OK, do the same for PROD collection.

    Regards,

    SAAD Youssef

    ______

    Please remember to mark the replies as answer if they help, thank you!


    Hi Youssef,

    I have already test and production and one deployment was sent for test and was ok then one deployment was done for production #1 which is for one department.

    Then now I will have to deploy to other department one by one. Each department has to give its approval for the deployment of applications and they are coming for different dates & time...depending on their own availability and convenience

    Thanks,
    Dom


    Security / System Center Configuration Manager Current Branch / SQL

    Monday, December 2, 2019 7:04 PM
  • Why do you want or need multiple repetitive deployments of the same application? If it's the same application, re-deploying it has no effect.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Hi Jason,

    Each deployment is split per department even it is for the same application. They are providing different dates and times for their deployment depending on their availability and schedules.

    Thanks,
    Dom


    Security / System Center Configuration Manager Current Branch / SQL

    Monday, December 2, 2019 7:06 PM
  • Then you can do one of two things:

    1. Create separate collections for each department and separate deployments for each collection with the deadline time specific to that department.

    2. Use a single collection and deployment adding systems from each department when its their turn to receive the software. There's no reason to remove systems from this collection though.


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by Felyjos Monday, December 2, 2019 7:38 PM
    Monday, December 2, 2019 7:12 PM
  • Thanks I will pick option which looks easier to monitor from a department side.

    Dom


    Security / System Center Configuration Manager Current Branch / SQL

    Monday, December 2, 2019 7:41 PM
  • Hi,

    Many thanks to Jason for the solution provided for this thread.
    Please allow me to write a short summary for this thread, because we believe this will make the thread clearer and more friendly for other people who have similar problems.


    Problem/Requirement:
    ===================
    what is the best practices for repetitive deployments of the same application

     
    Solution:
    ===================
    1. Create separate collections for each department and separate deployments for each collection with the deadline time specific to that department.
    2. Use a single collection and deployment adding systems from each department when its their turn to receive the software. There's no reason to remove systems from this collection though.

    Best regards,
    Larry

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, December 4, 2019 8:41 AM