locked
ConfigMgr 2012 SP1 to ConfigMgr 2012 R2 Site by Site Migration and Direct Membership Rules RRS feed

  • Question

  • Hi,

    one of my customers wants a Site by Site Migration form ConfigMgr 2012 SP1 to ConfigMgr 2012 R2 CU3.

    No we have some Trouble migrating the Collection Direct Membership Rules. The ConfigMgr Clients are migrated by WSUS. Therfore they create a new Object in ConfigMgr 2012 R2. know The Problem is that the Direct Membership Rules reference to the old Ressource ID.

    Is there a way to migrate the Computer Objects? Or do I have to write a powershell script to Change the Resource IDs.

    Thank you very Much.

    Tuesday, November 25, 2014 4:34 PM

Answers

  • You'll have to be "creative" to create the new direct membership rules. PowerShell is of course a great way to do this.

    Better yet, convert the rules to query based rules.


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

    • Marked as answer by BigHatte Tuesday, November 25, 2014 9:43 PM
    Tuesday, November 25, 2014 7:21 PM

All replies

  • You'll have to be "creative" to create the new direct membership rules. PowerShell is of course a great way to do this.

    Better yet, convert the rules to query based rules.


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

    • Marked as answer by BigHatte Tuesday, November 25, 2014 9:43 PM
    Tuesday, November 25, 2014 7:21 PM
  • Thank you Jason,

    I thought there would be an easier Way out of Box. Because of the Time Frame for Migration we need to sync Changes a view times in both directions.

    What is your best practice to avoid direct Membership Rules? For Example Do you create AD Sercurity Groups for Query Based Collection Rules?

    Tuesday, November 25, 2014 9:43 PM
  • There's no such thing a best practice. Every scenario and environment has unique elements and exactly how you do something depends upon what you are doing and what your goals are.

    Minimizing the number of rules created and the amount of manual intervention is typically a good goal though. This in turn would dictate that you use query based rules. Many folks also use AD security groups. This typically works quite well but does add a small amount of complexity.

    Direct membership rules are directly tied to a resource ID as you've noticed. "Resource" is the key word here as they are not tied to actual target systems. Thus, if the resource ID changes for any reason, the membership rule is useless. For most environment, that's not a big deal, but it ulti8mately depends upon what you are using the collections for.


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

    Wednesday, November 26, 2014 2:55 PM