“What has changed in Configuration Manager?” This is one of the first questions people ask me when talking about the next release. That is a VERY big question to answer and I don’t intend to answer it all right here. After all, there is product documentation. And I know that everyone reads the documentation, right?
Even if you have read the documentation, I wanted to give you the “skinny” on what to expect with changes regarding primary site servers – which is a rather drastic difference from what you had in Configuration Manager 2007. Biggest changes:
Ok, now that I have piqued your interest (or raised your blood pressure), understand that this is all part of reducing infrastructure management requirements. In other words, making your life much easier. So what can the primary site server do now?
You obviously need at least one primary site server if you are going to manage any clients with Configuration Manager 2012. But in what circumstances might you install more than one primary site server?
It is important to understand that ConfigMgr 2012 now only supports up to a maximum of 25 primary site servers in a single hierarchy. This low number actually will make more sense when you understand that ConfigMgr 2012 eliminates scenarios to deploy primary sites that you might have used in previous versions.
These are the reasons you are no longer required to deploy a primary site server in ConfigMgr 2012, as you did in previous versions. All of these scenarios are now handled logically, instead of physically, at a primary site.
There are certainly more details available in our documentation, but at a high level, this gives you a quick overview of the BIG changes we have made with primary site servers. You can use this information to jumpstart system architecture discussions and presentations to your leadership team about how reducing server infrastructure requirements can help save money with ConfigMgr 2012.
That makes it a win for everyone! Welcome to System Center 2012 Configuration Manager primary site server improvements.
D.C. Tardy Senior Program Manager System Center 2012 Configuration Manager
Comments in this blog are open and monitored for each post for a period of two weeks after the posting date. If you have a specific question about a blog post that is older than two weeks, please submit your question via our Twitter handle @MSCloud