Using smaller packages isolations and limits the scope of issues though - that's specifically why I greatly prefer them.
J From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Monday, June 1, 2015 1:55 PM To: [email protected] Subject: RE: [mssms] Is there a package version for SUP packages as for all other? Actually, small or not, if that content is not getting there for whatever reason, bad/dead connection or already pending distribution it would get stuck. And ADRs using the same package, like definition updates or even just regular updates as part of patch Tuesday. Although wondering if no one would have noticed that if it really happens. -R From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Montag, 1. Juni 2015 19:32 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Is there a package version for SUP packages as for all other? Yes, there is a package version number; however, the content of update packages is a bit different in that it keeps track of individual updates. Not sure if an in-progress package update will cause issues or not. Just another reason to use smaller packages for updates though. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Monday, June 1, 2015 8:38 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Is there a package version for SUP packages as for all other? Updating a regular package increases the version by 1, requires the new policy to be known to the client and if done during OSD for a required package, it may fail the TS. So don't change a live package. But what about software updates packages? The client isn't downloaded everything, so if new content is added it either can access it or not, right? Also is a software update package offline as all other packages are, while new content is added and distributed? -R
