At Microsoft IT, we are beginning the process of running our ConfigMgr infrastructure on Hyper-V (virtualized) and we are starting to invest some energy in architecting our future data center in a way to ensure we are cost effective yet performance conscious.
In this blog post, I wanted to share some of the cornerstones of how the dynamic provisioning takes place for our ConfigMgr site roles. In particular, I’m going to focus my attention on ConfigMgr 2007 Distribution Points.
As many are aware, deployment of site roles in ConfigMgr is a one-time “tax” that most system managers do manually. Besides, how often is one actually deploying new distribution points?
This is a very valid question but the game changes in the world of virtualization whereby the process for acquiring hardware resources is eliminated. With this barrier broken down, a system manager can move well beyond the manual and really start to think “dynamically” in the space of deployment & provisioning.
Thus, deploying Distribution Points (DP) is still a push methodology yet one that now is initiated by the system rather than a human being.
In the following script, we dynamically will advise the site server (in this case, our primary site) that we would like to deploy the DP role on the target system. This is done through our dynamic use of System Center Virtual Machine Manager 2008 (a future post) but just assume the OS is laid down and the server is already provisioned with IP stack, required roles\features (e.g. IIS, BITS, and WebDAV) & the domain membership is complete. With this out of the way, we move to deployment of the role -
Site Name: MMS
Site Server: CM01
To quickly pull this altogether, this script is just another method to deploy a site role and really becomes a reality when you start to virtualize your data center. Enjoy!