Fix: Your ConfigMgr 2007 eval expired or you are unable to upgrade from the evaluation version

Fix: Your ConfigMgr 2007 eval expired or you are unable to upgrade from the evaluation version

  • Comments 1
  • Likes

imageHi everyone, Tyler Franke here again with another issue I ran into recently.  Consider a scenario wherein System Center Configuration Manager 2007 has been installed and service packed to the latest (SP2) build. Now let's assume that the Evaluation version of R3 is installed on the server at some point. Once the evaluation period expires (180 days later) the user can open the console but cannot perform any actions whatsoever once it's launched. After uninstalling the R3 evaluation the behavior continues and when attempting to reinstall SP2 or R3, it's unsuccessful and in the ConfigMgrSetup.log you find the following snippet:

ConfigMgrSetup.log snippet:

===================== << Starting SMS V4 SP2 Upgrade Setup >> =====================
<10-06-2011 14:27:32> Commandline : "D:\ConfigMgr07SP2Upgrade_RTM_ENU\SMSSETUP\BIN\I386\setup.exe"
<10-06-2011 14:27:32> This is 32 bit.
<10-06-2011 14:27:32> Verifying the Reg for AssetIntelligence Installation
<10-06-2011 14:27:32> Found installation of AssetIntelligence Full version
<10-06-2011 14:27:32> Setup detected an existing SCCM installation. Currently installed version is 6487
<10-06-2011 14:27:32> Phase is 1C7
<10-06-2011 14:27:32> Setting the default CSV folder path
<10-06-2011 14:27:32> SMS Build Number = 6487
<10-06-2011 14:27:32> SMS Version = 4.0
<10-06-2011 14:27:32> SMS Minimum Build Number = 800
<10-06-2011 14:27:32> Verifying SMS Active Directory Schema Extensions.
<10-06-2011 14:27:32> DS Root:CN=Schema,CN=Configuration,DC=introot,DC=com
<10-06-2011 14:27:32> Verifying SMS Active Directory Schema Extensions.
<10-06-2011 14:27:32> DS Root:CN=Schema,CN=Configuration,DC=introot,DC=com

<10-06-2011 14:27:33> Eval site is detected.
<10-06-2011 14:27:33> Eval site is detected.
<10-06-2011 14:27:33> Setup has detected an existing primary site on this computer.

Because the current installation is Configuration Manager 2007 Eval version, you do not have the option of upgrading the installation.
<10-06-2011 14:27:33> Eval site is detected.
<10-06-2011 14:27:33> Eval site is detected.
<10-06-2011 14:27:33> Setup has detected an existing primary site on this computer.

Because the current installation is Configuration Manager 2007 Eval version, you do not have the option of upgrading the installation.

Cause

When the EVAL version of R3 was installed (in this case over top of a licensed copy of ConfigMgr2007 SP2) it reset the installation to reflect it as an EVAL version.

This can be confirmed by checking the value of the "Product Id" string value in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\Setup in the case of a 64-bit operating system. If the "Product Id" string value is found set to BBH2G-XXXXX-XXXXX-XXXXX-XXXXX then it is indeed using the EVAL product key.

Resolution

To resolve this, perform an in-place upgrade of ConfigMgr. In my case we had to upgrade using the Configuration Manager 2007 SP2 Complete Release (I.E. ConfigMgr2007 with SP2 slipstreamed). Please see the following links for more guidance:

Configuration Manager 2007 SP2 Supported Configuration - http://technet.microsoft.com/en-us/library/ee344146.aspx

Configuration Manager In-Place Upgrade - http://technet.microsoft.com/en-us/library/bb693584.aspx

How to Perform an In-Place Upgrade - http://technet.microsoft.com/en-us/library/bb680984.aspx

Tyler Franke | Senior Support Escalation Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

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/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • How to upgrade from ConfigMgr2012 SP1 eval expired ?  What do I do, to reinstall SCCM2012 SP1 ?