Somewhere between the physical and the virtual
System Center Blogs
Configuration ManagerThe team that supports Configuration Manager.
OrchestratorA blog by the teams who make and support Orchestrator.
Operations ManagerThe folks who make and support Operations Manager.
Data Protection ManagerBlog done by the Data Protection Manager product and support teams.
Service ManagerCommunications from the System Center Service Manager team.
Virtual Machine ManagerThe team that makes and supports Virtual Machine Manager.
System Center HomeThe home page for System Center on the Web.
System Center on TechNetTechNet's agglomerated resources on System Center.
myITforum.comRod Trent's Web site primarily focused on systems and configuration management.
SystemCenterCentral.comThird-party site that pulls together stuff across the SC suite.
Deployment ForumCommunity site about Windows deployment matters.
The Blogcast RepositoryWhere you'll find technical videos, blogs, forums and more on Config Manager as well as other System Center products.
FAQShop.comHints, tips, answers, FAQs on Microsoft's systems management products.
Virtualization FeedMaster aggregator of blog posts and twitters on virtualization.
Virtualization HomeFor all pertaining to the Microsoft Virtualization story.
Hey everyone, coming back from TechEd USA, a few of us were discussing some topics that came up, and a common thread was what version of ConfigMgr is needed for what? So, we thought we would list out the order and min requirements at a product level. There are other pre-reqs at the support, service, or component level that will also be verified at each product level installation in the setup phase. So areas like OS level, patch level, hotfix presence, SQL versions etc will still be checked. Those aren't covered in this post.
We often get asked what shipped when? The ship order looks like this from a calendar view:
But what version do you need? Well, the most current available version of ConfigMgr to all licensed customers is Service Pack 2. If your organization has Software Assurance (SA), your most current version (available) is ConfigMgr SP2 R2.
If you want to install a certain version of the product what is the order? Like many areas, the answer can be ‘it depends’. But, the logical start is to deploy SP2. The other area where organizations have told us they need clarification is with the ‘R’ releases. For example:
One thing to also make clear is if an organization wants to deploy a certain OS as a managed client, or as a site infrastructure host, the following applies:
Some recommendations for organizations looking at or using Configuration Manager 2007 products today:
Jeff Wettlaufer Sr Technical Product Manager System Center, Management and Security Division
Will it be possible to upgrade R3 beta to R3 RTM ? as you know, a SCCM lab isn't a small thing, so untill now, I'm keeping away from testing betas... but I would like to do it..
Hey Conrad, I totally understand your situation. Labs take a lot of time and work to setup. For R3, yes the beta will upgrade to the RTM product level. Because this is a beta though, this is not supported in production for customers. The only group that has that supported is our TAP program.
Technically it will work in your situation, and as you are referring to a lab its not creating a production support issue.
Hi Jeff, we are in the process of performing a pilot of SCCM. Our current environment consists of SMS 2003 SP3. Two questions; do you have any current "official" guidance for performing an in-place migration of SMS 2003 to SCCM 2007 versus a clean install to R2 or R3 Beta?
Also, is R3 of SCCM considered to be stable enough for a production environment? We are only planning to use remote support, OS deployment, and application deployment features but we don't want to do this work twice when the v.Next is introduced next year and we are planning for full production rollout this year. Perhaps we can get enrolled in the TAP for v.Next? We have 1280 desktops in our environment.
We are currently in the process of performing a pilot project to upgrade SMS 2003 to SCCM 2007. I have two questions; first do you have any "official" or otherwise unofficial guidance on doing an in-place upgrade of the exising environment versus doing a clean install side-by-side?
Also, does MS currently recommend new deployments of SCCM to go with R3 Beta or should we stick with R2? Perhaps we can get enrolled in the TAP Program for R3. We really only want to do the work once on this deployment and would like to be able to upgrade to R3 RTM and/or v.Next when its released. But I can't find much information around on the implications of the path I just proposed.
BTW, we have about 1280 Desktops in the environment. I don't know what kind of clients MS is qualifying for entry into the TAPS program. I'd like to speak to someone though.