It makes very little sense to me that Phased Deployments don't work with Automatic Deployment Rules. I work as a consultant and deal with clients who just don't update machines cause they don't understand ADR's. We implement ADRs for them to ensure their fleet is kept up to date and secure. We've always utilised a Test, Pilot and Production rollout model. Phased Deployments would add another level of control to this to help monitor and drive greater update success. Please consider adding this functionality to the product.
awesome ask. makes sense.
100% agree this is a must have ability in SCCM. Servicing Plans are an awesome idea to keep the devices within an organisation up-to-date with the latest builds. But having seen some of the results, and the fact that even some minor customisations are "killed" by Servicing Plans, there has to be some way to either run a script or a Task Sequence on the completion of the upgrade (i.e. like the "Post-Processing" group in the In-Place Upgrade Task Sequences). Long term I'd prefer to see Servicing Plans used over Task Sequences for the automation it provides, but currently it's just short of the mark.
I've actually achieved this using Dynamic Variables within the Task Sequence, where there were DP's all across the country that were capable of performing OSD builds. You can then use the "tzutil" command as "Run Command Line" with the variable e.g. tzutil /s %TZone%. Works like a charm.
Updated by bobmn for sangeev/OSD
16 votesNoted · 3 comments · Ideas » Setup and Server Infrastructure · Flag idea as inappropriate… · Admin →