locked
Odd software update migration issues RRS feed

  • Question

  • Hi,

    I have an odd software update migration issue between 2007 and 2012 (current branch).

    My client has a software update list for Workstations which is empty as they have been adding the updates directly to the Deployment management policy for that update list.

    Problem is when the migration has completed in 2012 it is reporting as empty as I believe the migration process is using the update list for the generation and not the deployment management policy.

    Any ideas how to resolve?

    One idea I had was to try and add all the updates from the deployment management policy to the update list but that could be as many as 500+ updates to add manually unless I can use the search features to make it easy.

    Mike

    Wednesday, March 2, 2016 9:56 AM

Answers

  • Without documentation, how do they even know? How they/you know if what they have is even sufficient?

    It would be far easier to set them up an automated process using ADRs instead of migrating old, question-able updates. You can simply exclude the updates that they *know* should be excluded (using custom severity) and let the ADR do the work.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by MikePalmer Monday, March 7, 2016 6:50 PM
    Saturday, March 5, 2016 10:03 PM

All replies

  • Don't know an exact answer here, but why not change things up and start them using ADRs now istead of migrating something that can easily be recreated?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, March 2, 2016 1:23 PM
  • Morning Jason,

    That's an option but I cannot be sure what updates the client has not deployed out of the security/critical updates due to them impacting the business.

    Mike

    Friday, March 4, 2016 9:51 AM
  • Don't they have that documented anywhere?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Saturday, March 5, 2016 12:41 AM
  • I can't comment on the subject of documentation ;)

    Yesterday I worked out why I was having issues which was my error. So far during the migration I have been migrating objects but not the collections yet. Turns out that the deployment management policies have references to collections so they can only be migrated using the collection migration feature.

    Hopefully I'll migrate the collections Monday/Tuesday this week following some housekeeping.

    Mike

    Saturday, March 5, 2016 9:00 AM
  • Without documentation, how do they even know? How they/you know if what they have is even sufficient?

    It would be far easier to set them up an automated process using ADRs instead of migrating old, question-able updates. You can simply exclude the updates that they *know* should be excluded (using custom severity) and let the ADR do the work.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by MikePalmer Monday, March 7, 2016 6:50 PM
    Saturday, March 5, 2016 10:03 PM