In the process of planning to apply R2 to my SCCM SP1 site. I ran across this in the help file: "After installing the Configuration Manager 2007R2 feature update release on the primary site server, Configuration Manager 2007R2 Setup must be run on any associated ConfigurationManager consoles to allow Configuration Manager 2007R2 features to be displayed." I need to also install it on my Secondary site too, right?

Thanks for the help and clarification.

So to be clear, in my case, I have one site in my organization. 1 Primary and 5 Secondary sites. You're saying I should apply R2 to the Secondary sites even though they don't have a database on them?

Torsten Meringer wrote: John Marcum wrote: it doesn't change the version number so I think JUST the primary sites. I shoudl have mentioned that I did do "upgrade secondary sites" to be on the safe side but I really think that was not needed. "Upgrade secondary sites" has nothing to do with R2. Matthew is right: yes, it has to be installed on secondaries (if you want to use the new features on them). "Upgrade secondary sites" pushes the current install files from the newly upgraded primary site and reinstalls the secondary site so how does it "have nothing to do with R2" Does R2 not update the install media on the site server? If not then anytime you add a new secondary site you would have to manually install R2 afterwards which makes no sense at all.

I was really hoping someone from Microsoft would post a definitive answer to this post.

If you want to take advantage of the R2 features, such as multicast and virtual apps support on DPs at secondary sites, then you must manually install R2 on secondary sites. It is not going to "upgrade" through the console automatically, or with an Upgrade Sites action, as it is not a version of Configuration Manager (at least not in the sense that you change server or client versions). It is a manual install. R2 can't be installed on a child site if the parent is not R2 also.

Thanks Wally. That answers my question.

John said: I was really hoping someone from Microsoft would post a definitive answer to this post. Wally says: Sometimes we don't have time to monitor and respond :-( Would be nice if people didn't expect us to :-) I was in China all last week teaching Configuration Manager, so not able to do much responding with teaching all day, hour long bus rides each direction, and having to eat and sleep. Sorry if that means I was selfish by not checking the forums (I know, just joking). You'll see I responded to practically nothing last week, and likely won't get to things this week either, as I'm teaching Configuration Manager to some new hires here the next couple of days also. As much as you guys don't want it, I do have a personal life also :-)

A life??? What's that?? So can we push out the install to the secondary sites via SCCM? I can't imagine running the installation manually on 350 secondary sites. :-(

Yes, that is what I'd do.

Is there a question that has not been answered, or just saying that the topic has been an interesting one? Just making sure nothing is lingering here.

I'm good on this one.