ConfigMgr/SCCM R3 Installation Notes

Quick correction to that last post: the shortest path is to install ConfigMgr 2007 SP2 from media that has SP2 integrated already. This is actually required if your site server is WIndows 2008 R2 as upgrading from RTM or SP1 is not supported then.

Also note that saying R3 is the same as R2 is incorrect. R3 contains all of the features or R2 plus Power Management and a handful of console accelerators, Delta Discovery and Dynamic Collection Evaluation.

And one other bit of info, migration from anything but ConfigMgr 2007 will not be supported. SMS 2003 is a unsupported product as of last year January.

Besides client side Power Management updates, R3 seems to be mostly Primary Site enhancements along with console updates.  I am trying to avoid deploying the patch and R3 to my many child secondary sites as well as the clients. 
 
Has anyone deployed R3 just on their Primary Site servers and skipped the secondary sites and clients?
 
Going to test this out in our lab, but just curious if anyone else has taken this approach.
 
Thanks

dchapman


Besides client side Power Management updates, R3 seems to be mostly Primary Site enhancements along with console updates.  I am trying to avoid deploying the patch and R3 to my many child secondary sites as well as the clients. 
 
Has anyone deployed R3 just on their Primary Site servers and skipped the secondary sites and clients?
 
Going to test this out in our lab, but just curious if anyone else has taken this approach.
 
Thanks

We recently did the above in our Production environment and all went well.  R3 without the client side patch and did not upgrade the secondary site servers.  Had to update the Central reporting site first and then the Primary admin site and it went fine. Now its time to focus on 2012 :-)