Here’s a new Knowledge Base article we published today on ConfigMgr 2007. This one talks about a couple issues you might run into if you use the Site Repair Wizard to restore a System Center Configuration Manager 2007 site server from a 32-bit Operating System to a 64-bit Operating System:
Microsoft supports the use of the Site Repair Wizard to restore a System Center Configuration Manager 2007 site server from a 32-bit Operating System to a 64-bit Operating System as noted in the article About the Site Repair Wizard (http://technet.microsoft.com/en-us/library/bb680393.aspx). However, there are two possible issues that may occur on a site server restored in this manner. These issues will only occur if the site server was originally installed to the default \Program Files\Microsoft Configuration Manager directory on the 32-bit Operating System.
Issue 1: Hotfixes, Service Packs, R-releases fail to install. Windows Installer (.MSI) based packages will redirect the TARGETDIR property from \Program Files\Microsoft Configuration Manager\ to \Program Files (x86)\Microsoft Configuration Manager\ on the 64-bit Operating System. As the site server is installed to \Program Files the patch or update will fail.
Use the mklink command line tool to temporarily redirect the installation folder:
mklink /D "C:\Program Files (x86)\Microsoft Configuration Manager" "C:\Program Files\Microsoft Configuration Manager"
Once the symbolic link is created, the hotfix or update installation will run without error. After the installation is complete, the link should be removed using rmdir:
rmdir "C:\Program Files (x86)\Microsoft Configuration Manager"
Issue 2: On System Center Configuration Manager 2007 R3 Site Servers with a Reporting Services Point installed, the Reporting Services node of the Administrator Console will fail to load. The following error can be seen in the adminui.log:
System.InvalidCastException\r\n[A]Microsoft.ConfigurationManagement.Reporting.Internal.Proxy.CatalogItem cannot be cast to [B]Microsoft.ConfigurationManagement.Reporting.Internal.Proxy.CatalogItem. Type A originates from 'Microsoft.ConfigurationManagement.Reporting, Version=22.214.171.124, Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context 'Default' at location 'C:\Program Files\Microsoft Configuration Manager\AdminUI\bin\Microsoft.ConfigurationManagement.Reporting.dll'. Type B originates from 'Microsoft.ConfigurationManagement.Reporting, Version=126.96.36.199, Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context 'LoadFrom' at location 'C:\Program Files (x86)\Microsoft Configuration Manager\AdminUI\bin\Microsoft.ConfigurationManagement.Reporting.dll'.\r\n at Microsoft.ConfigurationManagement.Reporting.Internal.Proxy.ReportingService2005.ListChildren(String Item, Boolean Recursive)
This occurs when R3 has been installed after using the Site Repair Wizard to move from a 32-bit to 64-bit Operating System, and after using the mklink resolution noted previously.
Edit the registry to set the R3 Assembly Search Path value to C:\Program Files\Microsoft Configuration Manager\AdminUI\bin\Microsoft.ConfigurationManagement.Reporting.dll in the following location:
For the most current version of this article please see the following:
J.C. Hornbeck | System Center & Security Knowledge Engineer
App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/