Ok. Just getting my feet wet and wanted to make sure the Network wasn’t going to get hit with a bunch of add/drops.
From: [email protected] [mailto:[email protected]] On Behalf Of Mote, Todd Sent: Wednesday, September 2, 2015 9:55 AM To: '[email protected]' Subject: RE: [mssms] updating a SUG I reuse the same SUG every month that is updated with new updates and removes all the old updates. I have the same packages and deployments I set up three years ago using ADR’s. Every month the ADR’s get the list of updates then replaces all the updates in my SUGs with the new discovered updates, all the superseded and expired ones get removed, all the new ones get added. The new updates get downloaded, added to the package, and then added to the deployment. I’m not sure about doing it manually, but that’s essentially the same process you describe. I don’t have to redistribute or redeploy anything and clients pick up the new updates every month. Todd From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Wednesday, September 2, 2015 8:46 AM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: RE: [mssms] updating a SUG So I had a SUG package. Dirstributed Deployed Ran a Microsoft update on the client after all deployed packages were installed. I found 2 additional KB’s that I missed. So I am downloading the KB’s. Editing the membership of the package. At this point I ??redistribute?? the package. Then redeploy or the next Software Update Cycle will catch the 2 new KB’s and install them without redeploying them? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of CESAR.ABREG0 . Sent: Wednesday, September 2, 2015 9:34 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] updating a SUG SUG you don't distribute, the downloaded updates that are part of packages get distributed so if the update you are adding are being downloaded, you need to distribute the package those are part of. On Wed, Sep 2, 2015, 6:28 AM David McSpadden <[email protected]<mailto:[email protected]>> wrote: If I update a SUG do I need to redistribute it and redeploy it after the distributions are complete? David McSpadden Systems Administrator Indiana Members Credit Union P: 317.554.8190 | F: 317.554.8106 [Description: imcu email icon]<http://imcu.com/> [Description: facebook email icon] <https://www.facebook.com/IndianaMembersCU> [Description: twitter email icon] <https://twitter.com/IndMembersCU> [Description: email logo] [mcp2] This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email.
