Request to add support for Distribution Point Maintenance mode
Situations where maintenance mode is useful/needed:
1. When the system (hardware) is in transit from the location where it was installed to the site where it is to be used in production.
2. When the system is down for other maintenance (software patching and updates, OS configuration changes, hardware reconfiguration and other external factors causing planned or unplanned downtime).
The above outlined method for installing new DPs to remote locations is widely used for various reasons (For example to have a dedicated team at one location install machine and to avoid having to copy a large content library across WAN links). During the time in transit (which is usually between 1 day and 2-3 weeks), the ConfigMgr site server will only know that the DP server is unreachable on the network.
Advantages with a maintenance mode option:
- The status system should/will mark the system as being in the fully expected maintenance mode state (no error condition).
- The log files for components actively working with the DPs will not be cluttered with information about attempts to work on packages targeted to the off-line DP.
- We will not have various error status messages generated regarding the distribution points and its packages during the planned off-line time.
- The Distribution Manager (DistMgr) / Package Transfer Manager (PkgXferMgr) pipe will not be burdened with and slowed down by requests for systems known to be offline.
- Packages targeted to systems that are in the maintenance mode state will not be labeled as failed after the retries are used up, but rather that they are in a “waiting” (for the DP to get out of maintenance mode) state.
The change requested:
The primary ask here is to let DistMgr and PkgXferMgr know that they should not need to work any request targeted to DPs that are in maintenance mode. If they are currently working on such requests, they should stop doing so and postpone the request until the DPs status changes.
It will also be good, if DP systems in the maintenance mode state are not considered when clients make content location requests.
This feature is added in the soon soon to be released #SCCM 1902.
Considering the number of votes and the idea, hoping to see this implemented soon.
This is exactly what I'm looking for right now. One of our very remote DPs suffered a hardware failure, and we're waiting to see if we can bring it back online, but in the meantime, I need things to be calm, so I can identify actual problems as they arise.
Levi Stevens commented
We experience this when we have to shut down locations due to things like fires (California) or a hurricane (East coast). It would be nice to not have these show as "Errors" with constant attempts to retry. They should be listed as "In Progress - Maintenance Mode".
Sean Huggans commented
This should also track jobs, perhaps in a DB table, for the offline DP. Any job can be added to that table instead of the distribution queue, allowing all jobs in the table for that DP to be loaded into the distribution queue when that DP is brought back online.
Matthew Laye commented
adding my 2 cents about this feature.... we have a large number of DP's spread out nationally at local constructions sites and some commonly go offline due to connectivity, power work etc...
Would be helpful to have a maint mode to stop errors and system being tied up trying to talk to in unavailable box.
Jon Gibert commented
Your idea seems to be the same as this idea: https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/16896544-maintenance-window-for-dp-role
Is it possible to mark a specific DP to be in maintenance mode? ConfigMgr site server then wouldn’t waste a thread trying to copy packages to DPs in maintenance mode. Sometimes when the DP is down or if there are network issues, marking DP in maintenance mode should be an option available.
Panu Saukko commented
Please allow to mark specific DPs to be in maintenance. During the maintenance, ConfigMgr site server wouldn't try to copy content to those DPs. Because there are a limited number of threads for copying content to DPs, it is no point trying to copy packages to servers that are known to be down.
Mads Borlund commented
This feature would really help us when shipping DPs worldwide to our 200+ sites. We currently "disconnect" the DPs in transit by using the scheduling feature, but that still forces the PkgXferMgr to run through each package and verify tat there is no available bandwidth.
A simple maintenance on/off switch would be much better and let PkgXferMgr use it's time where it can actually transmit data.
Bob Panick commented
This is a really good idea and would be very useful for troubleshooting DP problems.
Joe Safe commented
Really good idea, would definitely be beneficial whilst shipping DPs to remote locations.
Jesper Walsted commented
We often create DPs close to our primary DP and then afterwards ship them around the world. During this time the server is often stuck in customs. This is confusing our SCCM setup so would be nice to have a maint. option for DPS
Ursina Wyss commented
With this functionality you could prevent your system from a lot of connection errors.