Hello, I am trying to upgrade a new installation of Configuration Manager 2007 R2 to SP2, but I cannot install the update, I receive an error immediately that says "The version of this file is not compatible with the version of Windows you are running. Check your computers system information to see whether you need an X86 or X64 verison..." I have SCCM installed on a Windows 2008 R2 Server. The installation is clean, I have not started anything on it yet. Any help would be appreciated. I tried searching for tips on this particular error but I am coming up empty. Thanks, Joe

It is not supported to install ConfigMgr SP1 on Windows 2008 R2 and then upgrade to SP2. You should get the SP2 integrated media and install from there.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

ok, I am trying to pin down a copy of the full SP2 media, but am having difficulty finding it all together. I have been trying to load SCCM SP1 on a Windows 2008 Std server (not R2) and I am receiving an error on installation regarding the SMS Provider. I have Googled the error and tried just about everything, following the steps on the various articles and I cannot get it to install. At this point I am seriously considering just going back to R2 and installing on that again and just doing without SP2 for now until an upgrade path becomes available via some other posted method. I am at a loss, it is either that or go back to Windows 2003 R2 which I would like to avoid.

What error are you receiving?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Here is the error that I am getting from the sccm installation log file: compilemoffile: failed to compile mof d:\program files (x86)\microsoft configuration manager\bin\i386\smsrprt.mof, error -1 I have tried registering the service with an SPN, I have tried adsiedit to make sure that the registration is accurate. I have restarted the SQL service on the SQL server, and nothing. If anyone has any other tricks to try I am all ears. Thanks...

What SPN are you registering?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

I am registering the service account for my SQL service (domain account). So, I do: setspn -A MSSQLServer/<my SQL server>:1433 <MyDomain\SQLsvc2005>. I then run adsiedit.msc to verify that the SPN was successfully registered, which it is. I then go to the SQL server and restart the SQL server service.

For <my SQL server>, did you use the FQDN? Also, there is no need to restart the service as the SPN has nothing to do with the service itself.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

yes, I actuall have two entries on the SPN for the service account, the first entry is with the FQDN, the second is with the server name by itself.

How about delegation: http://support.microsoft.com/kb/319723?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Thanks, I was reading this article that you posted and it seems like it is for SQL 2000 on Windows 2003 Server, so I backed off. I have SQL 2005 on a Windows 2008 Server...

SPNs are a Kerberos concept and have nothing to do with the application itself thus the article, even though it references other products, is really about mutual authentication in Active Directory which is what setting up the SPN is supporting as is ensure that delegation is properly configured.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys