Hi! The site I am dealing with is a secondary site. I recently installed ConfigMgr 2007 SP2 on it. When I installed SP2, the prerequisite checker passed all checks on the trial run and failed all checks when it was run while actually being installed. I ended up having to use the /NoPrereq switch as outlined in http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/594c4800-7f6f-4190-bc4d-82e89124f9ae One of the weird things I noticed while running the prerequisite checker on this secondary site is that it even fails checks for the Primary Site such as "Pre-SMS 2003 SP2 direct child sites" when I have never even had SMS installed on this network. When that switch was used the install worked fine and I have had no problems since. Today I am attempting to install R2 on that site having already installed it on my other Primary and Secondary sites. It appears I am having the same problem with this one as I am receiving the following error: "Microsoft System Center Configuration Manager 2007 R2 requires a Configuration Manager 2007 installation of version 4.00.6202.0000 or higher." The version of all my sites, according to the Site Management object is 4.00.6487.2000 (including the site I am talking about). However, when I go to Help -> About on this secondary site it shows version number 4.00.5931.0000. My previous solution was to bypass the prerequisite checker. If this is going to happen every time I would rather find the root of the problem. Where should I be looking to determine what is causing this?

When you upgraded your primary site to SP1 (or SP2) did you also upgrade the secondary sites? If I remeber correctl 5931 is RTM. If you go to Site Database>Site Management and click on your central site (or parent primary) so you can see all of your secondary sites in the right pane you will see a version column there. What's listed as the version there? John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Yes, you're right. 5931 is RTM. The version of the site in the results pane is 4.00.6487.2000, which is proper for SP2. The location it shows up as 5931 is in the "About System Center Configuration Manager" item in the help menu of the console installed on the site. SP2 installed properly after I used the /noprereq flag. Communication between sites is fine and there have been no errors or warnings.

When you say the console is installed on the site are you referring to the secondary site? If so that's your problem. It's unsupported to install the console on secondary site servers and it does break stuff. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Yeah, that must be it then. How do I uninstall the console? There doesn't seem to be an option on the uninstaller. Do I have to reinstall the secondary sites that have the console installed on them?

See http://technet.microsoft.com/en-us/library/bb693800.aspx: "A Configuration Manager console should not be installed on an SMS 2003 secondary site server computer. If the Configuration Manager console has been installed on an SMS 2003 secondary site server computer, the secondary site cannot be upgraded to Configuration Manager 2007."

Yeah, I read that, however I have never had SMS 2003 installed. There was no upgrading from SMS 2003. This was a clean server until Configuration Manager 2007 RTM was installed back in 2008. So Configuration Manager 2007 RTM was installed, then the console was installed, then Configuration Manager 2007 SP2 was installed with the /noprereq flag.

The article mentions SMS 2003 but the same is true of SCCM. Never install the console on secondry sites. I don't know how to uninstall it though sorry.John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

I believe I can get away with reinstalling the secondary sites. Tomorrow I will give that a shot and see if it fixes the issue.

Looks like you were right, John. Thanks for the help! Just to clarify, it is only secondary sites that cannot have the management console installed on them?

Yes you can have it on primary sites.John Marcum | http://myitforum.com/cs2/blogs/jmarcum |