locked
SCCM 2012 Clients fail to install due to bad Windows upgrade (XP to 7) and orphaned SCCM 2007 clients RRS feed

  • Question

  • The scenario is the next:

    The company used to have a SCCM 2007 hierarchy, when this hierarchy existed, all the clients were Windows XP Pro, and then the hierarchy was deleted (not uninstalled or properly removed), letting all the clients orphaned, then due to an upgrade in all his desktops, the old Windows XP with SCCM 2007 clients were "overwrited" with a custom image of Windows 7, letting all the old values of SCCM 2007 stucked in several systems.

    Now we're trying to move those clients to SCCM 2012, and we already tried several troubleshooting steps, related to WMI, DCOM, overwriting parameters with Easy Transfer from healthy systems to the damaged ones, even tried to use SMS 2003 Toolkit... but nothing has worked.

    Does anyone has faced a similar issue?

    Thanks in advanced for your help!

    Cesar M.V.


    • Edited by cesarman Tuesday, September 9, 2014 12:00 AM corrections
    Monday, September 8, 2014 11:55 PM

Answers

  • I'm trying to replicate with more clients, but the workaround was:

    Search for the old installation folder and perform a manual uninstall

    In some clients I had to run:

    winmgmt /clearadap
    winmgmt /kill
    winmgmt /unregserver
    winmgmt /regserver
    winmgmt /resyncperf

    Set the client installation properties manually

    And last, verify that the Boundary Groups were assigned correctly to his corresponding site.

    Now the clients started to install.

    Thanks to both for your help!

    Regards.

    Wednesday, September 10, 2014 6:32 PM

All replies

  • Hi,

    Examine client.msi.log then. The actual error should be listed a few lines above the first occurance of "return value 3".


    Here's a great and still valid guide for troubleshooting client installation end-to-end:
    http://support.microsoft.com/kb/925282



    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Tuesday, September 9, 2014 8:14 AM
  • Hi Xin, thanks for your quick response, I'm trying to validate the troubleshooting mentioned on the link, thanks!

    Just one quick question, no "return value 3" or "error code 3" or something related to that was found on the client.msi log file... any other suggestion?

    Thanks again for your time and help!

    Tuesday, September 9, 2014 5:09 PM
  • Did you try to install the ConfigMgr (2012) client at all? You did not mention that explicitely. If so: how? Did you also clean up the system management container in AD?

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, September 9, 2014 5:14 PM
  • Hi Torsten, yes, tried several times the installation, and with a lot of troubleshooting... the container is OK, I have about 1,800 computers working fine, but not the ones with this particular issue with the old SCCM 2007 client stucked.

    I've also tried to run the installation manually, removed the computer from SCCM and run discovery again, checked if something was wrong with the SMSCFG file and the computer account SID in AD, but nothing has worked.

    Tuesday, September 9, 2014 5:30 PM
  • So what does ccmsmetup.log tell?

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, September 9, 2014 5:39 PM
  • In short:

    File C:\Windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
    Action:
    ErrorMessages:

    And in the client.msi log there's something strange, first says this:

    MSI (s) (F8:00) [12:09:24:240]: Producto: Configuration Manager Client - la actualización "CLP3082" no se pudo instalar. Código de error 1603. Se dispone de información adicional en el archivo de registro C:\Windows\ccmsetup\Logs\client.msi.log.

    And immediatly says:

    MSI (s) (F8:00) [12:09:24:240]: Windows Installer instaló una actualización. Nombre del producto: Configuration Manager Client. Versión del producto: 5.00.7804.1000. Idioma del producto: 3082. Fabricante: Microsoft Corporation. Nombre de la actualización: CLP3082. Resultado de la instalación: 1603.

    At the end of the client.msi log appears this:

    MSI (s) (F8:00) [12:09:24:240]: Producto: Configuration Manager Client -- Fallo en la operación de instalación.

    MSI (s) (F8:00) [12:09:24:240]: Windows Installer instaló el producto. Nombre del producto: Configuration Manager Client. Versión del producto: 5.00.7804.1000. Idioma del producto: 3082. Fabricante: Microsoft Corporation. Resultado de la instalación: 1603.

    Based on this looks like the problem is related to the language, but we have a lot of clients with OS in spanish working fine.

    Tuesday, September 9, 2014 6:09 PM
  • Checking another system, in which we haven't performed any troubleshooting, in the LocationServices log, there are references to the old hierarchy, I've tried to put the installation properties in the client push like this:

    SMSSITECODE="new site code" SMSMP="primary server name.domain.domain FSP="primary server name" DNSSUFFIX="Domain.domain"

    But still looking for the old servers... Is there a way to completely clear the client (not reinstalling OS)?

    Tuesday, September 9, 2014 7:30 PM
  • LocationServices.log should tell you were the old sitecode came from (AD, DNS or the registry). Make sure to remove those pointers.

    You were not able to find "return value 3" in client.msi.log because it's in Spanish (?). You would have to search for the translated term them.


    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, September 9, 2014 7:40 PM
  • Tried to look for the "return value 3" in spanish with no luck..

    The LocationServices.log says this:

    Failed to send request to /SMS_MP/.sms_aut?MPKEYINFORMATION at host "OLD MP SERVER", error 0x2ee7

    And lines below says this:

    Failed to refresh trusted key information while refreshing mp list. LocationServices 05/09/2014 02:44:25 p.m. 3940 (0x0F64)

    Also this messages:

    Persisting the default management point in WMI LocationServices 08/09/2014 08:13:44 a.m. 5788 (0x169C)

    Persisted Default Management Point Location locally LocationServices 08/09/2014 08:13:44 a.m. 5788 (0x169C)

    So... I'm thinking about running CCMSetup RESETKEYINFORMATION=TRUE to reset the trusted key and rebuild WMI repository, does that makes sense to you?

    Tuesday, September 9, 2014 8:39 PM
  • I'm trying to replicate with more clients, but the workaround was:

    Search for the old installation folder and perform a manual uninstall

    In some clients I had to run:

    winmgmt /clearadap
    winmgmt /kill
    winmgmt /unregserver
    winmgmt /regserver
    winmgmt /resyncperf

    Set the client installation properties manually

    And last, verify that the Boundary Groups were assigned correctly to his corresponding site.

    Now the clients started to install.

    Thanks to both for your help!

    Regards.

    Wednesday, September 10, 2014 6:32 PM