I've got a word doc, never blogged it and never finished it, to stop ALL software deployments you'll want to configure something to stop applications from installaing also, this only disables SWD the list stopped me from sending it as it's too big, email me if you want a copy.
On Mon, Aug 25, 2014 at 4:07 PM, Niall Brady <[email protected]> wrote: > here's what i did, never blogged it and never finished it, to stop ALL > software deployments you'll want to configure something to stop > applications from installaing also, this only disables SWD > > > On Mon, Aug 25, 2014 at 3:31 PM, Niall Brady <[email protected]> wrote: > >> i started blogging about disabling SWD and other functionality via CI/CB >> and got great success with that, however it only disabled that >> functionality (other functionality could still work) however the same >> ideaology could be used for disabling the other functionality... >> >> I never completed it but happy to share if anyone wants it >> >> >> On Mon, Aug 25, 2014 at 3:18 PM, Daniel Ratliff <[email protected]> >> wrote: >> >>> Also note that if you have any deployments set to Ignore Maintenance >>> Windows, adding Trevor’s suggestion below will not help. You will still >>> need to stop CCMexec, etc. >>> >>> >>> >>> You could setup a client policy to disable what you need? But I know >>> there are some limitations there as well. >>> >>> >>> >>> *Daniel Ratliff* >>> >>> >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *Trevor Sullivan >>> *Sent:* Monday, August 25, 2014 9:13 AM >>> *To:* [email protected] >>> *Subject:* RE: [mssms] Is it possible to have a Maitenance Window that >>> prevents any deployments? >>> >>> >>> >>> Sure, just create an *All Deployments* Maintenance Window that is 40 >>> years in the future, and apply it to those machines. If you’re especially >>> worried about these systems, then you could always consider disabling the >>> *ccmexec* service, or removing the ConfigMgr client altogether, but >>> then you’d lose other ConfigMgr features like Compliance Settings rules, >>> Inventory reports, and so on. It all depends on how critical these systems >>> are during that period. >>> >>> >>> >>> Cheers, >>> >>> Trevor Sullivan >>> >>> Microsoft PowerShell MVP >>> >>> [image: cid:[email protected]] <http://mms.mnscug.org/> >>> >>> >>> >>> *From:* [email protected] [ >>> mailto:[email protected] <[email protected]>] *On >>> Behalf Of *[email protected] >>> *Sent:* Monday, August 25, 2014 8:02 AM >>> *To:* [email protected] >>> *Subject:* [mssms] Is it possible to have a Maitenance Window that >>> prevents any deployments? >>> >>> >>> >>> Crazy question but I need to lock down a specific set of machines for a >>> 30 day window. Is it possible to prevent deployments entirely? Anyone >>> have a suggestion? >>> >>> >>> >>> Appreciate the help >>> >>> >>> >>> Thanks >>> >>> >>> >>> >>> >>> The information transmitted is intended only for the person or entity to >>> which it is addressed >>> and may contain CONFIDENTIAL material. If you receive this >>> material/information in error, >>> please contact the sender and delete or destroy the material/information. >>> >>> >> >> >
