ConfigMgr Content Source Update Tool 1.0.2

Update the content source location of any object type in System Center Configuration Manager when migrating, or simply cleaning up a folder structure.

5 Star
6,470 times
Add to favorites
System Center
E-mail Twitter Digg Facebook
  • Doesn't copy each file or folder
    2 Posts | Last post March 10, 2020
    • Hi guys,
      It doesn't copy each file and folder of the package while selecting option "copy content files to new location". Am I the only one who is getting this issue?
    • We used robocopy to copy all files and folders to the new share. So, no issue.
      Maybe you have a permission problem here, so that the user you use to copy can't see all files and folders?
  • Lazy Properties are gone
    1 Posts | Last post March 10, 2020
    • We used the "ISVData"-property to save some information about the Package for our 1st LVL. Whatssoever, after changing the content source path all so informations are gone.
      ISVData is a lazy property. Is it possible that you don't load these and that this is the reason they are empty now?
      Another wish would be, to see the number of vailidated packages (or whatever) and the number of matching packages AFTER the validation. I just see  this numbers WHILE the validation is running.
      Do you still maintain this Tool? Would be great.
  • Application Update strips Content settings
    4 Posts | Last post November 29, 2019
    • First off, thank you very much for this tool, its very useful!
      I noticed that when it updates Application Deployment Types, it strips the settings that were there.  For instance, we check the box to Allow Clients to use DP from default site boundary group and set the Deployment options to Download Content from DP and run locally.  After the update, those are set to default and not retain the settings we had before.  That's a problem as I have quite a lot of them to update!
    • So, I figured out what's wrong with the code, at around line 244, the process creates a new instance of the Deployment type, and then only adds the ID of the old ID.  By adding a capture of the settings before then adding them in, it effectively retains the current settings, This is how I did that;
                                          #Update content source
                                          #Extract what the settings were before
                                          $PinOnClientB4             = $DeploymentType.Installer.Contents.PinOnClient
                                          $PeerCacheB4               = $DeploymentType.Installer.Contents.PeerCache
                                          $FallbackToUnprotectedDPB4 = $DeploymentType.Installer.Contents.FallbackToUnprotectedDP
                                          $OnFastNetworkB4           = $DeploymentType.Installer.Contents.OnFastNetwork
                                          $OnSlowNetworkB4           = $DeploymentType.Installer.Contents.OnSlowNetwork
                                          #Create a new instance
                                          $ContentImporter = [Microsoft.ConfigurationManagement.ApplicationManagement.ContentImporter]::CreateContentFromFolder($UpdatedContentLocation)
                                          $DeploymentType.Installer.Contents[0].ID = $ContentImporter.ID
                                          $DeploymentType.Installer.Contents[0] = $ContentImporter
                                          #Reset the settings to what they were before
                                          $DeploymentType.Installer.Contents[0].PinOnClient             = $PinOnClientB4
                                          $DeploymentType.Installer.Contents[0].PeerCache               = $PeerCacheB4
                                          $DeploymentType.Installer.Contents[0].FallbackToUnprotectedDP = $FallbackToUnprotectedDPB4
                                          $DeploymentType.Installer.Contents[0].OnFastNetwork           = $OnFastNetworkB4
    • Thanks for the additional fix! but you forgot one last setting at the end
      $DeploymentType.Installer.Contents[0].OnSlowNetwork           = $OnSlowNetworkB4
    • Hi Nickolaj,
      Were these excellent additions ever aded to the current version of the tool 1.0.2?
  • Ability to export / import to csv?
    1 Posts | Last post August 28, 2019
    • Hey, your tool looks great, however is it possible to add a feature to save the export to a CSV and then re import it? 
      We are changing our source file structure and it would be great to be able to manually change the path for each application in something like excel.
  • Updated script with the changes mentioned?
    1 Posts | Last post June 12, 2019
    • Is there an updated script with the changes mentioned about keeping the settings?  I put them in myself as the commentor mentioned, but I noticed they don't have the "[0]" in "$DeploymentType.Installer.Contents.PinOnClient" as the others seem to have something more like "$DeploymentType.Installer.Contents[0].PinOnClient".  I am not sure if that matters.
      Second thing, I am noticing the applications deployment type when being re-added is Priority 0 instead of Priority 1 like all my other applications.  Can this be easily modified as well?  I am looking for it in the script, but it hasn't jumped out at me yet.
  • Not listing
    1 Posts | Last post April 16, 2019
    • hey Nickolaj.
      Thanks for your job! it's really usefully!. i'm testing it in CB1810 version. but I don't see any list in the "Content source information", i have seen that when i do click in validate botton …. i can see apps, pkg, … names in logging box.
      did you see that? i have checked set-culture en-us without any change :( 
      any idea?
      thanks in advanced!
  • Warning :Unable to determine site code
    2 Posts | Last post January 23, 2019
    • Hi Nickolaj,
      Getting error when executing the script:
      Warning :Unable to determinesite code
    • Hi Nickolaj,
      Should not be sitecode instead siteservername
  • Would it be possible add an option to *not* update the DPs automatically?
    4 Posts | Last post January 23, 2019
    • I second HACarter111's idea...
      Would it be possible add an option to *not* update the DPs automatically?
      I have dozens of large packages tied to OSD and slow network connections, I don't want my Window's builds to be down while they replicate.  I would like just to update the source path.
      Thanks for the hard work you did on this script!
    • Hi,
      I'll add a note about this and update the tool once I'm back from my vacation.
    • This is not possible. Changing the source path of any content automatically initiates an *update* of that content. This does not copy every file though:
    • Hi Nickolaj,
      Getting error when executing the script:
      Warning :Unable to determine the site  code
  • Source Patch Not updating
    2 Posts | Last post October 10, 2017
    • Hello,
      I am trying to update source paths from \\sccmserver\d$\source to \\dfspath\sccm\source in the tool it finishes with ": Completed updating content sources" but there is no change in the package properties.
      Any ideas on what to check?
    • For those who need the answer, its a weird one, running from the Powershell ISE in the sccm console WORKS but the regular powershell does not. Same msg that it completes the task but only working through ISE.... 
  • Great Tool....but
    1 Posts | Last post May 10, 2017
    • I am having a problem moving *.inf files using the tool. Would there be reason for this? Have ensure that that 'everyone' has full share and security access.
1 - 10 of 11 Items