Running System Center Configuration Manager 2007 in a Virtualized Environment: Pros, Cons, and Poor Design Decisions
As I recently attended the 6451B Planning, Deploying and Managing Microsoft System Center Configuration Manager 2007 course, I couldn’t help but notice a peculiar recommendation from one of the instructors: do not run System Center Configuration Manager (SCCM) virtually. This statement caught my attention as I’m a proponent of the “virtualize first” movement, and I was curious to understand the reasons behind this advice.
According to the instructor, SCCM is poorly designed in terms of log file management. The software relies heavily on text-based log files (inbox folder) to process client data before storing it in the back-end SQL database. This design choice is problematic for several reasons. Firstly, the constant writing of log files can cause high IO intensity, which doesn’t scale well with multiple clients. Secondly, the software’s reliance on text-based log files makes it less efficient compared to other modern management tools that use more advanced data storage and processing techniques.
The instructor also pointed out that SCCM’s poor design choices can lead to storage strain, especially when running the software virtually. Virtualized environments typically have limited storage capacity, which can become a bottleneck when dealing with large client populations and high log file activity. As a result, it’s essential to ensure that your storage is up to the task before deploying SCCM 2007 in a virtualized environment.
While there are ways to alleviate the strain on the machine running SCCM (such as running the SQL server on a separate server and using the management console on a local computer), the fact remains that sum of all the small write operations SCCM constantly does to your storage puts a heavy strain on it. Therefore, if you decide to run SCCM 2007 virtually, make sure you have adequate storage capacity and avoid saturating it with excessive log file activity.
It’s worth noting that these design limitations are specific to SCCM 2007 and may not apply to newer versions of the software, such as Configuration Manager 2012 (currently in beta 2). Hopefully, Microsoft has addressed these issues in the latest version, which promises better performance and more advanced features.
In conclusion, while it’s possible to run System Center Configuration Manager 2007 virtually, it’s crucial to be aware of the potential drawbacks and design limitations of the software. Before deploying SCCM 2007 in a virtualized environment, ensure that your storage capacity is sufficient and that you don’t saturate it with excessive log file activity. If you’re considering using SCCM for your organization, it may be worth waiting for Configuration Manager 2012 to see if Microsoft has addressed these issues in the latest version.