Yes of course, since this is a modification to the app/pack and hence a version change.
On Thu, May 21, 2015 at 3:10 AM, Jason Sandys <[email protected]> wrote: > Although an update is not needed, one will be initiated by ConfigMgr. > This will cause some overhead and network traffic because just like with a > manually initiated content update, ConfigMgr doesn’t know what changed and > so has to check each and every file on each and every DP. If no files have > changed, which they shouldn’t in this case, then nothing will be sent > across the wire, but the simple checking of files as mentioned does cause > some traffic and overhead. > > > > J > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Paul Winstanley > *Sent:* Tuesday, May 19, 2015 3:46 PM > *To:* [email protected] > *Subject:* Re: [mssms] RE: Migrating App Shares > > > > No Sean an update is not needed. > > > > On Tue, May 19, 2015 at 9:17 PM, Sean Pomeroy <[email protected]> > wrote: > > DFS is a great idea for source files! > > > > I've been pushing to move the source files and DP role off of our primary > site server for some time. > When that time comes I intended on either scripting the source file change > or using this utility from coretech: > http://blog.coretech.dk/jgs/coretech-package-source-changer/ > > > > Curious though, if you change the source file, do you need to update the > app/package in the console? > > I'm assuming no because the content is not changing. > > > > On Tue, May 19, 2015 at 1:11 PM Jason Sandys <[email protected]> wrote: > > Don’t get caught up in moving your source files to the DP. This will > cause additional network traffic because the DP is not populated from the > source files, it’s populated from the sccmcontentlib on the site server > which in turn is populated from the source files. Thus, moving the DP off > of the site server can certainly have a positive effect on performance, but > moving the source files off to the DP itself doesn’t make much sense as it > provides no benefit and will cause additional network load. > > > > J > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Daniel Ratliff > > *Sent:* Tuesday, May 19, 2015 11:52 AM > > > *To:* [email protected] > *Subject:* [mssms] RE: Migrating App Shares > > > > You can easily use PoSH to change the source path on drivers,boot images, > os images, packages, and I assume applications. I have done large > migrations on all but applications. Was in the same boat in our 2007 > environment, everything was on the site server. > > > > Just move the data, update the source directory, and you are set. > > > > *Daniel Ratliff* > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *John Aubrey > *Sent:* Tuesday, May 19, 2015 12:42 PM > *To:* [email protected] > *Subject:* [mssms] Migrating App Shares > > > > We currently have everything on one box, all SCCM rolls and the shares for > the various stuff in SCCM (images, packages, drivers, apps..). My goal is > to move the share folder with all the SCCM stuff to a different server. Is > there an easy way of doing this, or is the best method delete everything > and reimport it? I’m trying to break apart SCCM and the DP role + shares > onto a different servers. > > > > --John > > > > > 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. > > > > > > > > > >
