Microsoft System Center Configuration Manager 2007: Virtualization Challenges and Poor Design Choices
As a proponent of the “virtualize first” movement, I was intrigued to learn that running System Center Configuration Manager (SCCM) virtually is not recommended for larger deployments. This is because SCCM is designed to consume large amounts of log files, which can lead to storage and performance issues in a virtualized environment. In this blog post, we will explore the reasons why SCCM 2007 is poorly suited for virtualization and what you can do to mitigate these challenges.
Why SCCM 2007 is Poorly Designed for Virtualization
One of the main reasons why SCCM 2007 is not well-suited for virtualization is its reliance on text-based log files. Every time a client connects to the SCCM server, it generates a large amount of log data that is stored in the inbox folder. This log data contains valuable information about the client’s state and activities, but it also consumes a significant amount of storage space and processing power.
The problem with this design is that it was made in a time when virtualization was not as prevalent as it is today. At that time, physical servers were the norm, and the performance requirements for SCCM 2007 were designed accordingly. However, with the advent of virtualization, the same hardware can now support many more virtual machines, leading to a situation where SCCM 2007 is no longer optimized for the new environment.
Moreover, the constant writing of log files to disk can lead to storage-related issues in a virtualized environment. Virtual machine disk I/O operations are slower than physical disk I/O operations, and the constant write operations required by SCCM 2007 can quickly saturate the available bandwidth and cause performance bottlenecks.
Mitigating Challenges with SCCM 2007 Virtualization
While the design limitations of SCCM 2007 make it challenging to run virtually, there are some strategies you can use to mitigate these challenges:
1. Use a dedicated storage for logs: Instead of storing log files on the same disk as the SCCM server, consider using a separate storage for logs. This will help to reduce the amount of data that needs to be processed and stored, thereby improving performance.
2. Configure the inbox folder size: You can configure the inbox folder size to limit the amount of log data that is stored on the SCCM server. However, be cautious when doing so, as reducing the inbox folder size too much can lead to data loss and other issues.
3. Use a different storage for the SQL database: Instead of storing the SQL database on the same disk as the SCCM server, consider using a separate storage for the database. This will help to reduce the amount of data that needs to be processed and stored, thereby improving performance.
4. Run the management console on a local computer: Instead of running the management console on the SCCM server, consider running it on a local computer. This will help to reduce the load on the SCCM server and improve performance.
5. Use a different server for the SQL database: If possible, consider using a different server for the SQL database. This will help to reduce the load on the SCCM server and improve performance.
Future Improvements in Configuration Manager 2012
Hopefully, Microsoft will address these design limitations in future versions of SCCM. Configuration Manager 2012, which is currently in beta 2, shows promise in this regard. According to Microsoft’s documentation, Configuration Manager 2012 uses a new log file format that is more efficient and consumes less storage space than the previous format.
Furthermore, Configuration Manager 2012 introduces a new feature called “log file compression,” which can help to reduce the amount of storage required for log files. This feature is especially useful in virtualized environments where storage space is a premium.
Conclusion
While SCCM 2007 is not well-suited for virtualization due to its poor design choices, there are strategies you can use to mitigate these challenges. Moreover, future versions of SCCM such as Configuration Manager 2012 show promise in addressing these limitations. As a proponent of the “virtualize first” movement, I urge Microsoft to continue improving the performance and scalability of its management software to keep pace with the growing demands of virtualization.