Patch Management Solution

 View Only
  • 1.  Updating package source after moving patch repository

    Posted Nov 27, 2015 02:41 PM

    I recently moved my patch location from D: to E: and copied over all the packages manually after chaging the source in the settings. I have run the software update package integrity check but the package source for any previous update still uses D:. Any newly staged patches source from E:. I suspect I should have done the "relocate package" option instead of doing a manual copy. How do I update the package source now on all the old packages without re-creating dozens of bulletins?



  • 2.  RE: Updating package source after moving patch repository

    Broadcom Employee
    Posted Dec 10, 2015 03:47 AM

    Hi Brandon,

    so you've performed these actions and even today the same problem still occurs?

    1. Changed software updates location in Core Services and successfully performed "Check Software Update Package Integrity" task with enabled "Relocate the downloaded packages"

    CoreServices.jpg

    2. Following scheduled tasks were successfully executed on NS side but you still have this problem even today?

    • NS.Package Distribution Point Update Schedule.{29a2b641-222a-43b0-830c-a25c59e93fe4}
    • NS.Package Refresh.{bd6bf880-bfae-4dad-b746-e8be99f3b8a8}

    Thanks,

    IP.



  • 3.  RE: Updating package source after moving patch repository

    Posted Dec 10, 2015 01:57 PM

    Yes I ran all that and still had trouble.

    I finally just decided to restore the 'update' folder to the d drive and re-run it all with relocate option again and this method updated all the targets and moved everything after about 12 hours or so. I guess doing the copy manually isn't an option,