Project Description
SiteBound is a tool that allows bulk addition of boundaries to ConfigMgr (SCCM ) sites. Adding boundaries through the ConfigMgr console can be tedious if adding more than a handful. Previously for SMS 2003 there was the Siteboun.exe tool which solved this problem, however, to my knowledge there is not a version of this tool available for ConfigMgr 2007. If there is, then oh well I still learned something.

This tool is not as full featured as the Siteboun tool for SMS 2003. It will only add new boundaries to a ConfigMgr site.

Running the tool

SiteBound.exe /s {central site server} /file {excel file} /log {path}

/s Central Site Server name.
/file Path to Excel files.
/log Log file path.
  • The input for this tool is an Excel 2003 spreadsheet and there are some requirements for the format of this spreadsheet. Review the example spreadsheet, sbexample.xls, attached. Any deviation from this will either produce errors or unexpected resutls.
  • All output from this tool is written to the log file only. (The Trace utility from the ConfigMgr toolkit can be used to view the log)


Notes

I created this as a quick and dirty solution, its not polished or fine tuned, but since you can get the source code feel free to make changes as you wish.

There is limited validation of the input data.

The following is validated by this tool:
  • The boundary specified is not currently a boundary of the site code specified. If the boundary already exists in the site specified then theboundary will be skipped and execution will continue.
  • The boundary type must be valid and determinable. The tool will attempt to determine the boundary type using regular expressions. If it cannot then the server is skipped where this boundary is specified and execution continues. (IP Ranges, IP Subnets, AD Site Names, and IPv6 Prefixes are supported)

The following is not validated by this tool:
  • The boundary is a boundary in another site in the hierarchy. (i.e. overlapping boundaries)
  • The boundary specified represents a valid location on the network.
  • The boundary description specified does not contain profanity.


Testing

Testing has not been performed with IPv6 prefix boundaries.
Testing has not been performed against ConfigMgr 2007 SP1.
Testing has not been performed with a "/s" command line parameter other than the central site server. (it should work if you specify a regular primary site server but processing will fail for any sites specified in the spreadsheet that the primary site does not know about.)

I have used this tool succesfully in my production hierarchy with IP Range Boundaries and AD Site Name boundaries. I have not tested IP subnet boundaries or IPv6 prefix boundary. Also, I'm not sure that the regular expression used to determined IPv6 prefix boundary type is valid.

Last edited Jun 6, 2008 at 7:30 PM by ddelgado1, version 2