O R G A N I C / F E R T I L I Z E R: behaviors with configmgr and supernets

Apr 12, 2010

behaviors with configmgr and supernets

i was forwarded a very useful blog post called “clarification on issues resulting from the use of supernets in configmgr 2007”.  if you need details, i urge you to read it.  this is just a summary of the post for my own benefit.

related blog posts:

 

site assignment / client push:

  • adsysdis writes ad site and ip subnet information to ddr
  • ddm compares ddr data against site boundaries
    • if ad site is in site boundaries, assigned = yes
    • if supernet is listed in site boundaries (directly), assigned = yes
    • client’s true subnet (non-supernet) listed in site boundaries, assigned = no

 

package source location:

  • client posts request to mp with the following:
    • package id
    • package version
    • assigned site code
    • ip address
    • calculated ip subnet
  • mp executes stored procedures to retrieve:
    • child secondary sites below assigned site
    • sites codes where ad site and/or ip address are assigned
  • mp then executes stored procedures to retrieve:
    • list of protected DPs
    • list of unprotected DPs
  • information is returned to client to process and determine best source